From: Arnd Bergmann <arnd@arndb.de>
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>,
Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [patch 2/13] signal/timer/event fds v6 - signalfd core ...
Date: Mon, 19 Mar 2007 00:45:23 +0100 [thread overview]
Message-ID: <200703190045.24605.arnd@arndb.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0703181313460.5482@alien.or.mcafeemobile.com>
On Sunday 18 March 2007, Davide Libenzi wrote:
> bah, __put_user is basically a move, so I don't think that efficency would
> be that different (assuming that it'd matter in this case). The only thing
> many __put_user do, is increase the exception table sizes.
The cost of user access functions varies a lot depending on the
architectures. Those platforms with a 4G/4G split e.g. need to do more
than a simple move, and for s390 it may even come down to an indirect
function call, which incurs significant register pressure.
Arnd <><
next prev parent reply other threads:[~2007-03-18 23:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 0:22 [patch 2/13] signal/timer/event fds v6 - signalfd core Davide Libenzi
2007-03-17 21:35 ` Arnd Bergmann
2007-03-17 21:50 ` Arnd Bergmann
2007-03-18 4:56 ` Stephen Rothwell
2007-03-18 20:31 ` Davide Libenzi
2007-03-18 23:45 ` Arnd Bergmann [this message]
2007-03-19 0:22 ` Davide Libenzi
2007-03-19 17:20 ` Eric W. Biederman
2007-03-19 18:53 ` Davide Libenzi
2007-03-19 19:08 ` Eric W. Biederman
2007-03-19 19:11 ` Davide Libenzi
2007-03-19 20:36 ` Oleg Nesterov
2007-03-19 22:33 ` Davide Libenzi
2007-03-19 22:53 ` Oleg Nesterov
2007-03-19 23:28 ` Oleg Nesterov
2007-03-19 23:34 ` 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=200703190045.24605.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--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 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.