From: Yinghai Lu <yinghai@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] irq: sparseirq enabling v2
Date: Wed, 26 Nov 2008 10:33:12 -0800 [thread overview]
Message-ID: <492D9668.1030904@kernel.org> (raw)
In-Reply-To: <20081126081724.GK26036@elte.hu>
Ingo Molnar wrote:
> * Yinghai Lu <yinghai@kernel.org> wrote:
>
>> Ingo Molnar wrote:
>>> * Yinghai Lu <yinghai@kernel.org> wrote:
>>>
>>>> impact: new feature sparseirq
>>>> v2: use pointer array instead of hash
>>> ok, this looks pretty good!
>>>
>>> A few details:
>>>
>>>> +#ifdef CONFIG_SPARSE_IRQ
>>>> +#define set_ioapic_affinity_irq set_ioapic_affinity_irq_desc
>>>> +#else
>>>> +static void set_ioapic_affinity_irq(unsigned int irq, cpumask_t mask)
>>>> +{
>>>> + struct irq_desc *desc;
>>>> +
>>>> + desc = irq_to_desc(irq);
>>>> +
>>>> + set_ioapic_affinity_irq_desc(desc, mask);
>>>> +}
>>>> +#endif
>>> i think this distinction can now go away?.
>> i may miss sth in your previous mail. you said we may put full hash
>> back later, so need keep those change to avoid lookup costs later.
>
> full hash as in no NR_IRQS limit?
32 bit irqs.
>
> I dont think that's a good idea even in the far future: we can always
> make NR_IRQS large enough, and turn the current array-of-pointers into
> array-of-arrays-of-pointers scheme or an outright hash - but without
> losing the fundamental abstraction that it's a 0..NR_IRQS array (just
> accessed abstractly).
>
>> also if we need move_irq_desc between node?
>
> i'm not sure i understand. Do you mean we should deallocate and
> reallocate the irq_desc to another node?
yes. the patch 2/2. [PATCH 2/2] irq: move irq_desc according to smp_affinity v2
>
>>>> +#ifdef CONFIG_SPARSE_IRQ
>>>> + irq_want = nr_irqs;
>>>> +#else
>>>> + irq_want = NR_IRQS - 1;
>>>> +#endif
>>> ditto. I think we dont want 'nr_irqs' anymore - just remain with
>>> NR_IRQS, right?
>>>
>> nr_irqs is the total GSI number when sparseirq is used. so MSI irq
>> will start from that. ...
>
> ah, okay. I think we should renumber MSIs to the scheme Thomas
> suggested, independently of CONFIG_SPARSE_IRQ.
good, will add one local nr_irqs_gsi there..., and not touch nr_irqs.
>
> CONFIG_SPARSE_IRQ should _only_ impact the irq_desc[] data structure:
> it turns from a flat C array of irq_desc into an array of irq_desc
> pointers.
>
> No other semantic changes. Possibly all hidden away completely in the
> irq-desc-array accessors.
YH
next prev parent reply other threads:[~2008-11-26 18:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 2:59 [PATCH 1/2] irq: sparseirq enabling Yinghai Lu
2008-11-24 14:40 ` Ingo Molnar
2008-11-24 19:22 ` Yinghai Lu
2008-11-24 22:26 ` Thomas Gleixner
2008-11-25 3:57 ` [PATCH 1/2] irq: sparseirq enabling v2 Yinghai Lu
2008-11-25 3:58 ` [PATCH 2/2] irq: move irq_desc according to smp_affinity v2 Yinghai Lu
2008-11-26 7:48 ` [PATCH 1/2] irq: sparseirq enabling v2 Ingo Molnar
2008-11-26 8:02 ` Yinghai Lu
2008-11-26 8:17 ` Ingo Molnar
2008-11-26 18:33 ` Yinghai Lu [this message]
2008-11-27 2:26 ` [PATCH 1/2] irq: sparseirq enabling v3 Yinghai Lu
2008-11-27 2:26 ` [PATCH 2/2] irq: move irq_desc according to smp_affinity v3 Yinghai Lu
2008-11-28 16:34 ` [PATCH 1/2] irq: sparseirq enabling v3 Ingo Molnar
2008-11-29 7:13 ` [PATCH] irq: sparseirq enabling v4 Yinghai Lu
2008-11-29 10:02 ` Ingo Molnar
2008-11-29 10:26 ` Ingo Molnar
2008-12-01 4:44 ` [PATCH] irq: sparse irq_desc[] support - fix Yinghai Lu
2008-11-29 10:57 ` [PATCH] irq: sparseirq enabling v4 Sam Ravnborg
2008-11-29 14:33 ` Ingo Molnar
2008-11-29 17:54 ` Sam Ravnborg
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=492D9668.1030904@kernel.org \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.