public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Michael S. Tsirkin" <mst@mellanox.co.il>
Cc: linux-arch@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Roland Dreier <rdreier@cisco.com>,
	Hugh Dickins <hugh@veritas.com>
Subject: Re: [Fwd: Re: [PATCH] madvise MADV_DONTFORK/MADV_DOFORK]
Date: Wed, 15 Feb 2006 19:49:25 +1100	[thread overview]
Message-ID: <43F2EB15.5080402@yahoo.com.au> (raw)
In-Reply-To: <43F2E38C.5030602@yahoo.com.au>

Nick Piggin wrote:

> All I'm saying is that we can easily wait a few days until arch
> maintainers have had a chance to comment (you didn't think you
> were missing anything last time, either).
> 
> We can afford to be a little bit careful about changing user APIs.
> 

If it is a good idea to keep the common MADV_ parameters in synch
over all architectures, why not make 0x00 - 0xff the legacy space,
then 0x100 - 0xfff can be for arch specific parameters, and
0x1000 - ... can be for common/generic parameters?

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-02-15 10:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-15  6:18 [Fwd: Re: [PATCH] madvise MADV_DONTFORK/MADV_DOFORK] Nick Piggin
2006-02-15  8:10 ` Michael S. Tsirkin
2006-02-15  8:17   ` Nick Piggin
2006-02-15  8:49     ` Nick Piggin [this message]
2006-02-15 12:12       ` Michael S. Tsirkin
2006-02-15 10:18     ` Russell King
2006-02-15 12:31       ` Nick Piggin
2006-02-15 10:20     ` Michael S. Tsirkin
2006-02-15 12:43   ` Matthew Wilcox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43F2EB15.5080402@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=mst@mellanox.co.il \
    --cc=rdreier@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox