From: Jakub Kicinski <kuba@kernel.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
bjorn@kernel.org, magnus.karlsson@intel.com,
maciej.fijalkowski@intel.com, jonathan.lemon@gmail.com,
sdf@fomichev.me, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com, joe@dama.to,
willemdebruijn.kernel@gmail.com, bpf@vger.kernel.org,
netdev@vger.kernel.org, Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next v3] net: xsk: introduce XDP_MAX_TX_BUDGET set/getsockopt
Date: Sat, 21 Jun 2025 07:43:24 -0700 [thread overview]
Message-ID: <20250621074324.63ab381d@kernel.org> (raw)
In-Reply-To: <CAL+tcoA=KQCLdthH3VXPhd-z=sieKQu_xOPgQEzxdy0Mtnycag@mail.gmail.com>
On Fri, 20 Jun 2025 08:17:48 +0800 Jason Xing wrote:
> > Jason, I think some additions to Documentation/ and quantification of
> > the benefits would be needed as well.
>
> Got it.
>
> #1 Documentation. I would add one small section 'XDP_MAX_TX_BUDGET
> setsockopt' in Documentation/networking/af_xdp.rst.
>
> #2 quantification
> It's really hard to do so mainly because of various stacks implemented
> in the user-space. AF_XDP is providing a fundamental mechanism only
> and its upper layer is prosperous.
Sorry for the awkward phrase. By "quantification of the benefits"
I meant what performance improvement you have seen from increasing
this "budget".
next prev parent reply other threads:[~2025-06-21 14:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 9:04 [PATCH net-next v3] net: xsk: introduce XDP_MAX_TX_BUDGET set/getsockopt Jason Xing
2025-06-19 13:53 ` Willem de Bruijn
2025-06-19 23:53 ` Jason Xing
2025-06-20 0:02 ` Jason Xing
2025-06-20 13:43 ` Willem de Bruijn
2025-06-20 13:58 ` Willem de Bruijn
2025-06-20 14:37 ` Jason Xing
2025-06-20 22:21 ` Willem de Bruijn
2025-06-19 15:09 ` Jakub Kicinski
2025-06-20 0:17 ` Jason Xing
2025-06-20 13:50 ` Willem de Bruijn
2025-06-20 15:03 ` Jason Xing
2025-06-20 22:24 ` Willem de Bruijn
2025-06-21 0:40 ` Jason Xing
2025-06-21 14:43 ` Jakub Kicinski [this message]
2025-06-22 0:05 ` Jason Xing
2025-06-20 14:25 ` Stanislav Fomichev
2025-06-20 16:30 ` Jason Xing
2025-06-20 16:47 ` Stanislav Fomichev
2025-06-20 17:46 ` Jason Xing
2025-06-23 14:18 ` Stanislav Fomichev
2025-06-23 23:54 ` Jason Xing
2025-06-24 0:48 ` Stanislav Fomichev
2025-06-24 2:47 ` Jason Xing
2025-06-20 22:20 ` Willem de Bruijn
2025-06-21 1:06 ` Jason Xing
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=20250621074324.63ab381d@kernel.org \
--to=kuba@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=joe@dama.to \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=willemdebruijn.kernel@gmail.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.