From: "Ulrich Drepper" <drepper@gmail.com>
To: "Davide Libenzi" <davidel@xmailserver.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: [patch 0/6] sys_indirect RFC - sys_indirect introduction
Date: Sat, 30 Jun 2007 14:54:06 -0700 [thread overview]
Message-ID: <a36005b50706301454j46c23760m5f0ac6088fe24a9d@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706301208140.2957@alien.or.mcafeemobile.com>
On 6/30/07, Davide Libenzi <davidel@xmailserver.org> wrote:
> But, a __get_user(), once you scrap off all the gcc wrapping, is bacially
> a move. That could even be removed, but really I don't see the reason
> since it allows for a cleaner strcture definition in userland.
Don't generalize. The 4G/4G kernel, for instance, doesn't have this
property. Who knows what else will come up. Anyway, two memcpy are
slower than one.
> But this does not allow more than one context to be set at a time, like
> the current implementation does. Ie, the current implementation allow you
> to:
Of course it does. It just requires an appropriate union element.
I've listed flags and sigset_t as separate union elements since I
cannot think of a place where we need both extensions. Should there
be one this can easily be changed.
next prev parent reply other threads:[~2007-06-30 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 21:48 Davide Libenzi
2007-06-30 1:48 ` Ulrich Drepper
2007-06-30 19:23 ` Davide Libenzi
2007-06-30 21:54 ` Ulrich Drepper [this message]
2007-06-30 22:27 ` Davide Libenzi
2007-06-30 22:32 ` Davide Libenzi
2007-07-01 16:25 ` Ulrich Drepper
2007-07-01 17:09 ` Davide Libenzi
2007-07-02 14:09 ` Ulrich Drepper
2007-07-02 22:37 ` Davide Libenzi
2007-07-03 0:28 ` Ulrich Drepper
2007-07-03 0:37 ` Davide Libenzi
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=a36005b50706301454j46c23760m5f0ac6088fe24a9d@mail.gmail.com \
--to=drepper@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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®