Re: [RFC][PATCH] block: Isolate the buffer cache in it's own mappings.

On Sun, Oct 21, 2007 at 02:24:46PM +1000, Nick Piggin wrote:
> On Saturday 20 October 2007 07:27, Eric W. Biederman wrote:
> > Currently only 
> > metadata is more or less in sync with the contents of /dev/hda1.
> 
> It either is or it isn't, right? And it is, isn't it? (at least
> for the common filesystems).

It is not true for XFS - it's metadata is not in sync with /dev/<block>
at all as all the cached metadata is kept in a different address space
to the raw block device.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group
-
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:
  • [PATCH resend] ramdisk: fix zeroed ramdisk pages on memory pressure
    • From: Christian Borntraeger <[email protected]>
  • Re: [RFC][PATCH] block: Isolate the buffer cache in it's own mappings.
    • From: Andrew Morton <[email protected]>
  • Re: [RFC][PATCH] block: Isolate the buffer cache in it's own mappings.
    • From: [email protected] (Eric W. Biederman)
  • Re: [RFC][PATCH] block: Isolate the buffer cache in it's own mappings.
    • From: Nick Piggin <[email protected]>

• Prev by Date: Re: rt73usb: support for wireless in Kohjinsha subnotebook
• Next by Date: Re: BUG in: Driver core: convert block from raw kobjects to core devices
• Previous by thread: Re: [RFC][PATCH] block: Isolate the buffer cache in it's own mappings.
• Next by thread: Re: [RFC][PATCH] block: Isolate the buffer cache in it's own mappings.
• 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]