All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, jmoyer@redhat.com
Subject: Re: [PATCH 0/3] trivial fixes and a cleanup of provided buffers
Date: Thu, 05 Oct 2023 10:25:14 -0400	[thread overview]
Message-ID: <87pm1t2lkl.fsf@suse.de> (raw)
In-Reply-To: <2b5d884b-9709-4219-88bc-47840f62ff46@kernel.dk> (Jens Axboe's message of "Wed, 4 Oct 2023 20:18:26 -0600")

Jens Axboe <axboe@kernel.dk> writes:

> On 10/4/23 6:05 PM, Gabriel Krisman Bertazi wrote:
>> Jens,
>> 
>> I'm resubmitting the slab conversion for provided buffers with the
>> suggestions from Jeff (thanks!) for your consideration, and appended 2
>> minor fixes related to kbuf in the patchset. Since the patchset grew
>> from 1 to 3 patches, i pretended it is not a v2 and restart the
>> counting from 1.
>
> Thanks, this looks good. For patches 1-2, do you have test cases you
> could send for liburing?

Sure. I'll adapt them to liburing and submit shortly.

-- 
Gabriel Krisman Bertazi

  reply	other threads:[~2023-10-05 15:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  0:05 [PATCH 0/3] trivial fixes and a cleanup of provided buffers Gabriel Krisman Bertazi
2023-10-05  0:05 ` [PATCH 1/3] io_uring: Fix check of BID wrapping in " Gabriel Krisman Bertazi
2023-10-05  0:05 ` [PATCH 2/3] io_uring: Allow the full buffer id space for " Gabriel Krisman Bertazi
2023-10-05  0:05 ` [PATCH 3/3] io_uring: Use slab for struct io_buffer objects Gabriel Krisman Bertazi
2023-10-05  2:18 ` [PATCH 0/3] trivial fixes and a cleanup of provided buffers Jens Axboe
2023-10-05 14:25   ` Gabriel Krisman Bertazi [this message]
2023-10-05 14:38 ` 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=87pm1t2lkl.fsf@suse.de \
    --to=krisman@suse.de \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=jmoyer@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.