From: David Ahern <dsahern@kernel.org>
To: dccp@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/4] net: wire up support for file_operations->uring_cmd()
Date: Fri, 23 Jun 2023 15:20:25 +0000 [thread overview]
Message-ID: <5c6dc00b-9e25-501f-1497-ce7f67694a0e@kernel.org> (raw)
In-Reply-To: <20230614110757.3689731-2-leitao@debian.org>
On 6/23/23 3:17 AM, Stefan Metzmacher wrote:
>
> I'd like to keep it passed to socket layer, so that sockets could
> implement some extra features in an async fashion.
>
> What about having the function you posted below (and in v3)
> as a default implementation if proto_ops->uring_cmd is NULL?
>
Nothing about this set needs uring_cmd added to proto ops. It adds uring
commands which are wrappers to networking APIs. Let's keep proper APIs
between subsystems.
prev parent reply other threads:[~2023-06-23 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 11:07 [RFC PATCH v2 1/4] net: wire up support for file_operations->uring_cmd() Breno Leitao
2023-06-14 15:15 ` David Ahern
2023-06-19 9:28 ` Pavel Begunkov
2023-06-19 11:20 ` Breno Leitao
2023-06-19 14:18 ` Kanchan Joshi
2023-06-19 16:12 ` David Ahern
2023-06-20 2:09 ` David Ahern
2023-06-23 10:17 ` Stefan Metzmacher
2023-06-23 15:20 ` David Ahern [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 \
--in-reply-to=5c6dc00b-9e25-501f-1497-ce7f67694a0e@kernel.org \
--to=dsahern@kernel.org \
--cc=dccp@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