netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: jheffner@psc.edu
Cc: netdev@oss.sgi.com, herbert@gondor.apana.org.au
Subject: Re: [PATCH 0/9]: TCP: The Road to Super TSO
Date: Wed, 08 Jun 2005 14:49:06 -0700 (PDT)	[thread overview]
Message-ID: <20050608.144906.77057282.davem@davemloft.net> (raw)
In-Reply-To: <200506081740.11292.jheffner@psc.edu>

From: John Heffner <jheffner@psc.edu>
Subject: Re: [PATCH 0/9]: TCP: The Road to Super TSO
Date: Wed, 8 Jun 2005 17:40:10 -0400

> On Tuesday 07 June 2005 12:08 am, David S. Miller wrote:
> > Some folks, notable the S2IO guys, get performance degradation
> > from the Super TSO v2 patch (they get it from the first version
> > as well).  It's a real pain to spot what causes such things
> > in such a huge patch... so I started splitting things up in
> > a very fine grained manner so we can catch regressions more
> > precisely.
> 
> I'm curious about the details of this.  Is there decreased performance 
> relative to current TSO?  Relative to no TSO?  Sending to just one receiver 
> or many, and is it receiver limited?

The receiver is limited in their tests.  No current generation systems
can fill a 10gbit pipe fully, especially at 1500 byte MTU.

Performance went down, with both TSO enabled and disabled, compared to
not having the patches applied.

That's why I'm going through this entire exercise of doing things one
piece at a time.

  reply	other threads:[~2005-06-08 21:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07  4:08 [PATCH 0/9]: TCP: The Road to Super TSO David S. Miller
2005-06-07  4:16 ` [PATCH 1/9]: " David S. Miller
2005-06-07  4:17 ` [PATCH 2/9]: " David S. Miller
2005-06-07  4:17 ` [PATCH 3/9]: " David S. Miller
2005-06-07  4:18 ` [PATCH 4/9]: " David S. Miller
2005-06-07  4:19 ` [PATCH 5/9]: " David S. Miller
2005-06-07  4:20 ` [PATCH 6/9]: " David S. Miller
2005-06-07  4:21 ` [PATCH 7/9]: " David S. Miller
2005-06-07  4:22 ` [PATCH 8/9]: " David S. Miller
2005-06-07  4:23 ` [PATCH 9/9]: " David S. Miller
2005-06-07  4:56 ` [PATCH 0/9]: " Stephen Hemminger
2005-06-07  5:51   ` David S. Miller
2005-06-08 21:40 ` John Heffner
2005-06-08 21:49   ` David S. Miller [this message]
2005-06-08 22:10     ` Herbert Xu
2005-06-09  4:55       ` Leonid Grossman
2005-06-08 22:19     ` Leonid Grossman
  -- strict thread matches above, loose matches on Subject: below --
2005-06-09  4:30 Leonid Grossman

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=20050608.144906.77057282.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jheffner@psc.edu \
    --cc=netdev@oss.sgi.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).