netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	therbert@google.com, netdev@vger.kernel.org
Subject: Re: small RPS cache for fragments?
Date: Tue, 17 May 2011 22:11:43 +0100	[thread overview]
Message-ID: <1305666703.2848.49.camel@bwh-desktop> (raw)
In-Reply-To: <1305666050.2691.4.camel@edumazet-laptop>

On Tue, 2011-05-17 at 23:00 +0200, Eric Dumazet wrote:
> Le mardi 17 mai 2011 à 16:49 -0400, David Miller a écrit :
> > From: Tom Herbert <therbert@google.com>
> > Date: Tue, 17 May 2011 13:02:25 -0700
> > 
> > > I like it!  And this sounds like the sort of algorithm that NICs might
> > > be able to implement to solve the UDP/RSS unpleasantness, so even
> > > better.
> > 
> > Actually, I think it won't work.  Even Linux emits fragments last to
> > first, so we won't see the UDP header until the last packet where it's
> > no longer useful.
> > 
> > Back to the drawing board. :-/
> 
> Well, we could just use the iph->id in the rxhash computation for frags.

But then each datagram lands on a different CPU, and reordering is
liable to happen far more often than it does now.

> At least all frags of a given datagram should be reassembled on same
> cpu, so we get RPS (but not RFS)

You could still do RPS with just IP addresses (same as RSS using
Toeplitz hashes).

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.


  parent reply	other threads:[~2011-05-17 21:11 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 18:33 small RPS cache for fragments? David Miller
2011-05-17 20:02 ` Tom Herbert
2011-05-17 20:17   ` Rick Jones
2011-05-17 20:41     ` Rick Jones
2011-05-17 20:49   ` David Miller
2011-05-17 21:00     ` Eric Dumazet
2011-05-17 21:10       ` David Miller
2011-05-17 21:13         ` Rick Jones
2011-05-17 21:13         ` Ben Hutchings
2011-05-17 21:26           ` David Miller
2011-05-17 21:40             ` Rick Jones
2011-05-17 21:27           ` Eric Dumazet
2011-05-17 21:11       ` Rick Jones
2011-05-17 21:11       ` Ben Hutchings [this message]
2011-05-17 21:27     ` Tom Herbert
2011-05-17 21:28       ` David Miller
2011-05-17 23:59     ` Changli Gao
2011-05-18  6:37       ` David Miller
2011-05-17 20:14 ` Eric Dumazet
2011-05-17 20:47   ` David Miller
2011-05-17 21:44   ` Andi Kleen
2011-05-17 21:52     ` Eric Dumazet
2011-05-17 22:03       ` Andi Kleen
2011-05-17 21:44 ` David Miller
2011-05-17 21:48   ` Andi Kleen
2011-05-17 21:50     ` David Miller
2011-05-17 22:06       ` Andi Kleen
2011-05-17 22:42       ` Rick Jones
2011-05-24 20:01 ` David Miller
2011-05-24 21:38   ` Rick Jones
2011-06-04 20:29     ` David Miller
2011-06-06 17:08       ` Rick Jones
2011-06-06 17:15         ` Eric Dumazet
2011-06-06 18:06           ` Rick Jones
2011-06-06 19:23           ` David Miller
2011-06-06 19:22         ` David Miller
2011-06-06 20:05           ` Rick Jones
2011-06-06 21:06             ` Jay Vosburgh
2011-06-06 21:40               ` David Miller
2011-06-06 22:49                 ` Chris Friesen

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=1305666703.2848.49.camel@bwh-desktop \
    --to=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=therbert@google.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;
as well as URLs for NNTP newsgroup(s).