From: Matt Mackall <mpm@selenic.com>
To: Andi Kleen <ak@suse.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
John B?ckstrand <sandos@home.se>,
davem@davemloft.net
Subject: Re: [PATCH] netpoll can lock up on low memory.
Date: Fri, 5 Aug 2005 14:42:24 -0700 [thread overview]
Message-ID: <20050805214224.GW8074@waste.org> (raw)
In-Reply-To: <20050805212610.GA8266@wotan.suse.de>
On Fri, Aug 05, 2005 at 11:26:10PM +0200, Andi Kleen wrote:
> On Fri, Aug 05, 2005 at 01:01:57PM -0700, Matt Mackall wrote:
> > The netpoll philosophy is to assume that its traffic is an absolute
> > priority - it is better to potentially hang trying to deliver a panic
> > message than to give up and crash silently.
>
> That would be ok if netpoll was only used to deliver panics. But
> it is not. It delivers all messages, and you cannot hang the
> kernel during that. Actually even for panics it is wrong, because often
> it is more important to reboot in a panic than (with a panic timeout)
> to actually deliver the panic. That's needed e.g. in a failover cluster.
>
> If that was the policy it would be a quite dumb one and make netpoll
> totally unsuitable for production use. I hope it is not.
Suggest you rip __GFP_NOFAIL out of JBD before complaining about this.
> Dave, can you please apply the timeout patch anyways?
Yes, let's go right over the maintainer's objections almost
immediately after he chimes into the thread. I'll spare the list the
colorful language this inspires.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2005-08-05 21:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42F347D2.7000207@home.se.suse.lists.linux.kernel>
2005-08-05 11:45 ` lockups with netconsole on e1000 on media insertion Andi Kleen
2005-08-05 12:44 ` John Bäckstrand
2005-08-05 13:49 ` Steven Rostedt
2005-08-05 13:55 ` Andi Kleen
2005-08-05 14:10 ` Steven Rostedt
2005-08-05 14:14 ` Andi Kleen
2005-08-05 14:27 ` Steven Rostedt
2005-08-05 14:36 ` David S. Miller
2005-08-05 15:02 ` Steven Rostedt
2005-08-05 14:36 ` [PATCH] netpoll can lock up on low memory Steven Rostedt
2005-08-05 20:01 ` Matt Mackall
2005-08-05 20:57 ` Steven Rostedt
2005-08-05 21:28 ` Matt Mackall
2005-08-06 0:23 ` Steven Rostedt
2005-08-06 1:53 ` Matt Mackall
2005-08-06 2:32 ` Steven Rostedt
2005-08-06 7:30 ` Daniel Phillips
2005-08-06 7:58 ` Ingo Molnar
2005-08-06 23:10 ` Matt Mackall
2005-08-06 9:46 ` David S. Miller
2005-08-06 9:57 ` Steven Rostedt
2005-08-06 12:09 ` John Bäckstrand
2005-08-07 5:40 ` Matt Mackall
2005-08-05 21:26 ` Andi Kleen
2005-08-05 21:42 ` Matt Mackall [this message]
2005-08-05 21:51 ` Andi Kleen
2005-08-06 1:16 ` Matt Mackall
2005-08-06 0:30 ` Steven Rostedt
2005-08-06 7:45 ` Ingo Molnar
2005-08-06 11:29 ` Andi Kleen
2005-08-07 21:12 ` lockups with netconsole on e1000 on media insertion John Bäckstrand
2005-08-08 2:29 ` Steven Rostedt
2005-08-05 20:12 ` Matt Mackall
2005-08-05 21:56 ` Andi Kleen
2005-08-05 23:20 ` Matt Mackall
2005-08-05 23:51 ` Andi Kleen
2005-08-06 1:22 ` Matt Mackall
2005-08-06 1:37 ` Daniel Phillips
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=20050805214224.GW8074@waste.org \
--to=mpm@selenic.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sandos@home.se \
/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