mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: Bart Alewijnse <scarfboy@gmail.com>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: gigabit trouble
Date: Sat, 31 Jul 2004 23:18:36 +0200	[thread overview]
Message-ID: <20040731231836.A31121@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <b71082d804073112512bbd82e2@mail.gmail.com>; from scarfboy@gmail.com on Sat, Jul 31, 2004 at 09:51:27PM +0200

Bart Alewijnse <scarfboy@gmail.com> :
[...]
> of habit as something kernely ages back wanted it. But is there really no
> point to preempting in a server?

I don't know: I have no URL for the figures at hand.

> Right, both computers now run 2.6.8-rc2-mm1. It's better. Roughly
> speaking, the top *benchmark* speeds, rouding slightly up, are:
> udp: 33MB/s (using ~26Kints) one way, 12MB/s (9Kints/s) the other, 
> tcp: 22MB/s (16Kints)one way, 12MB/s (9Kints/s) the other. 
> 
> (The 9Kints ca be 12 when the packet size is 1K or 2K)

Can you give a try to a napi version of the module (it is a compile-time
option) ?
You may want higher {r/w}mem_max as well as renicing ksoftirqd with
a strongly < 0 value on the celeron client.

> Oddly enough, the slow direction is sending from my new computer
> (XP1700, KT333, 1GB ram) to my old (both running linux and the
> mentioned kernel). I'm fairly sure this is due to the fact that my

The r8169 driver has been reported to be faster on Rx than on Tx so your
observation makes sense.

[...]
> I guess I'll have to settle for this. I'm just annoyed that the 'giga'
> is basically a joke,  especially on my setup.

It should be possible to make things slightly better for the celeron box
as a client. I'll cook up a patch.

Would you be kind enough to do some ftp transfer test where the celeron
box retrieves data and send the 'vmstat 1' output of the client during
the test ?

--
Ueimor

  reply	other threads:[~2004-07-31 21:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29 16:45 Bart Alewijnse
2004-07-29 17:29 ` Erik Mouw
2004-07-29 19:04 ` Francois Romieu
2004-07-29 22:41   ` Bart Alewijnse
2004-07-30 15:35     ` Bart Alewijnse
     [not found]     ` <b71082d804073008157cf1d6c0@mail.gmail.com>
     [not found]       ` <20040730205412.A15669@electric-eye.fr.zoreil.com>
2004-07-30 21:03         ` Bart Alewijnse
2004-07-30 21:41           ` Francois Romieu
2004-07-31 19:51             ` Bart Alewijnse
2004-07-31 21:18               ` Francois Romieu [this message]
2004-08-01 19:03                 ` Bart Alewijnse
     [not found]                   ` <b71082d804080219476103bd47@mail.gmail.com>
2004-08-03  7:48                     ` Francois Romieu

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=20040731231836.A31121@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=scarfboy@gmail.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®