Block layer still stack abuser?
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.
Rgds
Signature · 5 lines
-- Pierre Ossman Linux kernel, MMC maintainer http://www.kernel.org PulseAudio, core developer http://pulseaudio.org rdesktop, core developer http://www.rdesktop.org
Quoted 6 lines · On Friday February 16, [email protected] 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.
NeilBrown
Quoted 7 lines · Neil Brown
Might this:
http://lkml.org/lkml/2007/2/10/22relate 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.
What are the current blocking issues? There are a lot of users of dm/md double-stacking (e.g. mirroring + multipath) that are in deep trouble currently and could be helped greatly with this patch.
Quoted 4 lines · On Thursday February 22, [email protected] wrote:
Quoted 3 lines · Neil Brown
Might this:
http://lkml.org/lkml/2007/2/10/22
Quoted 8 lines
Quoted 4 lines
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.What are the current blocking issues? There are a lot of users of dm/md double-stacking (e.g. mirroring + multipath) that are in deep trouble currently and could be helped greatly with this patch.
All I know is what is in that mail message that I linked to.
NeilBrown
Quoted 10 lines · Neil Brown
Quoted 7 lines · On Friday February 16, [email protected] 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.
Quoted 9 lines
Might this:
http://lkml.org/lkml/2007/2/10/22relate 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
Signature · 5 lines
-- Pierre Ossman Linux kernel, MMC maintainer http://www.kernel.org PulseAudio, core developer http://pulseaudio.org rdesktop, core developer http://www.rdesktop.org