From: John Ousterhout <ouster@cs.stanford.edu>
To: netdev@vger.kernel.org
Cc: pabeni@redhat.com, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, John Ousterhout <ouster@cs.stanford.edu>
Subject: [PATCH net-next v18 11/15] net: homa: export skb_attempt_defer_free
Date: Fri, 10 Apr 2026 13:03:05 -0700 [thread overview]
Message-ID: <20260410200310.1915-12-ouster@cs.stanford.edu> (raw)
In-Reply-To: <20260410200310.1915-1-ouster@cs.stanford.edu>
This function is now used by Homa.
Signed-off-by: John Ousterhout <ouster@cs.stanford.edu>
---
net/core/skbuff.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/net/core/skbuff.c b/net/core/skbuff.c
index 4657d0245a84..a66209647732 100644
--- a/net/core/skbuff.c
+++ b/net/core/skbuff.c
@@ -7314,6 +7314,7 @@ nodefer: kfree_skb_napi_cache(skb);
if (unlikely(kick))
kick_defer_list_purge(cpu);
}
+EXPORT_SYMBOL(skb_attempt_defer_free);
static void skb_splice_csum_page(struct sk_buff *skb, struct page *page,
size_t offset, size_t len)
--
2.43.0
next prev parent reply other threads:[~2026-04-10 20:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 20:02 [PATCH net-next v18 00/15] Begin upstreaming Homa transport protocol John Ousterhout
2026-04-10 20:02 ` [PATCH net-next v18 01/15] net: homa: define user-visible API for Homa John Ousterhout
2026-04-10 20:02 ` [PATCH net-next v18 02/15] net: homa: create homa_wire.h John Ousterhout
2026-04-10 20:02 ` [PATCH net-next v18 03/15] net: homa: create shared Homa header files John Ousterhout
2026-04-10 20:02 ` [PATCH net-next v18 04/15] net: homa: create homa_pool.h and homa_pool.c John Ousterhout
2026-04-10 20:02 ` [PATCH net-next v18 05/15] net: homa: create homa_peer.h and homa_peer.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 06/15] net: homa: create homa_sock.h and homa_sock.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 07/15] net: homa: create homa_interest.h and homa_interest.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 08/15] net: homa: create homa_rpc.h and homa_rpc.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 09/15] net: homa: create homa_outgoing.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 10/15] net: homa: create homa_utils.c John Ousterhout
2026-04-10 20:03 ` John Ousterhout [this message]
2026-04-10 20:03 ` [PATCH net-next v18 12/15] net: homa: create homa_incoming.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 13/15] net: homa: create homa_timer.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 14/15] net: homa: create homa_plumbing.c John Ousterhout
2026-04-10 20:03 ` [PATCH net-next v18 15/15] net: homa: create Makefile and Kconfig John Ousterhout
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=20260410200310.1915-12-ouster@cs.stanford.edu \
--to=ouster@cs.stanford.edu \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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