[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081007115052.GI20740@one.firstfloor.org>
Date: Tue, 7 Oct 2008 13:50:52 +0200
From: Andi Kleen <andi@...stfloor.org>
To: "Kirill A. Shutemov" <kirill@...temov.name>
Cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Ingo Molnar <mingo@...hat.com>,
Arjan van de Ven <arjan@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH, RFC] shmat: introduce flag SHM_MAP_HINT
On Tue, Oct 07, 2008 at 02:30:51PM +0300, Kirill A. Shutemov wrote:
> On Tue, Oct 07, 2008 at 08:26:03PM +0900, KOSAKI Motohiro wrote:
> > > > Honestly, I don't like that qemu specific feature insert into shmem core.
> > >
> > > I wouldn't say it's a qemu specific interface. While qemu would
> > > be the first user I would expect more in the future. It's a pretty
> > > obvious extension. In fact it nearly should be default, if the
> > > risk of breaking old applications wasn't too high.
> >
> > hm, ok, i understand your intension.
> > however, I think following code isn't self describing.
> >
> > addr = shmat(shmid, addr, SHM_MAP_HINT);
> >
> > because HINT is too generic word.
> > I think we should find better word.
> >
> > SHM_MAP_NO_FIXED ?
>
> I like it.
> Andi?
SHM_MAP_NOT_FIXED perhaps.
I personally would call it SHM_MAP_SEARCH_HINT
But to be honest I have no strong opinion on the naming. Perhaps others have.
-Andi
--
ak@...ux.intel.com
--
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