From: Jiang Liu <jiang.liu@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: Are we still willing to pay the cost of moving include/linux/irqdesc.h into kernel/irq/?
Date: Mon, 18 May 2015 17:48:36 +0800 [thread overview]
Message-ID: <5559B574.7070402@linux.intel.com> (raw)
Hi Thomas,
When refining irq related data structures, I found once we had
a plan to move include/linux/irqdesc.h into kernel/irq/, and I have
basic ideas about how to achieve the goal as:
1) de-inline accessor functions in irqdesc.h and move the declaration
into linux/irq.h.
2) remove reference to irq_desc->xxxx from drivers one by one (this
step is simple)
3) remove reference to irq_desc->xxxx from arch (this step is hard)
4) move irqdesc.h into kernel/irq/
But are we still willing to pay the cost of converting inline access
helpers into normal functions?
One possible tradeoff is to remove reference of irq_desc->xxxx from
drivers/, which is straight forward and shouldn't cause serious
performance regressions:)
Thanks!
Gerry
next reply other threads:[~2015-05-18 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 9:48 Jiang Liu [this message]
2015-05-18 14:46 ` Are we still willing to pay the cost of moving include/linux/irqdesc.h into kernel/irq/? Thomas Gleixner
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=5559B574.7070402@linux.intel.com \
--to=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--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