mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jiang Liu <jiang.liu@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Are we still willing to pay the cost of moving include/linux/irqdesc.h into kernel/irq/?
Date: Mon, 18 May 2015 16:46:42 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1505181635480.4225@nanos> (raw)
In-Reply-To: <5559B574.7070402@linux.intel.com>

Jiang,

On Mon, 18 May 2015, Jiang Liu wrote:

> 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

I had that plan for two reasons:

  1) Is was tired of chasing the abuse of irq_desc

  2) We wanted to move irq descriptor memory allocation when
     affinity changes to a different node.

> 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)

Not sure. drivers/irqchip pretty much needs it and we have other
demeltiplex handlers which need it as well.

> 3) remove reference to irq_desc->xxxx from arch (this step is hard)

Same issue as #2

> 4) move irqdesc.h into kernel/irq/
> 
> But are we still willing to pay the cost of converting inline access
> helpers into normal functions?

I dont think so.

Thanks,

	tglx

      reply	other threads:[~2015-05-18 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18  9:48 Jiang Liu
2015-05-18 14:46 ` Thomas Gleixner [this message]

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=alpine.DEB.2.11.1505181635480.4225@nanos \
    --to=tglx@linutronix.de \
    --cc=jiang.liu@linux.intel.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®