From: Jakub Kicinski <kuba@kernel.org>
To: zijianzhang@bytedance.com
Cc: netdev@vger.kernel.org, edumazet@google.com,
willemdebruijn.kernel@gmail.com, cong.wang@bytedance.com,
xiaochun.lu@bytedance.com
Subject: Re: [PATCH net-next v4 0/3] net: A lightweight zero-copy notification
Date: Mon, 13 May 2024 17:48:42 -0700 [thread overview]
Message-ID: <20240513174842.2af7d7f3@kernel.org> (raw)
In-Reply-To: <20240513211755.2751955-1-zijianzhang@bytedance.com>
On Mon, 13 May 2024 21:17:52 +0000 zijianzhang@bytedance.com wrote:
> Original title is "net: socket sendmsg MSG_ZEROCOPY_UARG".
>
> Original notification mechanism needs poll + recvmmsg which is not
> easy for applcations to accommodate. And, it also incurs unignorable
> overhead including extra system calls and usage of socket optmem.
Hi, as described in:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html
we close the net-next tree for the duration of the merge window.
We will not be applying any -next patches for the next 2 weeks.
Feel free to continue posting new versions once you get feedback,
but please switch to posting as RFC.
--
pw-bot: defer
next prev parent reply other threads:[~2024-05-14 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 21:17 [PATCH net-next v4 0/3] net: A lightweight zero-copy notification zijianzhang
2024-05-13 21:17 ` [PATCH net-next v4 1/3] selftests: fix OOM problem in msg_zerocopy selftest zijianzhang
2024-05-13 21:17 ` [PATCH net-next v4 2/3] sock: add MSG_ZEROCOPY notification mechanism based on msg_control zijianzhang
2024-05-14 3:40 ` kernel test robot
2024-05-13 21:17 ` [PATCH net-next v4 3/3] selftests: add MSG_ZEROCOPY msg_control notification test zijianzhang
2024-05-14 0:48 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-28 21:21 [PATCH net-next v4 0/3] net: A lightweight zero-copy notification zijianzhang
2024-05-29 13:59 ` Willem de Bruijn
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=20240513174842.2af7d7f3@kernel.org \
--to=kuba@kernel.org \
--cc=cong.wang@bytedance.com \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xiaochun.lu@bytedance.com \
--cc=zijianzhang@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).