From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: 2.5.39-mm1
Date: Mon, 30 Sep 2002 11:24:54 -0700 [thread overview]
Message-ID: <3D9896F6.8E584DC5@digeo.com> (raw)
In-Reply-To: 766838976.1033378149@[10.10.2.3]
"Martin J. Bligh" wrote:
>
> Which looks about the same to me? Me slightly confused.
I expect that with the node-local allocations you're not getting
a lot of benefit from the lock amortisation. Anton will.
It's the lack of improvement of cache-niceness which is irksome.
Perhaps the heuristic should be based on recency-of-allocation and
not recency-of-freeing. I'll play with that.
> Will try
> adding the original hot/cold stuff onto 39-mm1 if you like?
Well, it's all in the noise floor, isn't it? Better off trying
broader tests. I had a play with netperf and the chatroom
benchmark. But the latter varied from 80,000 msgs/sec up
to 350,000 between runs.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: 2.5.39-mm1
Date: Mon, 30 Sep 2002 11:24:54 -0700 [thread overview]
Message-ID: <3D9896F6.8E584DC5@digeo.com> (raw)
In-Reply-To: 766838976.1033378149@[10.10.2.3]
"Martin J. Bligh" wrote:
>
> Which looks about the same to me? Me slightly confused.
I expect that with the node-local allocations you're not getting
a lot of benefit from the lock amortisation. Anton will.
It's the lack of improvement of cache-niceness which is irksome.
Perhaps the heuristic should be based on recency-of-allocation and
not recency-of-freeing. I'll play with that.
> Will try
> adding the original hot/cold stuff onto 39-mm1 if you like?
Well, it's all in the noise floor, isn't it? Better off trying
broader tests. I had a play with netperf and the chatroom
benchmark. But the latter varied from 80,000 msgs/sec up
to 350,000 between runs.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-09-30 18:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 20:26 2.5.39-mm1 Andrew Morton
2002-09-29 20:26 ` 2.5.39-mm1 Andrew Morton
2002-09-30 1:24 ` 2.5.39-mm1 Ed Tomlinson
2002-09-30 1:24 ` 2.5.39-mm1 Ed Tomlinson
2002-09-30 1:35 ` 2.5.39-mm1 Andrew Morton
2002-09-30 1:35 ` 2.5.39-mm1 Andrew Morton
2002-09-30 7:51 ` 2.5.39-mm1 Martin J. Bligh
2002-09-30 7:51 ` 2.5.39-mm1 Martin J. Bligh
2002-09-30 8:01 ` 2.5.39-mm1 Andrew Morton
2002-09-30 8:01 ` 2.5.39-mm1 Andrew Morton
2002-09-30 16:29 ` 2.5.39-mm1 Martin J. Bligh
2002-09-30 16:29 ` 2.5.39-mm1 Martin J. Bligh
2002-09-30 18:24 ` Andrew Morton [this message]
2002-09-30 18:24 ` 2.5.39-mm1 Andrew Morton
2002-10-01 3:58 ` 2.5.39-mm1 Maneesh Soni
2002-10-01 3:51 ` 2.5.39-mm1 Andrew Morton
2002-10-01 4:13 ` 2.5.39-mm1 Maneesh Soni
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=3D9896F6.8E584DC5@digeo.com \
--to=akpm@digeo.com \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.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 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.