From: Samium Gromoff <_deepfire@mail.ru>
To: hahn@physics.mcmaster.ca (Mark Hahn)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.12-ac4 10Mbit NE2k interrupt load kills p166
Date: Mon, 10 Dec 2001 00:50:55 +0300 (MSK) [thread overview]
Message-ID: <200112092150.fB9Lot906422@vegae.deep.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0112091619190.6428-100000@coffee.psychology.mcmaster.ca> from "Mark Hahn" at Dec 09, 2001 04:21:06 PM
" Mark Hahn wrote:"
>
> > > I had an AMD K6 200 with an ISA NE2K card whan I started using Linux...
> ...
> > such broken behaviour.
>
> the only thing broken is that the nic is pitiful and eats CPU.
>
> > i`ve made a further research and discovered the fact that
> > ping -l 99999999 - does not corrupt the sound
> > ping -l 99999999 -s 256 - does not corrupt the sound
> > ping -l 99999999 -s 512 - significantly corrupts the sound
> > ping -l 99999999 -s 16384 - heavily corrupts the sound with stalls
>
> right, so more fragmentation-assembly increases the CPU load,
> no surprise there.
damn, i have a mtu of 1500 and i dont quite see abt what frag/reassembly
are you talking about while the problems start to pop out on _256_ bytes
large packets (yes 256+smth like 32 or more)
>
> > My thinking is that if 2.0 was better than 2.4 in this case, we definitely
> > need to find out why was it so and use its strong side.
>
> your particular case is not worth fixing; I doubt it applies to machines
> with modern CPU, modern dram, modern nics.
>
>
but why? 2.0 is ok, 2.4 is broken.
look: we have 2.0 serving NIC interrupts more efficintly than 2.4, and you
say that we even dont need to know _why_ its so!?
why do you neglect the possible improvement of that case?
cheers, Samium Gromoff
next parent reply other threads:[~2001-12-09 21:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0112091619190.6428-100000@coffee.psychology.mcmaster.ca>
2001-12-09 21:50 ` Samium Gromoff [this message]
2001-12-09 22:18 ` 2.4.12-ac4 10Mbit NE2k interrupt load kills p166 Alan Cox
2001-12-09 23:04 Samium Gromoff
-- strict thread matches above, loose matches on Subject: below --
2001-10-25 19:30 Samium Gromoff
2001-10-25 20:01 ` Benjamin LaHaise
2001-10-25 20:22 ` Alan Cox
2001-10-25 20:40 ` Martin Josefsson
2001-10-25 20:54 ` Alan Cox
2001-10-25 20:52 ` Benjamin LaHaise
2001-12-08 21:58 ` Samium Gromoff
2001-12-10 10:54 ` vda
2001-10-27 15:22 ` Jussi Laako
2001-10-27 15:50 ` Samium Gromoff
2001-10-25 20:21 ` Alan Cox
2001-10-25 21:19 ` Urban Widmark
2001-10-26 2:57 ` Samium Gromoff
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=200112092150.fB9Lot906422@vegae.deep.net \
--to=_deepfire@mail.ru \
--cc=hahn@physics.mcmaster.ca \
--cc=linux-kernel@vger.kernel.org \
/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