From: Manfred Spraul <manfred@colorfullife.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Jamie Lokier <jamie@shareable.org>, Adrian Bunk <bunk@fs.tum.de>,
linux-kernel@vger.kernel.org, peter_daum@t-online.de
Subject: Re: [2.4 patch] fix CONFIG_X86_L1_CACHE_SHIFT
Date: Mon, 08 Sep 2003 21:45:41 +0200 [thread overview]
Message-ID: <3F5CDC65.6060409@colorfullife.com> (raw)
In-Reply-To: <20030908172416.GA21226@gtf.org>
Jeff Garzik wrote:
>Yes; I've lost the specific context of the thread, but I have been
>working on MWI/cacheline size issues along with IvanK for a while.
>
>
Context: Peter experiences very bad network performance with 2.4.22 - it
looks like 99% packet drop or something like that. The packet drop
disappears if CONFIG_L1_CACHE_SHIFT is set to 7 (i.e. 128 byte cache
line size). 2.4.21 works.
The network cards are some kind of atm cards. Several systems are
affected - at least Pentium II and PPro systems.
Peter: what's the exact brand and nic driver that you use? Could you try
to figure out what exactly breaks? I'd use "ping -f -s 1500", perhaps
together with "tcpdump -s 1500 -x" on both ends.
--
Manfred
next prev parent reply other threads:[~2003-09-08 19:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-07 20:36 [2.4 patch] fix CONFIG_X86_L1_CACHE_SHIFT Manfred Spraul
2003-09-08 14:20 ` Adrian Bunk
2003-09-08 17:07 ` Jamie Lokier
2003-09-08 17:24 ` Jeff Garzik
2003-09-08 19:45 ` Manfred Spraul [this message]
2003-09-09 14:49 ` Peter Daum
[not found] <20030907195557.GK14436@fs.tum.de.suse.lists.linux.kernel>
2003-09-07 20:30 ` Andi Kleen
2003-09-07 21:39 ` Dave Jones
2003-09-08 8:15 ` Peter Daum
[not found] ` <Pine.LNX.4.30.0309072228110.9987-100000@swamp.bayern.net.suse.lists.linux.kernel>
2003-09-07 21:57 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2003-09-07 19:55 Adrian Bunk
2003-09-07 20:59 ` Peter Daum
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=3F5CDC65.6060409@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=bunk@fs.tum.de \
--cc=jamie@shareable.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter_daum@t-online.de \
/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