Re: RFC: i386: kill !4KSTACKS
From: Vladimir Saveliev (vs_at_namesys.com)
Date: 06/08/05
- Previous message: Paul Mackerras: "[PATCH] ppc64: Fix PER_LINUX32 behaviour"
- In reply to: Adrian Bunk: "RFC: i386: kill !4KSTACKS"
- Next in thread: Vladimir Saveliev: "Re: RFC: i386: kill !4KSTACKS"
- Reply: Vladimir Saveliev: "Re: RFC: i386: kill !4KSTACKS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Adrian Bunk <bunk@stusta.de> Date: Wed, 08 Jun 2005 16:00:16 +0400
Hello
On Wed, 2005-06-08 at 01:27, Adrian Bunk wrote:
> 4Kb kernel stacks are the future on i386, and it seems the problems it
> initially caused are now sorted out.
>
> I'd like to:
> - get a patch into the next -mm that unconditionally enables 4KSTACKS
> - if there won't be new reports of breakages, send a patch to
> completely remove !4KSTACKS for 2.6.13 or 2.6.14
>
> The only drawback is that REISER4_FS does still depend on !4KSTACKS.
> I told Hans back in March that this has to be changed.
> Is there any ETA until that all issues with 4Kb kernel stacks in Reiser4
> will be resolved?
>
yes, it should be ready to the end of this week.
> If not people using Reiser4 might have to decide whether to switch the
> filesystem or the architecture...
>
> cu
> Adrian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Paul Mackerras: "[PATCH] ppc64: Fix PER_LINUX32 behaviour"
- In reply to: Adrian Bunk: "RFC: i386: kill !4KSTACKS"
- Next in thread: Vladimir Saveliev: "Re: RFC: i386: kill !4KSTACKS"
- Reply: Vladimir Saveliev: "Re: RFC: i386: kill !4KSTACKS"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
