From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: take5: vector sharing (Large I/O system support)
Date: Mon, 07 Feb 2005 02:58:32 +0000 [thread overview]
Message-ID: <4206D958.9070409@jp.fujitsu.com> (raw)
In-Reply-To: <4201FC3A.40803@jp.fujitsu.com>
Hi David,
Thank you for your comments.
David Mosberger wrote:
> After a quick glance over the patch:
>
> - There are several lines introduced with trailing whitespace (some
> of them long). If you use emacs, you can get rid of them
> with delete-trailing-whitespace. Please do so.
Oh, sorry.
I'll fix this.
>
> - I'm not a fan of coding retry-loops with labels; I'd much rather
> have them be do/while-loops. In this particular case:
>
Ok, I'll change the patch to use do/while-loops instead
of using goto.
>
> How does the kernel fail when we're running out of statically
> allocated structures _before_ kmalloc() is initialized? It better be
> an obvious failure so one goes "oh, I better increase
> NR_RTE_CACHE_ENTRIES" instead of having to debug a weird crash deep in
> the allocator.
The lack of statically allocated structures is very rare
case (I think this will happen only if system has many
platform interrupt sources), so I didn't add the check if
we're running out of these structures. But, it possibly
happens and it will be hard to know what is happening. So
I'll change my patch to display debug messages.
Thanks,
Kenji Kaneshige
prev parent reply other threads:[~2005-02-07 2:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 10:26 take5: vector sharing (Large I/O system support) Kenji Kaneshige
2005-02-03 20:00 ` David Mosberger
2005-02-07 2:58 ` Kenji Kaneshige [this message]
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=4206D958.9070409@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--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