From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Neil Brown <neilb@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Block layer still stack abuser?
Date: Thu, 22 Feb 2007 06:44:37 +0100 [thread overview]
Message-ID: <45DD2DC5.2020108@drzeus.cx> (raw)
In-Reply-To: <17885.1120.437885.35438@notabene.brown>
Neil Brown wrote:
> On Friday February 16, drzeus-list@drzeus.cx wrote:
>
>> I was wondering if the block layer has been changed into a more serialized
>> manner yet? I've been trying to google this, but so far no luck. I know there
>> was some talk about removing the stack based approach, but I can't find any
>> information about where this went.
>>
>> If it is currently fixed, a pointer to from which version would be nice.
>>
>
> Might this:
> http://lkml.org/lkml/2007/2/10/22
>
> relate to your question?
> If you are talking about stacking block device (via dm or md), then a
> patch to fix this in in -mm but there are or were some potential
> issues in dm that seem to be holding it up.
>
>
Yes, I am. I know there has been general work to reduce stack usage here
and there, but the final suggested solution was to serialize all the
block subsystems so that only one was present on the stack at any given
time.
I was constantly hitting this problem a few years ago when I was running
md+xfs+nfs. The fix was in -mm back then as well. ;)
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
prev parent reply other threads:[~2007-02-22 5:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 11:57 Block layer still stack abuser? Pierre Ossman
2007-02-22 2:48 ` Neil Brown
2007-02-22 3:44 ` Christoph Hellwig
2007-02-22 3:46 ` Neil Brown
2007-02-22 5:44 ` Pierre Ossman [this message]
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=45DD2DC5.2020108@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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