linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@kvack.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: hpa@zytor.com, klibc@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: sys_mmap2 on different architectures
Date: Thu, 23 Feb 2006 12:39:07 -0500	[thread overview]
Message-ID: <20060223173907.GF27682@kvack.org> (raw)
In-Reply-To: <20060222.164347.12864037.davem@davemloft.net>

On Wed, Feb 22, 2006 at 04:43:47PM -0800, David S. Miller wrote:
> Aha, that part I didn't catch.  Thanks for the clarification
> Ben.
> 
> I wonder why we did things that way with a fixed shift...

Without that trick, we'd have needed an extra parameter for the syscall 
on x86, which is already at the maximum number of registers with 6 
arguments.  This was easier than changing the syscall ABI. =-)

		-ben
-- 
"Ladies and gentlemen, I'm sorry to interrupt, but the police are here 
and they've asked us to stop the party."  Don't Email: <dont@kvack.org>.

  parent reply	other threads:[~2006-02-23 17:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 21:45 sys_mmap2 on different architectures H. Peter Anvin
2006-02-22 21:54 ` David S. Miller
2006-02-22 22:00   ` H. Peter Anvin
2006-02-23  0:05   ` H. Peter Anvin
2006-02-23  0:40     ` David S. Miller
2006-02-23  0:41     ` David S. Miller
2006-02-23  0:14 ` Benjamin LaHaise
2006-02-23  0:22   ` H. Peter Anvin
2006-02-23  0:43   ` David S. Miller
2006-02-23  0:59     ` H. Peter Anvin
2006-02-23  1:03       ` David S. Miller
2006-02-23  1:06         ` H. Peter Anvin
2006-02-23 17:39     ` Benjamin LaHaise [this message]
2006-02-23 17:47       ` H. Peter Anvin
2006-02-23  2:56 ` Paul Mackerras
2006-02-23  3:35   ` H. Peter Anvin
2006-02-23 17:32     ` Ralf Baechle
2006-02-23 17:43       ` H. Peter Anvin

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=20060223173907.GF27682@kvack.org \
    --to=bcrl@kvack.org \
    --cc=davem@davemloft.net \
    --cc=hpa@zytor.com \
    --cc=klibc@zytor.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).