From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Anton Blanchard <anton@samba.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Allocate correct amount of memory for pid hash
Date: Mon, 06 Sep 2004 21:41:06 +1000 [thread overview]
Message-ID: <413C4CD2.3010200@yahoo.com.au> (raw)
In-Reply-To: <20040906113541.GR7716@krispykreme>
Anton Blanchard wrote:
>>Also, account for all the pid hashes when reporting hash memory usage.
>
>
> It looks like we are now allocating twice as much memory as required.
> How does this look?
>
Fine. Good catch thanks Anton.
next prev parent reply other threads:[~2004-09-06 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-22 4:44 [PATCH 1/2] fix PID hash sizing Nick Piggin
2004-08-22 4:46 ` [PATCH 2/2] use hlist for pid hash Nick Piggin
2004-08-22 5:00 ` David S. Miller
2004-08-22 5:31 ` Nick Piggin
2004-08-22 5:25 ` Ryan Cumming
2004-08-22 5:26 ` Nick Piggin
2004-09-06 11:35 ` [PATCH] Allocate correct amount of memory " Anton Blanchard
2004-09-06 11:41 ` Nick Piggin [this message]
2004-08-22 12:32 ` [PATCH 1/2] fix PID hash sizing William Lee Irwin III
2004-08-23 0:16 ` Nick Piggin
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=413C4CD2.3010200@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=anton@samba.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