| To: | Jens Axboe <axboe@xxxxxxx> |
|---|---|
| Subject: | Re: XFS, 4K stacks, and Red Hat |
| From: | Andi Kleen <ak@xxxxxxx> |
| Date: | Sun, 17 Jul 2005 03:57:00 +0200 |
| Cc: | Andi Kleen <ak@xxxxxxx>, Nathan Scott <nathans@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20050716191217.GE1568@suse.de> |
| References: | <Pine.LNX.4.58.0507071102460.4766@chaos.egr.duke.edu> <42CD4D38.1090703@xfs.org> <Pine.LNX.4.58.0507071142550.4766@chaos.egr.duke.edu> <20050708043740.GB1679@frodo> <42D3F44B.308@strike.wu-wien.ac.at> <20050713015626.GD980@frodo> <p73eka31mkv.fsf@bragg.suse.de> <20050716191217.GE1568@suse.de> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
> Sounds like a possible solution for the problem. 4kb stack is never > going to be completely enough for some block layer stacking setups. > Would need some careful work, I don't want to see each and every io > pushed to a worker for processing and potentially incurring 2 context > switches per io. Well, it's better than crashing. Also I think it could be a problem even with 8k stacks when the stacking setups become more complex. -Andi |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS, 4K stacks, and Red Hat, Jens Axboe |
|---|---|
| Next by Date: | Re: deadlocks on ENOSPC, ASANO Masahiro |
| Previous by Thread: | Re: XFS, 4K stacks, and Red Hat, Jens Axboe |
| Next by Thread: | Re: XFS corruption on move from xscale to i686, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |