[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 14 Mar 2011 02:47:48 +0100 (CET)
From: "Indan Zupancic" <indan@....nu>
To: "Theodore Tso" <tytso@....EDU>
Cc: "Jeff Garzik" <jeff@...zik.org>,
"Ric Wheeler" <ricwheeler@...il.com>,
"Arnd Bergmann" <arnd@...db.de>, "Sage Weil" <sage@...dream.net>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
"Aneesh Kumar K. V" <aneesh.kumar@...ux.vnet.ibm.com>,
"Jonathan Nieder" <jrnieder@...il.com>, akpm@...ux-foundation.org,
linux-api@...r.kernel.org, mtk.manpages@...il.com,
viro@...iv.linux.org.uk, hch@....de, l@...per.es
Subject: Re: [PATCH v3] introduce sys_syncfs to sync a single file system
On Mon, March 14, 2011 02:37, Theodore Tso wrote:
>
> On Mar 13, 2011, at 9:31 PM, Indan Zupancic wrote:
>
>> The new syscall works on only one fd too. The behaviour of the proposed
>> syncfs and an extended sync_file_range is exactly the same.
>
> No, it's quite different. One syncs the entire file system; sync_file_range
> requests that the pages associated with a file be pushed to disk --- it says
> nothing about the metadata associated with the file.
You missed the part where a new flag for sync_file_range would be added that
does sync the whole file system.
> I'm in favor of the new sys_syncfs system call.
Care to define its behaviour? Does it wait till all data is written out,
does it flush disk caches, what if new data is written to the fs while
a sync is going on, etc.
Greetings,
Indan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists