From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCHSET v2 RFC 0/11] Add support for ring mapped provided buffers
Date: Sun, 1 May 2022 08:25:07 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 5/1/22 7:39 AM, Pavel Begunkov wrote:
> I'd suggest for mapped pbuffers to have an old plain array with
> sequential indexing, just how we do it for fixed buffers. Do normal
> and mapped pbuffers share something that would prevent it?
Ah yes, we could do that. Registering it returns the group ID instead of
providing it up front.
--
Jens Axboe
next prev parent reply other threads:[~2022-05-01 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
2022-05-01 13:14 ` [PATCHSET v2 RFC 0/11] Add support for ring mapped provided buffers Pavel Begunkov
[not found] ` <[email protected]>
2022-05-01 13:39 ` Pavel Begunkov
2022-05-01 14:25 ` Jens Axboe [this message]
2022-05-01 15:00 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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