From: Roland McGrath <roland@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 uaccess to fixmap pages
Date: Fri, 9 May 2003 02:40:51 -0700 [thread overview]
Message-ID: <200305090940.h499ep513112@magilla.sf.frob.com> (raw)
In-Reply-To: Andrew Morton's message of Friday, 9 May 2003 02:19:21 -0700 <20030509021921.166f82fc.akpm@digeo.com>
> Nasty. Maybe the best approach is to mostly uninline the access_ok()
> check. Do the check for constant-sized small copies first, so those guys
> still do the access_ok() check inline; uninline the rest.
That was the only thing I could think of too. I haven't made any attempt
to figure out how much of the code size comes from the various inlined
user-memory copying functions that call access_ok, and could be reworked
not to inline any of the uncommon paths, vs direct uses of access_ok in
miscellaneous code.
next prev parent reply other threads:[~2003-05-09 9:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 2:03 Roland McGrath
2003-05-09 4:31 ` Andrew Morton
2003-05-09 8:55 ` Roland McGrath
2003-05-09 9:19 ` Andrew Morton
2003-05-09 9:40 ` Roland McGrath [this message]
2003-05-09 10:43 ` Roland McGrath
2003-05-09 11:42 ` Dave Jones
2003-05-09 11:55 ` Alan Cox
2003-05-09 12:40 ` Jamie Lokier
2003-05-09 16:06 ` Linus Torvalds
2003-05-09 16:38 ` Dave Hansen
2003-05-09 15:55 ` Martin J. Bligh
2003-05-09 18:20 ` William Lee Irwin III
2003-05-09 16:48 ` Linus Torvalds
2003-05-09 17:16 ` Dave Hansen
2003-05-10 3:26 ` H. Peter Anvin
2003-05-10 15:31 ` Jamie Lokier
2003-05-10 17:23 ` Ulrich Drepper
2003-05-10 19:23 ` H. Peter Anvin
2003-05-10 20:52 ` Jamie Lokier
2003-05-09 17:28 Chuck Ebbert
2003-05-09 17:49 ` Linus Torvalds
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=200305090940.h499ep513112@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®