mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Herbert <therbert@google.com>
To: David Miller <davem@davemloft.net>
Cc: yanmin_zhang@linux.intel.com, bhutchings@solarflare.com,
	andi@firstfloor.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, herbert@gondor.apana.org.au,
	jesse.brandeburg@intel.com, shemminger@vyatta.com
Subject: Re: [RFC v2: Patch 1/3] net: hand off skb list to other cpu to submit  to upper layer
Date: Fri, 13 Mar 2009 14:59:55 -0700	[thread overview]
Message-ID: <65634d660903131459m645eb468y3ad850a1fd56d447@mail.gmail.com> (raw)
In-Reply-To: <20090313.140217.143696945.davem@davemloft.net>

>
> If the hash is good is will distribute the load properly.
>
> If the NIC is sophisticated enough (Sun's Neptune chipset is)
> you can even group interrupt distribution by traffic type
> and even bind specific ports to interrupt groups.
>
> I really detest all of these software hacks that add overhead
> to solve problems the hardware can solve for us.
>

I appreciate this philosophy, but unfortunately I don't have the
luxury of working with a NIC that solves these problems.  The reality
may be that we're trying to squeeze performance out of crappy hardware
to scale on multi-core.  Left alone we couldn't get the stack to
scale, but with these "destable hacks" we've gotten 3X or so
improvement in packets per second across both our dumb 1G and 10G
NICs.  These gains have translated into tangible application
performance gains, so we'll probably continue to have interest in this
area of development at least for the foreseeable future.

  reply	other threads:[~2009-03-13 22:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11  8:53 Zhang, Yanmin
2009-03-11 11:13 ` Andi Kleen
2009-03-12  8:16   ` Zhang, Yanmin
2009-03-12 14:08     ` Ben Hutchings
2009-03-13  6:43       ` Zhang, Yanmin
2009-03-13 17:06         ` Tom Herbert
2009-03-13 18:51           ` David Miller
2009-03-13 21:01             ` Tom Herbert
2009-03-13 22:10               ` Ben Hutchings
2009-03-13 22:15                 ` Stephen Hemminger
     [not found]             ` <65634d660903131358h765bef64y6a0f1b0db7400f6f@mail.gmail.com>
2009-03-13 21:02               ` David Miller
2009-03-13 21:59                 ` Tom Herbert [this message]
2009-03-13 22:19                   ` David Miller
2009-03-13 23:58                     ` Herbert Xu
2009-03-14  0:24                     ` Tom Herbert
2009-03-14  1:53                       ` Andi Kleen
2009-03-14  2:19                       ` David Miller
2009-03-14 13:19                         ` Herbert Xu
2009-03-14 18:15                         ` Tom Herbert
2009-03-14 18:45                           ` David Miller
2009-03-16 16:53                             ` Tom Herbert
2009-03-14  1:51               ` Andi Kleen
2009-03-16  3:20           ` Zhang, Yanmin
2009-03-12 14:34     ` Andi Kleen
2009-03-13  9:06       ` Zhang, Yanmin

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=65634d660903131459m645eb468y3ad850a1fd56d447@mail.gmail.com \
    --to=therbert@google.com \
    --cc=andi@firstfloor.org \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=yanmin_zhang@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

all inboxes | Powered by JetHome®