[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1263408098.3874.19.camel@entropy>
Date: Wed, 13 Jan 2010 10:41:38 -0800
From: Nicholas Miell <nmiell@...cast.net>
To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc: paulmck@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
Steven Rostedt <rostedt@...dmis.org>,
Oleg Nesterov <oleg@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...e.hu>, akpm@...ux-foundation.org,
josh@...htriplett.org, tglx@...utronix.de, Valdis.Kletnieks@...edu,
dhowells@...hat.com, laijs@...fujitsu.com, dipankar@...ibm.com
Subject: Re: [RFC PATCH] introduce sys_membarrier(): process-wide memory
barrier (v5)
On Wed, 2010-01-13 at 13:24 -0500, Mathieu Desnoyers wrote:
> * Nicholas Miell (nmiell@...cast.net) wrote:
>
> > The whole point of compat and incompat flags is that it allows new
> > applications to run on old kernels and either work or fail as
> > appropriate, depending on whether the new features they're using must be
> > implemented or can be silently ignored.
>
> I see. Thanks for the explanation. Then the expedited flag should
> clearly be part of the mandatory flags.
>
> Can you point me to other system calls that are doing this ?
>
> Thanks,
>
> Mathieu
Not off the top of my head, but I did steal the idea from the ext2/3/4
disk format.
--
Nicholas Miell <nmiell@...cast.net>
--
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