| To: | Michael Lampe <Michael.Lampe@xxxxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: 2.4.25 & xfs & ide write barriers |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Mon, 1 Mar 2004 09:19:24 +1100 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <403E0A7A.3040505@xxxxxxxxxxxxxxxxxxxxx> |
| References: | <403E0A7A.3040505@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.3i |
On Thu, Feb 26, 2004 at 04:02:18PM +0100, Michael Lampe wrote: > fs/xfs/linux/xfs_buf.c already has > > #ifdef RQ_WRITE_ORDERED > if (flush) > set_bit(BH_Ordered_Flush, &bufferlist[cnt-1]->b_state); > #endif > > in _pagebuf_page_io. > > Is this all I need (I already have applied the ide write barrier patch) > to safely use disk write back caching? > (which IDE write barrier patch is that, out of curiousity?) This stuff is untested by anyone here at SGI, so YMMV. It is also not going to work in the presence of unwritten extents (which were implemented after this change), some additional code would be needed there. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: are xfs working on amd64 ?, Andrew B. Panphiloff |
|---|---|
| Next by Date: | Re: block size & 2.6 kernel, Nathan Scott |
| Previous by Thread: | 2.4.25 & xfs & ide write barriers, Michael Lampe |
| Next by Thread: | [Bug 296] Kernel 2.4.22 xfs_force_shutdown line 4049 of file xfs_bmap.c, bugzilla-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |