From: Frank de Lange <frank@unternet.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Manfred Spraul <manfred@colorfullife.com>,
dwmw2@infradead.org, linux-kernel@vger.kernel.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: QUESTION: Network hangs with BP6 and 2.4.x kernels, hardwarerelated?
Date: Sat, 13 Jan 2001 01:19:57 +0100 [thread overview]
Message-ID: <20010113011957.A29757@unternet.org> (raw)
In-Reply-To: <20010112214642.A27809@unternet.org> <Pine.LNX.4.10.10101121610050.8097-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.10.10101121610050.8097-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Fri, Jan 12, 2001 at 04:15:37PM -0800
On Fri, Jan 12, 2001 at 04:15:37PM -0800, Linus Torvalds wrote:
> On Fri, 12 Jan 2001, Frank de Lange wrote:
> >
> > Gentleman, this (the patch to 8390.c) seems to fix the problem.
>
> The problem with this patch is that anybody with a slow ISA ne2000 clone
> will basically have absolutely _horrible_ interrupt latency because we
> hold the irq lock over some quite expensive operations.
>
> The spin_lock_irqsave() is absolutely my preferred fix, and if I remember
> correctly this is in fact how some early 2.1.x code fixed the ne2000
> driver when the original irq scalability stuff happened (for some time
> during development we did not have a working "disable_irq()" AT ALL
> because the irq-disabling counters etc logic hadn't been done).
And that's the patch I meant... Manfred's
spin_lock_irqsave/spin_unlock_irqrestore based one, not my
(spin_lock_irq/spin_unlock_irq) based patch. That is also the one I'm running
now.
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-13 0:20 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 17:16 QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related? 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 20:11 ` QUESTION: Network hangs with BP6 and 2.4.x kernels, hardwarerelated? Manfred Spraul
2001-01-12 20:16 ` Frank de Lange
2001-01-12 20:19 ` Ingo Molnar
2001-01-12 20:26 ` Frank de Lange
2001-01-12 20:31 ` Ingo Molnar
2001-01-12 20:35 ` Frank de Lange
2001-01-12 20:37 ` Ingo Molnar
2001-01-12 20:46 ` David Woodhouse
2001-01-12 20:46 ` Frank de Lange
2001-01-12 20:51 ` Ingo Molnar
2001-01-12 21:05 ` Frank de Lange
2001-01-15 2:00 ` Jorge Nerin
2001-01-13 0:15 ` Linus Torvalds
2001-01-13 0:19 ` Frank de Lange [this message]
2001-01-13 0:29 ` Alan Cox
2001-01-12 20:54 ` Manfred Spraul
2001-01-12 21:07 ` Frank de Lange
2001-01-12 21:31 ` Manfred Spraul
2001-01-12 23:50 ` Alan Cox
2001-01-12 21:21 ` QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related? Frank de Lange
2001-01-12 23:35 ` QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware Alan Cox
2001-01-13 0:06 ` Manfred Spraul
2001-01-13 0:36 ` Linus Torvalds
2001-01-13 0:48 ` Frank de Lange
2001-01-13 0:56 ` Linus Torvalds
2001-01-13 1:27 ` Frank de Lange
2001-01-13 1:51 ` Manfred Spraul
2001-01-13 2:11 ` Frank de Lange
2001-01-13 1:49 ` Jens Axboe
2001-01-13 2:12 ` Andrew Morton
2001-01-13 2:48 ` Linus Torvalds
2001-01-13 3:24 ` Andrew Morton
2001-01-13 12:37 ` Russell King
2001-01-13 15:18 ` Call for testers: ne2k-pci and io apic (was: Re: QUESTION: Network hangs with BP6...) Manfred Spraul
2001-01-13 23:55 ` Manfred Spraul
2001-01-14 0:18 ` Call for testers: ne2k-pci and io apic J . A . Magallon
2001-01-14 0:23 ` Call for testers: ne2k-pci and io apic (was: Re: QUESTION: Network hangs with BP6...) J . A . Magallon
2001-01-14 2:14 ` Call for testers: ne2k-pci and io apic J . A . Magallon
2001-01-15 16:15 ` QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware Zdenek Kabelac
2001-01-13 1:38 ` Manfred Spraul
2001-01-13 2:10 ` Andrew Morton
2001-01-12 17:49 ` Alan Cox
2001-01-12 18:08 ` Manfred Spraul
2001-01-12 18:16 ` Ingo Molnar
2001-01-12 18:45 ` Manfred Spraul
2001-01-12 18:48 ` Ingo Molnar
2001-01-12 18:28 ` Linus Torvalds
2001-01-12 23:27 ` Alan Cox
2001-01-13 0:35 ` Linus Torvalds
2001-01-13 0:43 ` Alan Cox
2001-01-13 0:48 ` Linus Torvalds
2001-01-12 19:05 ` Frank de Lange
2001-01-12 20:04 ` Linus Torvalds
2001-01-15 14:36 ` Roeland Th. Jansen
2001-01-12 22:03 ` Latest status of IDE patches from Andre Jeff Nguyen
[not found] <20010112213217.E26555@unternet.org>
2001-01-12 20:34 ` QUESTION: Network hangs with BP6 and 2.4.x kernels, hardwarerelated? Ingo Molnar
2001-01-12 20:39 ` Frank de Lange
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=20010113011957.A29757@unternet.org \
--to=frank@unternet.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mingo@elte.hu \
--cc=torvalds@transmeta.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