From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: take7: vector sharing (Large I/O system support)
Date: Tue, 01 Mar 2005 21:51:18 +0000 [thread overview]
Message-ID: <20050301215118.GC5167@infradead.org> (raw)
In-Reply-To: <42226CCE.6070706@jp.fujitsu.com>
On Tue, Mar 01, 2005 at 11:35:11AM -0800, David Mosberger wrote:
> >>>>> On Mon, 28 Feb 2005 14:10:53 +0900, Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com> said:
>
> Kenji> Hi Cristoph,
> >>> +config NR_RTE_CACHES
> >>> + int "Number of RTE cache entries"
> >>> + depends on IOSAPIC
> >>> + default "256"
> >>> + help
> >>> + If your system panic with the message "out of rte cache
> >>> + entries!(shortage: XX)", please set this to a larger value.
> >>
> >>
> >> This screams for dynamic allocation of the underlying structures, no?
>
> Kenji> Some number (NR_RTE_CACHES) of iosapic_rte_info structures are
> Kenji> statically allocated because this structure might be needed before
> Kenji> kmalloc is initialized. The panic message mentioned above means we
> Kenji> run out of these statically allocated structures.
>
> The problem is naming, I think. Those aren't "cache entries", they
> are statically preallocated entries. How about changing the config
> option name to:
Even for early allocations what speaks against alloc_bootmem?
next prev parent reply other threads:[~2005-03-01 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 0:58 take7: vector sharing (Large I/O system support) Kenji Kaneshige
2005-02-28 3:12 ` Christoph Hellwig
2005-02-28 5:10 ` Kenji Kaneshige
2005-03-01 19:35 ` David Mosberger
2005-03-01 21:51 ` Christoph Hellwig [this message]
2005-03-01 22:04 ` David Mosberger
2005-03-02 1:20 ` Kenji Kaneshige
2005-03-02 5:17 ` Christoph Hellwig
2005-03-02 17:42 ` Luck, Tony
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=20050301215118.GC5167@infradead.org \
--to=hch@infradead.org \
--cc=linux-ia64@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