From: Jiang Liu <jiang.liu@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <marc.zyngier@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Proposal about reorganize struct irq_data and struct irq_desc
Date: Mon, 19 Jan 2015 22:19:02 +0800 [thread overview]
Message-ID: <54BD1256.1020406@linux.intel.com> (raw)
Hi Thomas and Marc,
During working on the generic MSI support, I have some proposal
about reorganizing struct irq_data and struct irq_desc. The proposed
changes are:
1) Add a pointer "struct irq_desc *" to struct irq_data, so we could
quickly get struct irq_desc from struct irq_data.
2) Move "node" from struct irq_data into struct irq_desc, NUMA info
should be per-irq instead of per-chip.
3) Move "affinity" from struct irq_data into struct irq_desc, NUMA info
should be per-irq instead of per-chip.
4) Move "msi_desc" from struct irq_data into struct irq_desc. (Not sure
whether we should do this. Theoretically we should use
irq_data->handler_data to store msi_desc.)
With above change applied, struct irq_data only hosts per-chip data, and
struct irq_desc hosts per-irq data. What's your thoughts?
Regards,
Gerry
next reply other threads:[~2015-01-19 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 14:19 Jiang Liu [this message]
2015-01-20 9:31 ` Thomas Gleixner
2015-01-20 10:02 ` Jiang Liu
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=54BD1256.1020406@linux.intel.com \
--to=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome