From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>, Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH net-next-2.6] inetpeer: lower false sharing effect
Date: Fri, 10 Jun 2011 19:17:06 +0200 [thread overview]
Message-ID: <1307726226.4044.27.camel@edumazet-laptop> (raw)
In-Reply-To: <1307725531.17300.58.camel@schen9-DESK>
Le vendredi 10 juin 2011 à 10:05 -0700, Tim Chen a écrit :
> On Fri, 2011-06-10 at 06:31 +0200, Eric Dumazet wrote:
>
> >
> > Thanks Tim
> >
> > I have some questions for further optimizations.
> >
> > 1) How many different destinations are used in your stress load ?
> > 2) Could you provide a distribution of the size of packet lengthes ?
> > Or maybe the average length would be OK
> >
> >
> >
>
> Actually I have one load generator and one server connected to each
> other via a 10Gb link.
>
> The server is a 40 core 4 socket Westmere-EX machine and the load
> generator is a 12 core 2 socket Westmere-EP machine.
>
> There are 40 memcached daemons on the server each bound to a cpu core
> and listening on a distinctive UDP port. The load generator has 40
> threads, with each thread sending memcache request to a particular UDP
> port.
>
>
> The load generator's memcache request packet has a UDP payload of 25
> bytes. The response packet from the daemon has a UDP payload of 13
> bytes.
>
> The UPD packets on the load generator and server are distributed across
> 16 Tx-Rx queues by hashing on the UDP ports (with slight modification of
> the hash flags of ixgbe).
Excellent, thanks for all these details.
I had the idea some weeks ago to add a fast path to udp_sendmsg() for
small messages [doing the user->kernel copy before RCU route lookup],
that should fit your workload (and other typical UDP workloads)
I'll try to cook patches in next days.
Thanks
prev parent reply other threads:[~2011-06-10 17:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 6:26 [PATCH net-next-2.6] inetpeer: lower false sharing effect Eric Dumazet
2011-06-09 6:31 ` David Miller
2011-06-10 0:03 ` Tim Chen
2011-06-10 3:43 ` David Miller
2011-06-10 4:47 ` Eric Dumazet
2011-06-10 22:33 ` Tim Chen
2011-06-11 0:54 ` Changli Gao
2011-06-11 4:54 ` Eric Dumazet
2011-06-11 6:17 ` Changli Gao
2011-06-11 7:09 ` Andi Kleen
2011-06-10 4:31 ` Eric Dumazet
2011-06-10 17:05 ` Tim Chen
2011-06-10 17:17 ` Eric Dumazet [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=1307726226.4044.27.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tim.c.chen@linux.intel.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