Re: [PATCH] disable PREEMPT_BKL per default

 On Tue, Oct 18, Arjan van de Ven wrote:

> > Its disabled in our configs.
> 
> any particular reason for that? Eg are there any known or suspected
> issues with this?

I have no idea. Maybe it was the general 'preempt isnt right' move.

-- 
short story of a lazy sysadmin:
 alias appserv=wotan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] disable PREEMPT_BKL per default
  - From: Ingo Molnar <[email protected]>

References:
- 2.6.14-rc4-mm1
  - From: Andrew Morton <[email protected]>
- [PATCH] disable PREEMPT_BKL per default
  - From: Olaf Hering <[email protected]>
- Re: [PATCH] disable PREEMPT_BKL per default
  - From: Arjan van de Ven <[email protected]>
- Re: [PATCH] disable PREEMPT_BKL per default
  - From: Olaf Hering <[email protected]>
- Re: [PATCH] disable PREEMPT_BKL per default
  - From: Arjan van de Ven <[email protected]>

Prev by Date: Re: [PATCH] mark __init code noinline to stop erroneous inclusions
Next by Date: Re: [PATCH] Adaptive read-ahead v4
Previous by thread: Re: [PATCH] disable PREEMPT_BKL per default
Next by thread: Re: [PATCH] disable PREEMPT_BKL per default
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]