[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a56dfcf00708092151q2c485fb9o328db1ae9802e591@mail.gmail.com>
Date: Fri, 10 Aug 2007 04:51:13 +0000
From: "Dan Merillat" <dan.merillat@...il.com>
To: "Neil Brown" <neilb@...e.de>
Cc: "Eric Sandeen" <sandeen@...deen.net>,
"Satyam Sharma" <satyam.sharma@...il.com>,
"Alan Cox" <alan@...rguk.ukuu.org.uk>,
"Andrea Arcangeli" <andrea@...e.de>,
"Matt Mackall" <mpm@...enic.com>,
"Rene Herman" <rene.herman@...il.com>,
"Ray Lee" <ray-lk@...rabbit.org>, "Bodo Eggert" <7eggert@....de>,
"Jeremy Fitzhardinge" <jeremy@...p.org>,
"Jesper Juhl" <jesper.juhl@...il.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"William Lee Irwin III" <wli@...omorphy.com>,
"David Chinner" <dgc@....com>,
"Arjan van de Ven" <arjan@...radead.org>
Subject: Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...?
On 8/1/07, Neil Brown <neilb@...e.de> wrote:
> No, this does not use indefinite stack.
>
> loop will schedule each request to be handled by a kernel thread, so
> requests to 'loop' are serialised, never stacked.
>
> In 2.6.22, generic_make_request detects and serialises recursive calls,
> so unlimited recursion is not possible there either.
Is that saying "before 2.6.22, a read/write on a deeply layered device
would use a lot of stack?"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists