From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: bhutchings@solarflare.com, pstaszewski@itcare.pl, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ipv4: PKTINFO doesnt need dst reference
Date: Wed, 09 Nov 2011 23:03:03 +0100 [thread overview]
Message-ID: <1320876183.3272.8.camel@edumazet-laptop> (raw)
In-Reply-To: <20111109.163708.2156133928191684256.davem@davemloft.net>
Le mercredi 09 novembre 2011 à 16:37 -0500, David Miller a écrit :
> From: Eric Dumazet <eric.dumazet@gmail.com>
> Date: Wed, 09 Nov 2011 18:24:35 +0100
>
> > [PATCH net-next] ipv4: IP_PKTINFO doesnt need dst reference
> >
> > When a socket uses IP_PKTINFO notifications, we currently force a dst
> > reference for each received skb. Reader has to access dst to get needed
> > information (rt_iif & rt_spec_dst) and must release dst reference.
> >
> > We also forced a dst reference if skb was put in socket backlog, even
> > without IP_PKTINFO handling. This happens under stress/load.
> >
> > We can instead store the needed information in skb->cb[], so that only
> > softirq handler really access dst, improving cache hit ratios.
> >
> > This removes two atomic operations per packet, and false sharing as
> > well.
> >
> > On a benchmark using a mono threaded receiver (doing only recvmsg()
> > calls), I can reach 720.000 pps instead of 570.000 pps.
> >
> > IP_PKTINFO is typically used by DNS servers, and any multihomed aware
> > UDP application.
> >
> > Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
>
> Looks good, if it compiles I'll push it out to net-next :-)
Arg :( I cross my fingers :)
BTW, on my bnx2x adapter, even small UDP frames use more than PAGE_SIZE
bytes :
skb->truesize=4352 len=26 (payload only)
Truesize being now more precise, we hit badly the shared
udp_memory_allocated, even with single frames.
I wonder if we shouldnt increase SK_MEM_QUANTUM a bit to avoid
ping/pong...
-#define SK_MEM_QUANTUM ((int)PAGE_SIZE)
+#define SK_MEM_QUANTUM ((int)PAGE_SIZE * 2)
next prev parent reply other threads:[~2011-11-09 22:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 15:57 Linux Route Cache performance tests Paweł Staszewski
2011-11-06 17:29 ` Eric Dumazet
2011-11-06 18:28 ` Paweł Staszewski
2011-11-06 18:48 ` Eric Dumazet
2011-11-06 19:20 ` Paweł Staszewski
2011-11-06 19:38 ` Eric Dumazet
2011-11-06 20:25 ` Paweł Staszewski
2011-11-06 21:26 ` Eric Dumazet
2011-11-06 21:57 ` Paweł Staszewski
2011-11-06 23:08 ` Eric Dumazet
2011-11-07 8:36 ` Paweł Staszewski
2011-11-07 9:08 ` Eric Dumazet
2011-11-07 9:16 ` Eric Dumazet
2011-11-07 22:12 ` Paweł Staszewski
2011-11-07 13:42 ` Ben Hutchings
2011-11-07 14:33 ` Eric Dumazet
2011-11-09 17:24 ` [PATCH net-next] ipv4: PKTINFO doesnt need dst reference Eric Dumazet
2011-11-09 21:37 ` David Miller
2011-11-09 22:03 ` Eric Dumazet [this message]
2011-11-10 0:29 ` [PATCH net-next] bnx2x: reduce skb truesize by 50% Eric Dumazet
2011-11-10 15:05 ` Eilon Greenstein
2011-11-10 15:27 ` Eric Dumazet
2011-11-10 16:27 ` Eilon Greenstein
2011-11-10 16:45 ` Eric Dumazet
2011-11-13 18:53 ` Eilon Greenstein
2011-11-13 19:42 ` Eric Dumazet
2011-11-13 20:08 ` Eilon Greenstein
2011-11-13 22:00 ` Eric Dumazet
2011-11-14 5:08 ` David Miller
2011-11-14 6:25 ` Eric Dumazet
2011-11-14 15:57 ` Eric Dumazet
2011-11-14 19:21 ` 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=1320876183.3272.8.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pstaszewski@itcare.pl \
/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