Date: Thu, 9 Feb 2006 21:13:56 -0800
From: Andrew Morton <akpm@osdl.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux@horizon.com, linux-kernel@vger.kernel.org, sct@redhat.com
Subject: Re: msync() behaviour broken for MS_ASYNC, revert patch?
Message-Id: <20060209211356.6c3a641a.akpm@osdl.org>
In-Reply-To: <43EC1BFF.1080808@yahoo.com.au>
References: <20060209071832.10500.qmail@science.horizon.com>
	<20060209001850.18ca135f.akpm@osdl.org>
	<43EAFEB9.2060000@yahoo.com.au>
	<20060209004208.0ada27ef.akpm@osdl.org>
	<43EB3801.70903@yahoo.com.au>
	<20060209094815.75041932.akpm@osdl.org>
	<43EC0A44.1020302@yahoo.com.au>
	<20060209195035.5403ce95.akpm@osdl.org>
	<43EC0F3F.1000805@yahoo.com.au>
	<20060209201333.62db0e24.akpm@osdl.org>
	<43EC16D8.8030300@yahoo.com.au>
	<20060209204314.2dae2814.akpm@osdl.org>
	<43EC1BFF.1080808@yahoo.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 799
Lines: 17

Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
> If you want to start the IO *now* without waiting on it, call msync(MS_ASYNC)
>  If you don't want to start the IO now, that's really easy, do nothing.
>  If you want to start the IO now and also wait for it to finish, call msync(MS_SYNC)

I've already explained the problems with the start-io-in-MS_ASYNC approach.

>  Presently, the first option is unavailable.

We need to patch the kernel either way.  There's no point in going back to
either the known-problematic approach or to something half-assed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/