drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From julienledem <...@git.apache.org>
Subject [GitHub] drill pull request: DRILL-4134: Allocator updates
Date Tue, 01 Dec 2015 18:19:30 GMT
Github user julienledem commented on a diff in the pull request:

    --- Diff: exec/memory/base/src/main/java/org/apache/drill/exec/memory/README.md ---
    @@ -0,0 +1,121 @@
    + Licensed to the Apache Software Foundation (ASF) under one
    + or more contributor license agreements.  See the NOTICE file
    + distributed with this work for additional information
    + regarding copyright ownership.  The ASF licenses this file
    + to you under the Apache License, Version 2.0 (the
    + "License"); you may not use this file except in compliance
    + with the License.  You may obtain a copy of the License at
    + http://www.apache.org/licenses/LICENSE-2.0
    + Unless required by applicable law or agreed to in writing, software
    + distributed under the License is distributed on an "AS IS" BASIS,
    + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + See the License for the specific language governing permissions and
    + limitations under the License.
    +# Memory: Allocation, Accounting and Management
    +The memory management package contains all the memory allocation related items that Drill
uses to manage memory.
    +## Key Components
    +Memory management can be broken into the following main components:
    +- Memory chunk allocation and fragmentation management
    +  - `PooledByteBufAllocatorL` - A LittleEndian clone of Netty's jemalloc implementation
    +  - `UnsafeDirectLittleEndian` - A base level memory access interface
    +  - `LargeBuffer` - A buffer backing implmentation used when working with data larger
than one Netty chunk (default to 16mb)
    --- End diff --
    typo: s/implmentation/implementation

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message