From: Jens Axboe <axboe@kernel.dk>
To: Bijan Mottahedeh <bijan.mottahedeh@oracle.com>
Cc: io-uring@vger.kernel.org
Subject: Re: [RFC 1/2] io_uring: disallow overlapping ranges for buffer registration
Date: Fri, 12 Jun 2020 09:16:17 -0600 [thread overview]
Message-ID: <b33937c3-6dbb-607a-d406-a2b42f407d86@kernel.dk> (raw)
In-Reply-To: <1591928617-19924-2-git-send-email-bijan.mottahedeh@oracle.com>
On 6/11/20 8:23 PM, Bijan Mottahedeh wrote:
> Buffer registration is expensive in terms of cpu/mem overhead and there
> seems no good reason to allow overlapping ranges.
There's also no good reason to disallow it imho, so not sure we should
be doing that.
--
Jens Axboe
next prev parent reply other threads:[~2020-06-12 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 2:23 [RFC 0/2] io_uring: disallow overlapping ranges for buffer registration Bijan Mottahedeh
2020-06-12 2:23 ` [RFC 1/2] " Bijan Mottahedeh
2020-06-12 15:16 ` Jens Axboe [this message]
2020-06-12 18:22 ` Bijan Mottahedeh
2020-06-14 15:56 ` Jens Axboe
2020-06-12 2:23 ` [RFC 2/2] io_uring: report pinned memory usage Bijan Mottahedeh
2020-06-12 15:16 ` Jens Axboe
2020-06-12 15:19 ` Jens Axboe
2020-06-12 15:50 ` Jens Axboe
2020-06-13 4:43 ` Bijan Mottahedeh
2020-06-14 15:57 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b33937c3-6dbb-607a-d406-a2b42f407d86@kernel.dk \
--to=axboe@kernel.dk \
--cc=bijan.mottahedeh@oracle.com \
--cc=io-uring@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox