From: Felix Fietkau <nbd@nbd.name>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
Florian Westphal <fw@strlen.de>
Subject: Re: [PATCH net-next] net: use bulk free in kfree_skb_list
Date: Sun, 24 Mar 2019 17:54:06 +0100 [thread overview]
Message-ID: <c19a38ef-762f-1f39-04da-c3bff074fb44@nbd.name> (raw)
In-Reply-To: <20190324123130.7b86487a@carbon>
On 2019-03-24 12:31, Jesper Dangaard Brouer wrote:
> On Sun, 24 Mar 2019 07:58:34 +0100
> Felix Fietkau <nbd@nbd.name> 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>
>
> Thanks for working on this, it's been on my todo list for a very long
> time. I just discussed this with Florian at NetDevconf.
No problem. It was showing up on my perf traces while improving
mac80211/mt76 performance, so I decided to deal with it now :)
>> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
>> index 2415d9cb9b89..ec030ab7f1e7 100644
>> --- a/net/core/skbuff.c
>> +++ b/net/core/skbuff.c
>> @@ -666,12 +666,39 @@ 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 (!skb_unref(segs))
>> + continue;
>> +
>> + if (segs->fclone != SKB_FCLONE_UNAVAILABLE ||
>> + n_skbs >= ARRAY_SIZE(skbs)) {
>
> You could call kmem_cache_free_bulk() here and reset n_skbs=0.
Sure, good idea. I'll send v2 shortly.
- Felix
prev parent reply other threads:[~2019-03-24 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 6:58 [PATCH net-next] net: use bulk free in kfree_skb_list Felix Fietkau
2019-03-24 11:31 ` Jesper Dangaard Brouer
2019-03-24 16:54 ` Felix Fietkau [this message]
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=c19a38ef-762f-1f39-04da-c3bff074fb44@nbd.name \
--to=nbd@nbd.name \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
/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).