From: Jens Axboe <[email protected]>
To: Stefan Metzmacher <[email protected]>
Cc: io-uring <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: For 5.20 or 5.19? net: wire up support for file_operations->uring_cmd()
Date: Tue, 28 Jun 2022 13:26:14 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/28/22 1:09 PM, Stefan Metzmacher wrote:
> Hi Jens,
>
> I'm wondering what happened to you patch passing file_ops->uring_cmd()
> down to socket layers.
>
> It was part of you work in progress branches...
>
> The latest one I found was this:
> https://git.kernel.dk/cgit/linux-block/commit/?h=nvme-passthru-wip.2&id=28b71b85831f5dd303acae12cfdc89e5aaae442b
>
> And this one just having the generic parts were in a separate commit
> https://git.kernel.dk/cgit/linux-block/commit/?h=io_uring-fops.v7&id=c2ba3bd8940ef0b7d1c09adf4bed01acc8171407
> vs.
> https://git.kernel.dk/cgit/linux-block/commit/?h=io_uring-fops.v7&id=542c38da58841097f97f710d1f05055c2f1039f0
>
> I took this:
> https://git.kernel.dk/cgit/linux-block/commit/?h=io_uring-fops.v7&id=c2ba3bd8940ef0b7d1c09adf4bed01acc8171407
> adapted it on top of v5.19-rc4 and removed stuff that was not really needed.
>
> Even if it's not used in tree, it would be good to have uring_cmd hooks in
> struct proto_ops and struct proto, so that out of tree socket implementations
> like my smbdirect driver are able to hook into it.
>
> What do you think?
We need to just finalize a format for this, don't think it'll be too
complicated. But for in-kernel users first and foremost, not for some
out of tree code! I've got various things I'd like to use it for
internally too. For example, returning number of bytes left in a socket
post receive rather than just a flag telling you there's more data.
--
Jens Axboe
prev parent reply other threads:[~2022-06-28 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 19:09 For 5.20 or 5.19? net: wire up support for file_operations->uring_cmd() Stefan Metzmacher
2022-06-28 19:26 ` Jens Axboe [this message]
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] \
[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