[PATCH 0/4] (RESEND) ext3[34] barrier changes
- From: Eric Sandeen <sandeen@xxxxxxxxxx>
- Date: Fri, 16 May 2008 14:02:46 -0500
Sorry, that last send was totally stuffed up w.r.t. mail headers.
So for the benefit of proper cc:'s here it comes again...
A collection of patches to make ext3 & 4 use barriers by
default, and to call blkdev_issue_flush on fsync if they
are enabled.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
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 0/4] (RESEND) ext3[34] barrier changes
- From: Andrew Morton
- [PATCH 4/4] ext4: call blkdev_issue_flush on fsync
- From: Eric Sandeen
- [PATCH 3/4] ext4: enable barriers by default
- From: Eric Sandeen
- [PATCH 2/4] ext3: call blkdev_issue_flush on fsync
- From: Eric Sandeen
- [PATCH 1/4] ext3: enable barriers by default
- From: Eric Sandeen
- Re: [PATCH 0/4] (RESEND) ext3[34] barrier changes
- Prev by Date: Re: [PATCH][PCI]: Introduce pci_find_capability_cached and make MSI use it
- Next by Date: Re: [PATCH] PCI: Correct last two HP entries in the bfsort whitelist
- Previous by thread: [patch 00/14] VM pageout scalability improvements (V7)
- Next by thread: [PATCH 1/4] ext3: enable barriers by default
- Index(es):
Relevant Pages
|
