From: Jan Killius <jkillius@arcor.de>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@oss.sgi.com, davem@davemloft.net, jgarzik@pobox.com
Subject: Re: r8169: page allocation failure
Date: Sun, 17 Oct 2004 09:40:28 +0200 [thread overview]
Message-ID: <200410170940.28350.jkillius@arcor.de> (raw)
In-Reply-To: <20041016214903.GC21849@electric-eye.fr.zoreil.com>
On Saturday 16 October 2004 23:49, Francois Romieu wrote:
> Jan Killius <jkillius@arcor.de> :
> > On Saturday 16 October 2004 23:04, Jan Killius wrote:
> > > > - what is the current transfer rate and is it better/worse w/o TSO ?
> > >
> > > I'm getting almost the same with both settings ~405Mbit/s.
>
> Roughly the same CPU usage ?
I have tested the maximum transfer rate with netperf here makes TSO no
difference in cpu usage.
>
> > > > - which cpu/disk system are there within the (?) 128Mo box ?
> > >
> > > Athlon XP 1600+ the disk is a Maxtor 6Y060L0 gets with hdparm 42.76
> > > MB/s
> >
> > ups forget to say the ram size 512MB FSB333 DDR RAM
>
> I did not notice it first but the bi/bo columns of the vmstat output
> are mostly null. Assuming this is a single session ftp transfer, what ftp
> software does the r8169 based system run ?
vsftpd
>
> Pure curiosity: can you issue a test+vmstat with a blowfish scp to see if
> TSO makes a difference for your setup when the system is not disk-limited ?
without TSO(1628MB 11.1MB/s 02:27):
1 0 166388 27716 332 97264 0 0 12300 0 12323 7616 37 45 0
18
1 0 166388 26108 332 99804 0 0 12880 4 12727 7975 39 52 0 9
1 0 166388 24612 336 102796 0 0 12720 0 12590 7900 38 48 0
15
1 0 166388 27644 332 100420 0 0 8232 0 8845 5517 27 30 2 40
1 2 166388 27648 368 101024 0 0 11240 4 11705 7546 35 44 0
21
1 0 166388 26592 384 102536 0 0 12372 56 13001 8409 34 55 0
11
1 2 166388 25192 388 104424 0 0 12504 0 12428 7700 43 44 0
13
1 0 166388 25488 436 104424 0 0 10844 48 10900 6868 34 40 0
27
0 1 166388 25076 452 105200 0 0 11928 0 11949 7412 36 48 0
17
1 1 166388 24412 456 106108 0 0 12172 60 12225 7612 39 45 0
15
with TSO(1628MB 12.8MB/s 02:07):
1 0 166340 27672 376 120056 0 0 13740 0 11879 2041 36 58 6
0
1 0 166340 25352 384 122288 0 0 13968 4 12148 2072 41 55 3
1
1 0 166340 22924 376 124692 0 0 14028 0 12174 2050 36 60 4
0
1 0 166340 20896 368 126696 0 0 13644 0 11859 2016 39 54 7
0
0 0 166340 30792 352 116856 0 0 13328 0 11646 2013 36 56 8
0
1 0 166340 28440 332 119280 0 0 14156 0 12343 2063 37 59 2
2
1 3 166340 28120 348 119556 0 0 11936 4 10527 2329 32 49 4
15
1 3 166340 27728 456 119920 0 0 12152 4 10549 2516 31 52 0
17
2 0 166340 26600 492 120588 0 0 12216 208 10347 2274 37 48 0
16
0 2 166340 24344 572 122760 0 0 13900 0 11937 2217 37 58 0
5
>
> --
> Ueimor
--
Jan
next prev parent reply other threads:[~2004-10-17 7:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 18:04 r8169: page allocation failure Jan Killius
2004-10-16 19:08 ` Francois Romieu
[not found] ` <200410162134.22727.jkillius@arcor.de>
[not found] ` <20041016195435.GA21317@electric-eye.fr.zoreil.com>
2004-10-16 20:12 ` Jan Killius
2004-10-16 20:48 ` Francois Romieu
2004-10-16 21:04 ` Jan Killius
2004-10-16 21:23 ` Jan Killius
2004-10-16 21:49 ` Francois Romieu
2004-10-17 7:40 ` Jan Killius [this message]
2004-10-17 10:39 ` Francois Romieu
2004-10-17 7:47 ` Herbert Xu
2004-10-17 9:08 ` Herbert Xu
2004-10-17 10:13 ` Jan Killius
2004-10-20 5:30 ` David S. Miller
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=200410170940.28350.jkillius@arcor.de \
--to=jkillius@arcor.de \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.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).