Re: [PATCH 2/9]: Reduce Log I/O latency

> FWIW from a "real time" database POV this seems to make sense to me...
> in fact, we probably rely on filesystem metadata way too much
> (historically it's just "worked".... although we do seem to get issues
> on ext3).

For that case you really would need priority inheritance: any metadata
IO on behalf or blocking a process needs to use the process' block IO 
priority.

David's change just fixes a limited set of cases, but breaks others.

-Andi
-
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 2/9]: Reduce Log I/O latency
    • From: David Chinner <[email protected]>

• References:
  • Re: [PATCH 2/9]: Reduce Log I/O latency
    • From: Andi Kleen <[email protected]>
  • Re: [PATCH 2/9]: Reduce Log I/O latency
    • From: David Chinner <[email protected]>
  • Re: [PATCH 2/9]: Reduce Log I/O latency
    • From: Stewart Smith <[email protected]>

• Prev by Date: Re: [PATCH RFC] [1/9] Core module symbol namespaces code and intro.
• Next by Date: Re: MMC/SDIO sub-system: block mode versus byte mode
• Previous by thread: Re: [PATCH 2/9]: Reduce Log I/O latency
• Next by thread: Re: [PATCH 2/9]: Reduce Log I/O latency
• 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]