From: Andrew Morton <akpm@osdl.org>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bh_lru_install
Date: Tue, 27 Jul 2004 16:06:17 -0700 [thread overview]
Message-ID: <20040727160617.321ce504.akpm@osdl.org> (raw)
In-Reply-To: <20040723170338.0c9a38ef.davem@redhat.com>
"David S. Miller" <davem@redhat.com> wrote:
>
> So I was doing some profiling of memcpy() calls to try and tune
> the UltraSPARC-III memcpy a little more, and you wouldn't believe
> what was at the top of the list during a kernel build :-)
>
> It's bh_lru_install. On a 64-bit system every time the local
> cpu's lru->bh[0] doesn't match 'bh' we do a 64-byte memcpy()
> from the stack into the lru->bh[] array.
Well I said it was dopey-but-simple ;)
> It shouldn't be too hard to make the code just work without
> an on-stack copy, shuffling the lru->bh[] array entries
> directly.
Yup, that plus making it a ringbuffer maybe.
But I don't recall seeing bh_lru_install() standing out on profiles. I
expect that when the system is working hard we're averaging nearly zero
cache misses in that copy. Do you really think it is worth optimising?
next prev parent reply other threads:[~2004-07-27 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 0:03 bh_lru_install David S. Miller
2004-07-27 23:06 ` Andrew Morton [this message]
2004-07-27 23:41 ` bh_lru_install David S. Miller
2004-07-28 0:15 ` bh_lru_install David S. Miller
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=20040727160617.321ce504.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davem@redhat.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
all inboxes | Powered by JetHome®