On 01/14/2015 12:11 AM, Anand Avati wrote:
> 3) Why not have a separate iobuf pool for RDMA?
Since every fops are using the default iobuf_pool, if we go with another
iobuf_pool dedicated to rdma, we need to copy that buffer from default
pool to rdma or so, unless we are intelligently allocating t
On 01/13/2015 08:18 PM, Ben England wrote:
> Rafi,
>
> it totally makes sense to me that you need to pre-allocate i/o buffers that
> will be used by RDMA, and you don't want to constantly change (i.e. allocate
> and deallocate) these buffers. Since a remote RDMA controller can be reading
> and
3) Why not have a separate iobuf pool for RDMA?
On Tue Jan 13 2015 at 6:30:09 AM Mohammed Rafi K C
wrote:
> Hi All,
>
> When using RDMA protocol, we need to register the buffer which is going
> to send through rdma with rdma device. In fact, it is a costly
> operation, and a performance killer i
Rafi,
it totally makes sense to me that you need to pre-allocate i/o buffers that
will be used by RDMA, and you don't want to constantly change (i.e. allocate
and deallocate) these buffers. Since a remote RDMA controller can be reading
and writing to them, we have to be very careful about deal
Hi All,
When using RDMA protocol, we need to register the buffer which is going
to send through rdma with rdma device. In fact, it is a costly
operation, and a performance killer if it happened in I/O path. So our
current plan is to register pre-allocated iobuf_arenas from iobuf_pool
with rdma wh
Since we're on the subject of minimizing STAT calls, there was talk in the
small-file perf meeting about moving the md-cache translator into the server
just before the POSIX translator so that all the stat and getxattr calls, etc.
could be intercepted. This would be consistent with not needing
On Tue, Jan 13, 2015 at 12:46:51PM +0100, Niels de Vos wrote:
> Hi all,
>
> This meeting is scheduled for anyone that is interested in learning more
> about, or assisting with the Bug Triage.
>
> Meeting details:
> - location: #gluster-meeting on Freenode IRC
> - date: every Tuesday
> - time: 12:
Hi all,
This meeting is scheduled for anyone that is interested in learning more
about, or assisting with the Bug Triage.
Meeting details:
- location: #gluster-meeting on Freenode IRC
- date: every Tuesday
- time: 12:00 UTC, 13:00 CET (run: date -d "12:00 UTC")
- agenda: https://public.pad.fsfe.o
On 01/13/2015 05:45 AM, Anand Avati wrote:
Valid questions. access-control had to be as close to posix as possible
in its first implementation (to minimize the cost of the STAT calls
originated by it), but since the introduction of posix-acl there are no
extra STAT calls, and given the later intr
