From: Eric Dumazet <eric.dumazet@gmail.com>
To: Changli Gao <xiaosuo@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH v2] net: avoid the unnecessary kmalloc
Date: Tue, 30 Nov 2010 07:52:01 +0100 [thread overview]
Message-ID: <1291099921.2725.28.camel@edumazet-laptop> (raw)
In-Reply-To: <1291077629-6339-1-git-send-email-xiaosuo@gmail.com>
Le mardi 30 novembre 2010 à 08:40 +0800, Changli Gao a écrit :
> If the old memory allocated by kmalloc() is larger than the new requested,
> pskb_expand_head() doesn't need to allocate a new one, unless the skb->head
> is shared.
>
> Signed-off-by: Changli Gao <xiaosuo@gmail.com>
Seems fine to me, but patch title and changelog are a bit uninformative.
skb head being allocated by kmalloc(), it might be larger than what
actually requested because of discrete kmem caches sizes. Before
reallocating a new skb head, check if the current one has the needed
extra size.
Do this check only if skb head is not shared.
> +
> + if (fastpath &&
> + size + sizeof(struct skb_shared_info) <= ksize(skb->head)) {
> + memmove(skb->head + size, skb_shinfo(skb),
> + offsetof(struct skb_shared_info,
> + frags[skb_shinfo(skb)->nr_frags]));
> + memmove(skb->head + nhead, skb->head,
> + skb_tail_pointer(skb) - skb->head);
> + off = nhead;
> + goto adjust_others;
> + }
> +
I suggest doing the max possible resize at this stage ?
Ie moving skb_shared_info at the edge of memory block.
Maybe its not necessary, and a given skb is not expanded multiple times
in our stack, I dont really know.
next prev parent reply other threads:[~2010-11-30 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-30 0:40 [PATCH v2] net: avoid the unnecessary kmalloc Changli Gao
2010-11-30 6:52 ` Eric Dumazet [this message]
2010-11-30 7:45 ` Changli Gao
2010-11-30 8:16 ` Eric Dumazet
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=1291099921.2725.28.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=xiaosuo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox