From: David Miller <davem@davemloft.net>
To: ak@suse.de
Cc: kuznet@ms2.inr.ac.ru, dev@sw.ru, netdev@vger.kernel.org
Subject: Re: [PATCH] limit rt cache size
Date: Mon, 07 Aug 2006 23:18:34 -0700 (PDT) [thread overview]
Message-ID: <20060807.231834.48498773.davem@davemloft.net> (raw)
In-Reply-To: <200608080711.06788.ak@suse.de>
From: Andi Kleen <ak@suse.de>
Date: Tue, 8 Aug 2006 07:11:06 +0200
> The hash sizing code needs far more tweaks. iirc it can still
> allocate several GB hash tables on large memory systems (i've seen
> that once in the boot log of a 2TB system). Even on smaller systems
> it is usually too much.
There is already a limit parameter to alloc_large_system_hash(), the
fact that the routing cache passes in zero (which causes the limit to
be 1/16 of all system memory) is just a bug. :-)
In passing this immediately this suggests a fix to alloc_large_system_hash,
in that when limit is given as 0, it should follow the same rules for
HASH_HIGHME which are applied to the "scale" arg. It currently goes:
if (max == 0) {
max = ((unsigned long long)nr_all_pages << PAGE_SHIFT) >> 4;
do_div(max, bucketsize);
}
Whereas it should probably go:
if (max == 0) {
max = (flags & HASH_HIGHMEM) ? nr_all_pages : nr_kernel_pages;
max = (max << PAGE_SHIFT) >> 4;
do_div(max, bucketsize);
}
or something like that.
next prev parent reply other threads:[~2006-08-08 6:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44D75EF8.1070901@sw.ru>
2006-08-07 16:48 ` [PATCH] limit rt cache size Alexey Kuznetsov
2006-08-08 3:42 ` David Miller
2006-08-08 5:11 ` Andi Kleen
2006-08-08 6:18 ` David Miller [this message]
2006-08-08 6:53 ` Andi Kleen
2006-08-08 7:01 ` David Miller
2006-08-08 12:54 ` Kirill Korotaev
2006-08-08 12:58 ` Andi Kleen
2006-08-08 20:37 ` akepner
2006-08-08 23:23 ` Andi Kleen
2006-08-09 0:06 ` akepner
2006-08-09 0:11 ` David Miller
2006-08-09 0:11 ` akepner
2006-08-09 0:22 ` David Miller
2006-08-09 1:02 ` Andi Kleen
2006-08-09 16:16 ` akepner
2006-08-09 16:32 ` Andi Kleen
2006-08-10 0:02 ` David Miller
2006-08-09 8:05 ` Kirill Korotaev
2006-08-09 0:24 ` Andi Kleen
2006-08-09 0:32 ` David Miller
2006-08-09 8:09 ` Kirill Korotaev
2006-08-09 8:53 ` Eric Dumazet
2006-08-09 9:22 ` David Miller
2006-08-08 8:17 ` Kirill Korotaev
2006-08-08 8:34 ` David Miller
2006-08-08 8:57 ` Eric Dumazet
2006-08-08 9:12 ` David 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=20060807.231834.48498773.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ak@suse.de \
--cc=dev@sw.ru \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).