Re: [PATCH 00/14] Concurrent Page Cache

On Sun, 28 Jan 2007, Peter Zijlstra wrote:

> With Nick leading the way to getting rid of the read side of the tree_lock,
> this work continues by breaking the write side of said lock.

Could we get the read side in separately from the write side? I think I 
get the read side but the write side still looks scary to me and 
introduces new ways of locking. Ladder locking?
 
> Aside from breaking MTD this version of the concurrent page cache seems
> rock solid on my dual core x86_64 box.

What exactly is the MTD doing and how does it break?
-
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 00/14] Concurrent Page Cache
    • From: Peter Zijlstra <[email protected]>

• References:
  • [PATCH 00/14] Concurrent Page Cache
    • From: Peter Zijlstra <[email protected]>

• Prev by Date: Re: slab: start_cpu_timer/cache_reap CONFIG_HOTPLUG_CPU problems
• Next by Date: [PATCH] Fix compilation problem with spider network driver on 2.6.20-rc6-mm2
• Previous by thread: [PATCH 05/14] mm: lockless pagecache lookups
• Next by thread: Re: [PATCH 00/14] Concurrent Page Cache
• 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]