linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@mellanox.com>
To: Yury Norov <ynorov@caviumnetworks.com>
Cc: <cmetcalf@tilera.com>, <arnd@arndb.de>, <catalin.marinas@arm.com>,
	<linux-kernel@vger.kernel.org>, <libc-alpha@sourceware.org>,
	<pinskia@gmail.com>
Subject: Re: [glibc] preadv/pwritev question
Date: Tue, 31 May 2016 17:00:31 -0400	[thread overview]
Message-ID: <d8f96b34-1a13-66a2-9c10-8a361ea6998a@mellanox.com> (raw)
In-Reply-To: <20160531200454.GA32677@yury-N73SV>

On 5/31/2016 4:04 PM, Yury Norov wrote:
> Hi Chris,
>
> In path a63c7fa18a (Add sysdeps/unix/sysv/linux/generic/.) you add
> this:
> +++ b/sysdeps/unix/sysv/linux/generic/wordsize-32/preadv.c
>
> [...]
>
> +static ssize_t
> +do_preadv (int fd, const struct iovec *vector, int count, off_t
> offset)
> +{
> +  assert (sizeof (offset) == 4);
> +  return INLINE_SYSCALL (preadv, __ALIGNMENT_COUNT (5, 6), fd,
> +                         vector, count, __ALIGNMENT_ARG
> +                         __LONG_LONG_PAIR (offset >> 31, offset));
> +}
> +
>
> And this is the code that is picked up if I choose wordsize-32 for my
> AARCH64/ILP32. So I have questions.
>
> 1. What is the assert for? We agreed that all new ABIs will be 64-bit
> off_t only.
>
> I fixed it internally like this:
> +#ifndef __OFF_T_MATCHES_OFF64_T
>          assert (sizeof (offset) == 4);
> +#endif
>
> There is a bunch of similar assertions in glibc.
>
> 2. This one looks weird:
> __LONG_LONG_PAIR (offset >> 31, offset))
> Why 31-bit offset? And why you don't mask 2nd argument?
> Later in your patch I see this:
> +static ssize_t
> +do_preadv64 (int fd, const struct iovec *vector, int count, off64_t
> offset)
>
> +{
> +  return INLINE_SYSCALL (preadv, __ALIGNMENT_COUNT (5, 6), fd,
> +                         vector, count, __ALIGNMENT_ARG
> +                         __LONG_LONG_PAIR ((off_t) (offset >> 32),
> +                                           (off_t) (offset & 0xffffffff)));
> +}
>
> And it looks correct to me. If 1st version is correct as well, I think
> it should be commented.

I did this work before x32 came out, so I tried to model it more closely on
the existing x86 compat API.  I agree that a 64-bit off_t model seems reasonable;
however, the code does exactly what it does to match x86, namely preadv() takes
a 32-bit offset, and preadv64() take a 64-bit offset.  The assert() in preadv to force
sizeof to be 4 is exactly why in that routine we use (offset >> 31, offset).  Since
we know offset fits in 32 bits, all we need to do is properly sign-extend it into
64 bits in the high register of the pair, which is what (offset >> 31) does - you end
up with only 0 or -1, thus sign-extending the 32-bit signed off_t. Then in
preadv64() we actually need to break apart the 64-bit offset into a high 32 bits
and a low 32 bits, which is what (offset >> 32, offset & 0xffffffff) does.

For a 64-bit off_t you will want to not compile preadv.c at all, and instead make
__libc_preadv() and friends be aliases of __libc_preadv64().

-- 
Chris Metcalf, Mellanox Technologies
http://www.mellanox.com

  reply	other threads:[~2016-05-31 21:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 20:04 [glibc] preadv/pwritev question Yury Norov
2016-05-31 21:00 ` Chris Metcalf [this message]
2016-05-31 22:00   ` Mike Frysinger

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=d8f96b34-1a13-66a2-9c10-8a361ea6998a@mellanox.com \
    --to=cmetcalf@mellanox.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=cmetcalf@tilera.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pinskia@gmail.com \
    --cc=ynorov@caviumnetworks.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;
as well as URLs for NNTP newsgroup(s).