All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	arnd@arndb.de, "H. Peter Anvin" <hpa@zytor.com>,
	linux-api@vger.kernel.org, linux-arch@vger.kernel.org,
	Ingo Molnar <mingo@elte.hu>,
	ralf@linux-mips.org, tglx@linutronix.de,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [patch 143/166] preadv/pwritev: Add preadv and pwritev system calls.
Date: Fri, 03 Apr 2009 21:57:22 +0200	[thread overview]
Message-ID: <49D66A22.7090909@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0904030739540.4130@localhost.localdomain>

Linus Torvalds wrote:
>  - I changed the order to "low first". Why? Because when we have it like 
>    this, the 64-bit system calls now don't use the "pos_high" argument at 
>    all, and it makes more sense for the native system call to simply match 
>    the user-mode prototype.

Good idea.

> problems if we ever do 128-bit loff_t). So the user call wrapper isn't 
> really any more complicated - the HALF_BITS thing may look more 
> complicated than just doing a hard-coded '16' there twice, but if you 
> understand what it's doing it's actually more logical.

The whole point of the HALF_BITS thing is just to kill the gcc "hey your
shift is greater than bitsize of $type" warning, right?

> I think.
> 
> Comments?

I really like it.  Except for the low/high ordering it is basically
identical to the patch I've mailed.

While hashing out all the issues I've learned alot about arch specific
ABIs.  I can't see possible trouble spots and don't expect vetos from
arch maintainers.

cheers,
  Gerd

  reply	other threads:[~2009-04-03 19:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02 23:59 [patch 143/166] preadv/pwritev: Add preadv and pwritev system calls akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b
2009-04-02 23:59 ` akpm
     [not found] ` <200904022359.n32NxNYu022834-AB4EexQrvXRQetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
2009-04-03  1:43   ` Linus Torvalds
2009-04-03  1:43     ` Linus Torvalds
2009-04-03  8:35     ` Gerd Hoffmann
2009-04-03  9:25       ` Gerd Hoffmann
2009-04-03  9:25         ` Gerd Hoffmann
     [not found]         ` <49D5D609.7030400-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-04-03 11:53           ` Gerd Hoffmann
2009-04-03 11:53             ` Gerd Hoffmann
2009-04-03 11:53             ` Gerd Hoffmann
2009-04-03 15:03       ` Linus Torvalds
2009-04-03 19:57         ` Gerd Hoffmann [this message]
     [not found]           ` <49D66A22.7090909-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-04-03 20:08             ` Linus Torvalds
2009-04-03 20:08               ` Linus Torvalds
2009-04-04 17:38         ` Andrew Morton
2009-04-04 17:51           ` Linus Torvalds
     [not found]     ` <alpine.LFD.2.00.0904021839390.15441-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-04-03 16:57       ` H. Peter Anvin
2009-04-03 16:57         ` 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=49D66A22.7090909@redhat.com \
    --to=kraxel@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=hpa@zytor.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=ralf@linux-mips.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.