public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>,
	Caleb Sander Mateos <csander@purestorage.com>
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] io_uring/net: use REQ_F_IMPORT_BUFFER for send_zc
Date: Wed, 26 Mar 2025 22:31:23 +0000	[thread overview]
Message-ID: <d1bf1b35-126d-4484-8bb5-0a720717ad78@gmail.com> (raw)
In-Reply-To: <9770387a-9726-4905-9166-253ec02507ff@kernel.dk>

On 3/26/25 17:05, Jens Axboe wrote:
> On 3/26/25 11:01 AM, Caleb Sander Mateos wrote:
>> On Wed, Mar 26, 2025 at 2:59?AM Pavel Begunkov <asml.silence@gmail.com> wrote:
>>>
>>> On 3/25/25 14:39, Caleb Sander Mateos wrote:
>>>> Instead of a bool field in struct io_sr_msg, use REQ_F_IMPORT_BUFFER to
>>>> track whether io_send_zc() has already imported the buffer. This flag
>>>> already serves a similar purpose for sendmsg_zc and {read,write}v_fixed.
>>>
>>> It didn't apply cleanly to for-6.15/io_uring-reg-vec, but otherwise
>>> looks good.
>>
>> It looks like Jens dropped my earlier patch "io_uring/net: import
>> send_zc fixed buffer before going async":
>> https://lore.kernel.org/io-uring/20250321184819.3847386-3-csander@purestorage.com/T/#u
>> .
>> Not sure why it was dropped. But this change is independent, I can
>> rebase it onto the current for-6.15/io_uring-reg-vec if desired.
> 
> Mostly just around the discussion on what we want to guarantee here. I
> do think that patch makes sense, fwiw!
> 
>>> Reviewed-by: Pavel Begunkov <asml.silence@gmail.com>
>>
>> Thanks!
>>
>>>
>>>> Signed-off-by: Caleb Sander Mateos <csander@purestorage.com>
>>>> Suggested-by: Pavel Begunkov <asml.silence@gmail.com>
>>>
>>> Note for the future, it's a good practice to put your sob last.
>>
>> Okay. Is the preferred order of tags documented anywhere? I ran
>> scripts/checkpatch.pl, but it didn't have any complaints.
> 
> I think that one is minor, as it's not reordering with another SOB. Eg
> mine would go below it anyway. But you definitely should always include
> a list of what changed since v1 when posting v2, and so forth. Otherwise
> you need to find the old patch and compare them to see what changed.
> Just put it below the --- line in the email.

Minor, yes. But to answer why, because it's normally chronological.
By default I read it as Suggested-by was added later and not by the
patch author, which nobody cares too much about, but that's why Jens
mentions ordering b/w sob of other people.

-- 
Pavel Begunkov


  parent reply	other threads:[~2025-03-26 22:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 14:39 [PATCH v2] io_uring/net: use REQ_F_IMPORT_BUFFER for send_zc Caleb Sander Mateos
2025-03-26  9:59 ` Pavel Begunkov
2025-03-26 17:01   ` Caleb Sander Mateos
2025-03-26 17:05     ` Jens Axboe
2025-03-26 17:23       ` Caleb Sander Mateos
2025-03-26 17:31         ` Jens Axboe
2025-03-26 22:41           ` Pavel Begunkov
2025-03-26 22:31       ` Pavel Begunkov [this message]
2025-03-26 17:05 ` 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=d1bf1b35-126d-4484-8bb5-0a720717ad78@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=csander@purestorage.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@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