From: Eric Dumazet <eric.dumazet@gmail.com>
To: Felix Fietkau <nbd@nbd.name>, netdev@vger.kernel.org
Cc: davem@davemloft.net, brouer@redhat.com, fw@strlen.de, pabeni@redhat.com
Subject: Re: [PATCH v3] net: use bulk free in kfree_skb_list
Date: Mon, 25 Mar 2019 02:27:14 -0700 [thread overview]
Message-ID: <5d973ed2-1915-a87d-d10f-6a0f68240ac0@gmail.com> (raw)
In-Reply-To: <20190325091456.54285-1-nbd@nbd.name>
On 03/25/2019 02:14 AM, Felix Fietkau wrote:
> Since we're freeing multiple skbs, we might as well use bulk free to save a
> few cycles. Use the same conditions for bulk free as in napi_consume_skb.
>
> Signed-off-by: Felix Fietkau <nbd@nbd.name>
> ---
> v3: reorder checks to prevent skb double unref
> v2: call kmem_cache_free_bulk once the skb array is full instead of
> falling back to kfree_skb
> net/core/skbuff.c | 40 ++++++++++++++++++++++++++++++++++++----
> 1 file changed, 36 insertions(+), 4 deletions(-)
>
> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
> index 2415d9cb9b89..ca0308485669 100644
> --- a/net/core/skbuff.c
> +++ b/net/core/skbuff.c
> @@ -666,12 +666,44 @@ EXPORT_SYMBOL(kfree_skb);
>
> void kfree_skb_list(struct sk_buff *segs)
> {
> - while (segs) {
> - struct sk_buff *next = segs->next;
> + struct sk_buff *next = segs;
> + void *skbs[16];
> + int n_skbs = 0;
>
> - kfree_skb(segs);
> - segs = next;
> + while ((segs = next) != NULL) {
> + next = segs->next;
> +
> + if (segs->fclone != SKB_FCLONE_UNAVAILABLE) {
> + kfree_skb(segs);
> + continue;
> + }
> +
> + if (!skb_unref(segs))
> + continue;
> +
> + trace_kfree_skb(segs, __builtin_return_address(0));
> +
> + /* drop skb->head and call any destructors for packet */
> + skb_release_all(segs);
> +
> +#ifdef CONFIG_SLUB
> + /* SLUB writes into objects when freeing */
> + prefetchw(segs);
> +#endif
This is done too late :
You should probably either remove this prefetchw()
or do it before reading segs->next at the beginning of the loop.
> +
> + skbs[n_skbs++] = segs;
> +
> + if (n_skbs < ARRAY_SIZE(skbs))
> + continue;
> +
> + kmem_cache_free_bulk(skbuff_head_cache, n_skbs, skbs);
> + n_skbs = 0;
> }
> +
> + if (!n_skbs)
> + return;
> +
> + kmem_cache_free_bulk(skbuff_head_cache, n_skbs, skbs);
> }
> EXPORT_SYMBOL(kfree_skb_list);
>
>
next prev parent reply other threads:[~2019-03-25 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 9:14 [PATCH v3] net: use bulk free in kfree_skb_list Felix Fietkau
2019-03-25 9:27 ` Eric Dumazet [this message]
2019-03-25 15:49 ` Jesper Dangaard Brouer
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=5d973ed2-1915-a87d-d10f-6a0f68240ac0@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=nbd@nbd.name \
--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;
as well as URLs for NNTP newsgroup(s).