From: Robert Love <rml@tech9•net>
To: "David S. Miller" <davem@redhat•com>
Cc: torvalds@transmeta•com, dane@aiinet•com, shmulik.hen@intel•com,
bonding-devel@lists•sourceforge.net,
bonding-announce@lists•sourceforge.net, netdev@oss•sgi.com,
linux-kernel@vger•kernel.org, linux-net@vger•kernel.org,
mingo@redhat•com, kuznet@ms2•inr.ac.ru
Subject: Re: BUG or not? GFP_KERNEL with interrupts disabled.
Date: 27 Mar 2003 14:52:11 -0500 [thread overview]
Message-ID: <1048794730.775.14.camel@localhost> (raw)
In-Reply-To: <20030327.113933.123322481.davem@redhat.com>
On Thu, 2003-03-27 at 14:39, David S. Miller wrote:
> I hadn't considered this, good idea. I'm trying this out right now.
I hope it works. I have a sinking feeling we call it some places that
may have interrupts disabled...
> Someone should backport the might_sleep() stuff to 2.4.x, it's very
> useful.
Would be nice, but for the maximum effect we need kernel preemption
(which keeps track of atomicity via preempt_count). I doubt we want to
go there for 2.4.
Robert Love
next prev parent reply other threads:[~2003-03-27 19:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B785392832ED71192AE00D0B7B0D75B539668@aimail.aiinet.com>
2003-03-27 19:02 ` BUG or not? GFP_KERNEL with interrupts disabled Dan Eble
2003-03-27 19:08 ` Linus Torvalds
2003-03-27 19:10 ` David S. Miller
2003-03-27 19:22 ` Linus Torvalds
2003-03-27 19:39 ` David S. Miller
2003-03-27 19:52 ` Robert Love [this message]
2003-03-27 19:53 ` David S. Miller
2003-03-27 20:55 ` David S. Miller
2003-03-27 21:29 ` David S. Miller
[not found] <E791C176A6139242A988ABA8B3D9B38A01085638@hasmsx403.iil.intel.com>
2003-03-27 13:32 ` shmulik.hen
2003-03-27 13:43 ` David S. Miller
2003-03-27 14:11 ` Trond Myklebust
2003-03-27 14:12 ` David S. Miller
2003-03-27 17:22 ` Linus Torvalds
2003-03-27 17:55 ` David S. Miller
2003-03-27 18:04 ` Linus Torvalds
2003-03-27 18:07 ` David S. Miller
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=1048794730.775.14.camel@localhost \
--to=rml@tech9$(echo .)net \
--cc=bonding-announce@lists$(echo .)sourceforge.net \
--cc=bonding-devel@lists$(echo .)sourceforge.net \
--cc=dane@aiinet$(echo .)com \
--cc=davem@redhat$(echo .)com \
--cc=kuznet@ms2$(echo .)inr.ac.ru \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-net@vger$(echo .)kernel.org \
--cc=mingo@redhat$(echo .)com \
--cc=netdev@oss$(echo .)sgi.com \
--cc=shmulik.hen@intel$(echo .)com \
--cc=torvalds@transmeta$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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