> > I do expect that buffer cache flushes on the client side > > actually hit at least the underlying device's write cache (nearly sync > > writes on the server side), > > With the FUA patch (which finally has been accepted into Linux proper), > this will happen; when the client side does an explicit buffer cache > flush, this will be finished with an FUA call, which will cause an > fsync() on the server side.
Are they mapped to "barriers"? And can I now safely buffer all writes until the barrier is/FUA is invoked and force them on the platters? Unfortunately the client does not tell you if it will be using barriers so that you can use this buffering. Folkert van Heusden -- MultiTail รจ uno flexible tool per seguire di logfiles e effettuazione di commissioni. Feltrare, provedere da colore, merge, 'diff-view', etc. http://www.vanheusden.com/multitail/ ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Nbd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nbd-general
