From: Frank de Lange <frank@unternet.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related?
Date: Fri, 12 Jan 2001 01:28:39 +0100 [thread overview]
Message-ID: <20010112012839.A11091@unternet.org> (raw)
In-Reply-To: <20010110223015.B18085@unternet.org> <3A5D9D87.8A868F6A@uow.edu.au> <20010111201819.B3269@unternet.org> <3A5E0849.EB428D70@mandrakesoft.com>
In-Reply-To: <3A5E0849.EB428D70@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Thu, Jan 11, 2001 at 02:23:53PM -0500
On Thu, Jan 11, 2001 at 02:23:53PM -0500, Jeff Garzik wrote:
> Just out of curiosity, if you boot a Linux 2.4.0 kernel with the
> "noapic" command line option, does behavior improve?
For the curious, here's a summary of some tests I did:
apic, 2 cpu's, no smp affinity -> network hangs under load
apic, maxcpus=1, no smp affinity -> network hangs under load
apic, 2 cpu's, smp affinity for all irq's on CPU1 -> network hangs under load
noapic, 2 cpu's, no smp affinity -> NO HANG, WORKSFORME
Quick and dirty conclusion: as soon as the apic comes in to play, things get
messy...
ps. load == 2 simultaneous nfs cp -rd <big_directory> sessions and streaming
esd audio over the network
Cheers//Frank
--
WWWWW _______________________
## o o\ / Frank de Lange \
}# \| / \
##---# _/ <Hacker for Hire> \
#### \ +31-320-252965 /
\ frank@unternet.org /
-------------------------
[ "Omnis enim res, quae dando non deficit, dum habetur
et non datur, nondum habetur, quomodo habenda est." ]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-12 0:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 21:30 QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related? Frank de Lange
2001-01-10 22:21 ` Manfred Spraul
2001-01-10 22:29 ` Frank de Lange
2001-01-10 22:40 ` Frank de Lange
2001-01-11 11:48 ` Andrew Morton
2001-01-11 15:22 ` Frank de Lange
2001-01-11 16:55 ` Frank de Lange
2001-01-11 19:18 ` Frank de Lange
[not found] ` <3A5E0849.EB428D70@mandrakesoft.com>
2001-01-12 0:28 ` Frank de Lange [this message]
2001-01-12 11:40 ` Andrew Morton
2001-01-12 15:06 ` Frank de Lange
2001-01-12 15:36 ` Frank de Lange
2001-01-11 19:38 ` Frank de Lange
2001-01-11 19:49 ` Frank de Lange
2001-01-11 21:09 ` Frank de Lange
2001-01-11 21:47 ` Jeff Garzik
2001-01-11 21:53 ` Frank de Lange
2001-01-12 14:35 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-01-12 16:53 Manfred Spraul
2001-01-12 17:02 ` David Woodhouse
2001-01-12 17:16 Manfred Spraul
2001-01-12 17:33 ` Frank de Lange
2001-01-12 17:51 ` Manfred Spraul
2001-01-12 18:25 ` Frank de Lange
2001-01-12 19:04 ` Manfred Spraul
2001-01-12 19:07 ` Frank de Lange
2001-01-12 19:21 ` Frank de Lange
2001-01-12 19:33 ` Manfred Spraul
2001-01-12 19:52 ` Frank de Lange
2001-01-12 19:59 ` Linus Torvalds
2001-01-12 20:03 ` Ingo Molnar
2001-01-14 0:13 ` Roeland Th. Jansen
2001-01-14 0:23 ` Frank de Lange
2001-01-12 20:05 ` Frank de Lange
2001-01-12 21:21 ` Frank de Lange
[not found] <20010112165104.A22465@unternet.org>
2001-01-16 19:23 ` Maciej W. Rozycki
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=20010112012839.A11091@unternet.org \
--to=frank@unternet.org \
--cc=jgarzik@mandrakesoft.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.