From: Eric Dumazet <dada1@cosmosbay.com>
To: Linux Netdev List <netdev@vger.kernel.org>,
Corey Minyard <minyard@acm.org>
Subject: [RFC] skb_free_datagram() doing something expensive ?
Date: Wed, 05 Nov 2008 00:02:22 +0100 [thread overview]
Message-ID: <4910D47E.4030004@cosmosbay.com> (raw)
Hi all
I noticed high contention on udp_memory_allocated on a typical VOIP application.
(Now that oprofile correctly runs on my machine :) )
I can see that skb_free_datagram() is :
void skb_free_datagram(struct sock *sk, struct sk_buff *skb)
{
kfree_skb(skb);
sk_mem_reclaim(sk);
}
So each time an UDP packet is received, we must touch udp_memory_allocated
Each time application reads a packet, we call sk_mem_reclaim() and touch again udp_memory_allocated.
Surely this cannot be correct ?
If this is correct, time is to resurrect a patch to make proto->memory_allocated a percpu_counter
or something to have a percpu reserve of say 64 or 128 pages to avoid cache line trashing...
tcp_memory_allocated do not have this problem, since tcp carefully calls sk_mem_reclaim(sk) only on
selected paths, not on fast path.
Thanks
next reply other threads:[~2008-11-04 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 23:02 Eric Dumazet [this message]
2008-11-04 23:41 ` [RFC] skb_free_datagram() doing something expensive ? David Miller
2008-11-05 5:05 ` Eric Dumazet
2008-11-05 9:38 ` David Miller
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=4910D47E.4030004@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=minyard@acm.org \
--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).