public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: MP M <mageshmp2003@yahoo.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: help in TCP checksum offload , TSO and zero copy
Date: Fri, 27 Feb 2004 07:12:20 +0100	[thread overview]
Message-ID: <20040227061220.GC7785@alpha.home.local> (raw)
In-Reply-To: <20040226185219.70474.qmail@web21407.mail.yahoo.com>

On Thu, Feb 26, 2004 at 10:52:19AM -0800, MP M wrote:
> ttcp-t: 216442880 bytes in 299.34 real seconds =
> 706.13 KB/sec +++
^^^^^^^^^

It's obvious that you have other problems, because lack of hardware
checksum won't lead to such abysmal performance. You should start
with *real* traffic, and not with I/O bound tools such as tar.
For instance, you'd better use "dd if=/dev/zero bs=64k count=4000"
(or use /dev/urandom) to generate some data if you absolutely need
some. But here, I'm fairly certain that your disk is *THE* problem.
I could easily reach the Gb/s with a P3/1G on a crappy dl2k, so I
don't see why you could not to it on better hardware.

Oh, and BTW, check your cable (netstat -i) to see if you get drops
or errors. You can also have poor wires which lead to frequent
retransmits. GigE uses all 4 pairs (8 wires), so a cable which
works well on FastEth is not necessarily OK on GigE.

Cheers,
Willy


  parent reply	other threads:[~2004-02-27  6:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-26 18:52 help in TCP checksum offload , TSO and zero copy MP M
2004-02-27  5:00 ` Stuart Young
2004-02-27  6:12 ` Willy Tarreau [this message]
2004-02-27 15:46 ` Jesse Pollard

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=20040227061220.GC7785@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=mageshmp2003@yahoo.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