[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0806021305550.11775@blonde.site>
Date: Mon, 2 Jun 2008 13:11:00 +0100 (BST)
From: Hugh Dickins <hugh@...itas.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Andrew Morton <akpm@...ux-foundation.org>,
Pavel Machek <pavel@...e.cz>, mtk.manpages@...il.com,
kernel list <linux-kernel@...r.kernel.org>
Subject: Re: sync_file_range(SYNC_FILE_RANGE_WRITE) blocks?
On Mon, 2 Jun 2008, Rafael J. Wysocki wrote:
>
> Well, frankly, I'm not sure if we need anything better than we already have.
> In fact my numbers show that SYNC_FILE_RANGE_WRITE works quite well -
> please see
> http://sourceforge.net/mailarchive/message.php?msg_name=200806020122.36193.rjw%40sisk.pl
> "early writeout" means that SYNC_FILE_RANGE_WRITE is used and the file with
> the results is attached for convenience.
>
> My interpretation of the results is here:
> http://sourceforge.net/mailarchive/forum.php?thread_name=200806021238.17100.rjw%40sisk.pl&forum_name=suspend-devel
If the current SYNC_FILE_RANGE_WRITE is good enough for you, great,
keep on using it. Forgive me, I'm not much concerned with your
particular use, I'll happily leave that to you and Pavel! What
bothers me is Pavel's discovery that a WAIT|WRITE|WAIT interface,
designed to help callers by allowing those stages to be separated,
ends up doing a significant amount of WAITing in the WRITE stage.
Hugh
--
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