From: "David S. Miller" <davem@redhat.com>
To: tleete@mountain.net
Cc: jgarzik@mandrakesoft.com, linux-kernel@vger.kernel.org
Subject: Re: Hard lockups solved
Date: Mon, 13 Nov 2000 17:14:44 -0800 [thread overview]
Message-ID: <200011140114.RAA14493@pizda.ninka.net> (raw)
In-Reply-To: <3A1073B4.CDCA21DF@mountain.net> (message from Tom Leete on Mon, 13 Nov 2000 18:05:24 -0500)
In-Reply-To: <3A1073B4.CDCA21DF@mountain.net>
Date: Mon, 13 Nov 2000 18:05:24 -0500
From: Tom Leete <tleete@mountain.net>
Your net/ipv4/tcp.c patch from the NE2000 thread cured them even
before I found the hardware fault. Has that patch gone to the
queue? I recommend it.
The bugs I was "fixing" there were due to problems in wait queue
exclusivity nesting. We instead fixed wait queue exclusivity nesting
so it actually worked in test11-pre3, can you see if by itself that
kernel does not show your problems too?
Thanks.
Later,
David S. Miller
davem@redhat.com
-
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:[~2000-11-14 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 23:05 Tom Leete
2000-11-14 1:14 ` David S. Miller [this message]
2000-11-15 4:09 ` Tom Leete
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=200011140114.RAA14493@pizda.ninka.net \
--to=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tleete@mountain.net \
/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
all inboxes | Powered by JetHome®