From: Andrea Arcangeli <andrea@suse.de>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Samuel Flory <sflory@rackable.com>, Stephen Lord <lord@sgi.com>,
Austin Gonyou <austin@coremetrics.com>,
Christian Guggenberger
<christian.guggenberger@physik.uni-regensburg.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-xfs@oss.sgi.com
Subject: Re: 2.4.20pre5aa2
Date: Mon, 16 Sep 2002 18:20:01 +0200 [thread overview]
Message-ID: <20020916162001.GK11605@dualathlon.random> (raw)
In-Reply-To: <3D8600DD.1010707@us.ibm.com>
On Mon, Sep 16, 2002 at 09:03:41AM -0700, Dave Hansen wrote:
> + vmi = get_vmalloc_info();
hmm, not sure if it's better to slowdown vmalloc instead of
/proc/meminfo and to keep meminfo o1. In theory vmalloc should be used
only for persistent infrequent allocations, so meminfo has a chance to
be recalled more frequently with monitors like xosview during workloads.
Admittedly in final production with no monitoring meminfo is going to
never be recalled, however I like the idea to keep meminfo very quick.
Andrea
next prev parent reply other threads:[~2002-09-16 16:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 18:16 2.4.20pre5aa2 Christian Guggenberger
2002-09-11 18:24 ` 2.4.20pre5aa2 Austin Gonyou
2002-09-11 18:28 ` 2.4.20pre5aa2 Christian Guggenberger
[not found] ` <1031769317.24629.28.camel@UberGeek.coremetrics.com>
2002-09-11 18:45 ` 2.4.20pre5aa2 Christian Guggenberger
2002-09-11 18:51 ` 2.4.20pre5aa2 Austin Gonyou
2002-09-11 18:41 ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-12 23:29 ` 2.4.20pre5aa2 Samuel Flory
2002-09-12 23:45 ` 2.4.20pre5aa2 Stephen Lord
2002-09-13 0:06 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 0:23 ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-13 0:47 ` 2.4.20pre5aa2 Stephen Lord
2002-09-13 0:54 ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-13 2:14 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 12:53 ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-13 21:09 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 21:18 ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-14 14:39 ` 2.4.20pre5aa2 Stephen Lord
2002-09-15 11:13 ` 2.4.20pre5aa2 Andi Kleen
2002-09-15 19:39 ` 2.4.20pre5aa2 Samuel Flory
2002-09-16 16:03 ` 2.4.20pre5aa2 Dave Hansen
2002-09-16 16:20 ` Andrea Arcangeli [this message]
2002-09-16 16:39 ` 2.4.20pre5aa2 Dave Hansen
2002-09-13 1:27 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 2:14 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 1:18 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 19:17 ` 2.4.20pre5aa2 Stephen Lord
2002-09-11 18:44 ` 2.4.20pre5aa2 Christoph Hellwig
2002-09-11 19:11 ` 2.4.20pre5aa2 Christian Guggenberger
-- strict thread matches above, loose matches on Subject: below --
2002-09-09 16:50 2.4.20pre5aa2 Andrea Arcangeli
2002-09-10 18:51 ` 2.4.20pre5aa2 Joe Kellner
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=20020916162001.GK11605@dualathlon.random \
--to=andrea@suse.de \
--cc=austin@coremetrics.com \
--cc=christian.guggenberger@physik.uni-regensburg.de \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=lord@sgi.com \
--cc=sflory@rackable.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