netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	willemb@google.com, fw@strlen.de,
	Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 0/3] net: skbuff: cache one skb_ext for use by GRO
Date: Tue, 14 Feb 2023 19:43:52 -0800	[thread overview]
Message-ID: <20230215034355.481925-1-kuba@kernel.org> (raw)

New offload features may require attaching skb_ext to every packet.
PSP support adds fields to the skb in the patches published by Google:
  https://github.com/google/psp
Since PSP is designed to be stateless on the device we need to carry
metadata thru the stack and perform validation at the socket layer.

Upstream we'll likely try to use skb_ext to place such metadata.

Lower the cost of allocation of skb_ext by caching a single object
per core.

Obviously the PSP support isn't upstream yet, but I think that this
should also help the TC fallback, and any other skb_ext uses people
may come up with in the meantime.

Jakub Kicinski (3):
  net: skb: carve the allocation out of skb_ext_add()
  net: skbuff: cache one skb_ext for use by GRO
  net: create and use NAPI version of tc_skb_ext_alloc()

 .../ethernet/mellanox/mlx5/core/en/rep/tc.c   |   2 +-
 .../net/ethernet/mellanox/mlx5/core/en_tc.c   |   2 +-
 include/linux/skbuff.h                        |   1 +
 include/net/pkt_cls.h                         |   9 ++
 net/core/skbuff.c                             | 131 ++++++++++++++----
 5 files changed, 117 insertions(+), 28 deletions(-)

-- 
2.39.1


             reply	other threads:[~2023-02-15  3:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15  3:43 Jakub Kicinski [this message]
2023-02-15  3:43 ` [PATCH net-next 1/3] net: skb: carve the allocation out of skb_ext_add() Jakub Kicinski
2023-02-15  3:43 ` [PATCH net-next 2/3] net: skbuff: cache one skb_ext for use by GRO Jakub Kicinski
2023-02-15  8:41   ` Paolo Abeni
2023-02-15 17:45     ` Jakub Kicinski
2023-02-15 18:08       ` Alexander Lobakin
2023-02-15 19:08         ` Paolo Abeni
2023-02-15 15:37   ` Edward Cree
2023-02-15 16:17     ` Alexander Lobakin
2023-02-15 17:52       ` Jakub Kicinski
2023-02-15 18:01         ` Alexander Lobakin
2023-02-15 18:20           ` Jakub Kicinski
2023-02-16 12:04             ` Alexander Lobakin
2023-02-15  3:43 ` [PATCH net-next 3/3] net: create and use NAPI version of tc_skb_ext_alloc() Jakub Kicinski
2023-02-15 16:50   ` Jamal Hadi Salim
2023-02-15 17:03     ` Jiri Pirko
2023-02-15 18:36       ` Jamal Hadi Salim
2023-02-15 17:35     ` Jakub Kicinski
2023-02-15 18:38       ` Jamal Hadi Salim

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=20230215034355.481925-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemb@google.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).