From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Luca Barbieri <ldb@ldb.ods.org>
Cc: Pavel Machek <pavel@suse.cz>,
Linux-Kernel ML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH 1 / ...] i386 dynamic fixup/self modifying code
Date: 30 Aug 2002 12:17:59 +0100 [thread overview]
Message-ID: <1030706279.3180.26.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <1030666256.1491.143.camel@ldb>
On Fri, 2002-08-30 at 01:10, Luca Barbieri wrote:
> That wouldn't work for compiler-generated prefetches (unless you
> preprocess the compiler output) and would enlarge the kernel.
> However, it would be significantly cleaner.
My general experience with compiler generated prefetches right now is
pretty poor for kernel type code. Its hard to do it right in the
compiler for complex stuff rather than 'fortran in C' type jobs
We certainly could perl the asm to drop in the right directives if it
became an issue, but there are children on the list so lets worry about
it if it becomes a problem
next prev parent reply other threads:[~2002-08-30 11:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 3:41 [PATCH 1 / ...] i386 dynamic fixup/self modifying code Luca Barbieri
2002-08-28 12:11 ` Pavel Machek
2002-08-29 22:57 ` Luca Barbieri
2002-08-29 23:19 ` Alan Cox
2002-08-29 23:22 ` Pavel Machek
2002-08-30 0:05 ` David S. Miller
2002-08-30 0:21 ` Luca Barbieri
2002-08-29 23:29 ` Luca Barbieri
2002-08-29 23:32 ` Alan Cox
2002-08-30 0:10 ` Luca Barbieri
2002-08-30 11:17 ` Alan Cox [this message]
2002-09-03 21:31 ` Jamie Lokier
2002-09-03 21:35 ` Jamie Lokier
2002-08-30 0:08 ` David S. Miller
2002-08-28 15:53 ` Mikael Pettersson
2002-08-28 16:16 ` Luca Barbieri
2002-08-28 19:48 ` Mikael Pettersson
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=1030706279.3180.26.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ldb@ldb.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).