Re: [RFC][PATCH 4/4] deadlock prevention for NBD

Hi!

> Limit each request to 1 page, so that the request throttling also limits the
> number of in-flight pages and force the IO scheduler to NOOP as anything else
> doesn't make sense anyway.

I'd like to understand why it breaks with other schedulers before
merging this. Maybe the failure in NOOP is just harder to trigger?

							Pavel

-- 
Thanks for all the (sleeping) penguins.
-
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/

---

• References:
  • [RFC][PATCH 0/4] VM deadlock prevention -v4
    • From: Peter Zijlstra <[email protected]>
  • [RFC][PATCH 4/4] deadlock prevention for NBD
    • From: Peter Zijlstra <[email protected]>

• Prev by Date: Re: [PATCH] BLOCK: Make it possible to disable the block layer
• Next by Date: Re: cpufreq stops working after a while
• Previous by thread: [RFC][PATCH 4/4] deadlock prevention for NBD
• Next by thread: [RFC][PATCH 2/4] SROG allocator
• 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]