* Alan Cox <[EMAIL PROTECTED]> wrote:
> You won't bisect obscure timing triggered problems, and the _p users
> are almost all for hardware where performance doesn't matter one iota
> (eg CMOS).
actually, people have, and i have too. But i agree that io_delay=none
would be stupid now, and would probably be stupid in v2.6.26 too.
i also have a debug patch that counts the number of _p() API uses and
prints a stacktrace (once per bootup) if it occurs [wrote it 2 weeks
ago] - so i agree with you that we can do this more gradually and more
intelligently. As long as it does not turn into a BKL situation. It's
2008 in a day and we've still got the NFS client code running under the
BKL - quite ridiculous IMO.
Ingo
--
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/
