From: Andrew Morton <akpm@digeo.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: kiran@in.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [patch] Inline vm_acct_memory
Date: Wed, 28 May 2003 19:23:30 -0700 [thread overview]
Message-ID: <20030528192330.77d3d9e9.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0305281631030.1240-100000@localhost.localdomain>
Hugh Dickins <hugh@veritas.com> wrote:
>
> On Wed, 28 May 2003, Ravikiran G Thirumalai wrote:
> > I found that inlining vm_acct_memory speeds up vm_enough_memory.
> > Since vm_acct_memory is only called by vm_enough_memory,
>
> No, linux/mman.h declares
>
> static inline void vm_unacct_memory(long pages)
> {
> vm_acct_memory(-pages);
> }
>
> and I count 18 callsites for vm_unacct_memory.
>
> I'm no judge of what's worth inlining, but Andrew is widely known
> and feared as The Scourge of Inliners, so I'd advise you to hide...
Maybe I'm wrong. kernbench is not some silly tight-loop microbenchmark.
It is a "real" workload: gcc.
The thing about pagetable setup and teardown is that it tends to be called
in big lumps: for a while the process is establishing thousands of pages
and then later it is tearing down thousands. So the cache-thrashing impact
of having those eighteen instances sprinkled around the place is less
than it would be if they were all being called randomly. If you can believe
such waffle.
Kiran, do you still have the raw data available? profiles and runtimes?
next prev parent reply other threads:[~2003-05-29 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 11:05 [patch] Inline vm_acct_memory Ravikiran G Thirumalai
2003-05-28 11:04 ` Andrew Morton
2003-05-28 15:45 ` Hugh Dickins
2003-05-29 2:23 ` Andrew Morton [this message]
2003-05-29 4:43 ` Ravikiran G Thirumalai
2003-05-29 5:59 ` Hugh Dickins
2003-05-29 9:52 ` Ravikiran G Thirumalai
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=20030528192330.77d3d9e9.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=hugh@veritas.com \
--cc=kiran@in.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.