public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH take3 0/12] Support vector domain on ia64
Date: Fri, 20 Jul 2007 05:37:21 +0000	[thread overview]
Message-ID: <46A04A11.7010505@jp.fujitsu.com> (raw)
In-Reply-To: <469CB3FA.7010301@jp.fujitsu.com>

Hi Eric,

Eric W. Biederman wrote:
> Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com> writes:
> 
>> - define NR_IRQS as follow:
>>
>>   Vector domain can provide the number of irqs being proportional to the
>>   number of CPUs theoretically. However, the relation between them is
>>   actually not linear, especially in large system. To avoid the memory
>>   consumption derived from too many irqs, I define NR_IRQS as follows:
>>
>>   #if (NR_VECTORS + 32 * NR_CPUS) < 1024
>>   #define NR_IRQS (NR_VECTORS + 32 * NR_CPUS)
>>   #else
>>   #define NR_IRQS 1024
>>   #endif
> 
> 
> Below is my old patch to address this in a different way.
> Basically this moves the per cpu counter of the number of
> times an irq has happened on an individual cpu out of the
> per cpu area.  Honestly I think this might even have better
> cache performance.

Sorry for my late reply.

I overviewed your patch and the patch looks good to me. It can improve
not only ia64 vector domain but also x86_64 vector domain. I'll consider
testing the patch after rebasing it, and if it'll be OK, including your
idea (or similar one) into my patchset.

BTW, I googled to find the discussion related to your patch, but can't find
it at all. Where did you submit it to?

Thanks,
Yasuaki Ishimatsu

  parent reply	other threads:[~2007-07-20  5:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 12:20 [PATCH take3 0/12] Support vector domain on ia64 Yasuaki Ishimatsu
2007-07-17 17:40 ` Luck, Tony
2007-07-17 19:38 ` Eric W. Biederman
2007-07-18  6:47 ` Yasuaki Ishimatsu
2007-07-20  5:37 ` Yasuaki Ishimatsu [this message]
2007-07-20  5:52 ` Eric W. Biederman

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=46A04A11.7010505@jp.fujitsu.com \
    --to=isimatu.yasuaki@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