From: David Miller <davem@davemloft.net>
To: bos@serpentine.com
Cc: linux-kernel@vger.kernel.org, arjan@infradead.org
Subject: Re: [PATCH] Add memcpy_cachebypass, a copy routine that tries to keep cache pressure down
Date: Tue, 11 Jul 2006 15:08:10 -0700 (PDT) [thread overview]
Message-ID: <20060711.150810.13051231.davem@davemloft.net> (raw)
In-Reply-To: <1152655509.16499.49.camel@chalcedony.pathscale.com>
From: Bryan O'Sullivan <bos@serpentine.com>
Date: Tue, 11 Jul 2006 15:05:08 -0700
> Well, exactly this scheme seems to work for __iowrite_copy*. There's a
> weak generic version and a strong version in arch/x86_64/lib that
> overrides it, and it gets picked up at kernel link time.
It is linked in as an object, not into the library archive,
that's why that one works like that.
That is why io.o is added to the "obj-y" variable instead of the
"lib-y" variable. It is also necessary to link these things
in as objects when module exports are present, because if there
is no in-kernel reference to the function, you won't get the
function nor it's module export :)
next prev parent reply other threads:[~2006-07-11 22:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 20:50 [PATCH] Add memcpy_cachebypass, a copy routine that tries to keep cache pressure down Bryan O'Sullivan
2006-07-11 20:56 ` Arjan van de Ven
2006-07-11 20:57 ` David Miller
2006-07-11 21:30 ` Bryan O'Sullivan
2006-07-11 21:57 ` David Miller
2006-07-11 22:05 ` Bryan O'Sullivan
2006-07-11 22:08 ` David Miller [this message]
2006-07-12 8:04 ` Christoph Hellwig
2006-07-11 21:09 ` Randy.Dunlap
2006-07-11 21:35 ` Bryan O'Sullivan
2006-07-11 22:48 ` Randy.Dunlap
2006-07-12 16:15 ` Andi Kleen
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=20060711.150810.13051231.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arjan@infradead.org \
--cc=bos@serpentine.com \
--cc=linux-kernel@vger.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