From: Christoph Hellwig <hch@lst.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Dmitry V. Levin" <ldv@altlinux.org>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Christoph Hellwig <hch@lst.de>,
LKML <linux-kernel@vger.kernel.org>,
Milosz Tanski <milosz@adfin.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] x86: use compat version for preadv2 and pwritev2
Date: Thu, 12 May 2016 09:31:33 +0200 [thread overview]
Message-ID: <20160512073133.GB3852@lst.de> (raw)
In-Reply-To: <alpine.DEB.2.11.1605111212440.3540@nanos>
On Wed, May 11, 2016 at 12:14:11PM +0200, Thomas Gleixner wrote:
> On Wed, 11 May 2016, Dmitry V. Levin wrote:
> > Similar to preadv and pwritev, preadv2 and pwritev2 need compat entries
> > in the 32-bit syscall table.
>
> So this is 2016 and we added a syscalls which require compat support. What's
> wrong here?
Nothing. It's and extension of readv/writev and uses struct iovec,
which is different for compat vs native. We have efficient infrastructure
to deal with that in the kernel, while in userspace people would have
to copy around all the iovecs for every I/O, which would be a nightmare.
next prev parent reply other threads:[~2016-05-12 7:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 8:48 Dmitry V. Levin
2016-05-11 10:14 ` Thomas Gleixner
2016-05-11 10:25 ` Dmitry V. Levin
2016-05-11 11:01 ` Thomas Gleixner
2016-05-12 7:31 ` Christoph Hellwig [this message]
2016-05-12 7:30 ` Christoph Hellwig
2016-05-12 10:55 ` Dmitry V. Levin
2016-05-12 12:33 ` [tip:x86/urgent] x86: Use " tip-bot for Dmitry V. Levin
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=20160512073133.GB3852@lst.de \
--to=hch@lst.de \
--cc=hpa@zytor.com \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=milosz@adfin.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@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
all inboxes | Powered by JetHome®