From: Anton Blanchard <anton@samba.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andrey Panin <pazke@orbita1.ru>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [RFC] irq handling code consolidation, second try (ppc part)
Date: Sun, 5 Jan 2003 11:25:34 +1100 [thread overview]
Message-ID: <20030105002534.GA4217@krispykreme> (raw)
In-Reply-To: <1041685293.641.17.camel@zion.wanadoo.fr>
> The "easy" way here to implement that is to make the irq_desc array
> larger than NR_IRQs (or rather split NR_IRQs into NR_SYS_IRQS +
> NR_DYNAMIC_IRQS). The additional "slots" could then easily be
> allocated/freed.
On ppc64 irqs are sparse and can be very large (> 1000) so we have a
mapping between them and slots in irq_desc[NR_IRQS]. I wonder how
hard it would be to kill irq_desc and just dynamically allocate
irq_desc stuff. That would solve my problem.
Anton
next prev parent reply other threads:[~2003-01-05 0:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-04 11:59 [RFC] irq handling code consolidation, second try (ppc part) Andrey Panin
2003-01-04 13:01 ` Benjamin Herrenschmidt
2003-01-04 17:41 ` Linus Torvalds
2003-01-05 8:56 ` Benjamin Herrenschmidt
2003-01-05 19:05 ` Linus Torvalds
2003-01-05 22:03 ` Benjamin Herrenschmidt
2003-01-05 0:25 ` Anton Blanchard [this message]
2003-01-05 0:50 ` Anton Blanchard
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=20030105002534.GA4217@krispykreme \
--to=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pazke@orbita1.ru \
--cc=torvalds@transmeta.com \
/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.