public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bh_lru_install
Date: Tue, 27 Jul 2004 16:41:47 -0700	[thread overview]
Message-ID: <20040727164147.39ad7f5c.davem@redhat.com> (raw)
In-Reply-To: <20040727160617.321ce504.akpm@osdl.org>

On Tue, 27 Jul 2004 16:06:17 -0700
Andrew Morton <akpm@osdl.org> wrote:

> 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?

On a full kernel build after a fresh boot, that memcpy() executes
approximately 400K times on my sparc64 boxes.

  reply	other threads:[~2004-07-27 23:43 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 ` bh_lru_install Andrew Morton
2004-07-27 23:41   ` David S. Miller [this message]
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=20040727164147.39ad7f5c.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=akpm@osdl.org \
    --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