public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Arun Sharma <arun.sharma@intel.com>
To: Matthew Wilcox <willy@debian.org>
Cc: davidm@hpl.hp.com, "David S. Miller" <davem@redhat.com>,
	linux-arch@vger.kernel.org
Subject: Re: SHMLBA and compat tasks
Date: Tue, 2 Mar 2004 11:43:02 -0800	[thread overview]
Message-ID: <20040302194302.GA17408@intel.com> (raw)
In-Reply-To: <20040301205510.GF25779@parcelfarce.linux.theplanet.co.uk>

On Mon, Mar 01, 2004 at 08:55:10PM +0000, Matthew Wilcox wrote:
> On Mon, Mar 01, 2004 at 12:16:13PM -0800, Arun Sharma wrote:
> > Sounds like we have sufficient grounds for using different alignment
> > rules for different architectures ?
> 
> #ifndef COMPAT_SHMLBA
> #define COMPAT_SHMLBA SHMLBA
> #endif
> 
> should be enough, no?

I'm concerned that we'll have to duplicate/inline much of sys_shmat() in
ipc/compat.c and it might become a maintenance problem. Perhaps there is 
a way to do it in a better way, but I don't see it.

An ifdef in sys_shmat() that distinugishes between architectures that enforce 
SHMLBA in all cases and the ones which don't would be ideal for my purposes.

	-Arun

  reply	other threads:[~2004-03-02 19:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-28  1:41 SHMLBA and compat tasks Arun Sharma
2004-02-28 23:55 ` David S. Miller
2004-02-29  2:11   ` Arun Sharma
2004-03-01  5:57     ` David S. Miller
2004-03-01 19:33       ` Arun Sharma
2004-03-01 19:41         ` David Mosberger
2004-03-01 20:11           ` David S. Miller
2004-03-01 20:17             ` David Mosberger
2004-03-01 20:16           ` Arun Sharma
2004-03-01 20:55             ` Matthew Wilcox
2004-03-02 19:43               ` Arun Sharma [this message]
2004-03-06  2:37                 ` Arun Sharma
2004-03-06  7:39                   ` David S. Miller

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=20040302194302.GA17408@intel.com \
    --to=arun.sharma@intel.com \
    --cc=davem@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=willy@debian.org \
    /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