All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lina Iyer <lina.iyer@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: khilman@linaro.org, ulf.hansson@linaro.org,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, rjw@rjwysocki.net,
	daniel.lezcano@linaro.org
Subject: Re: [PATCH v3 3/4] irq: Allow multiple clients to register for irq affinity notification
Date: Mon, 17 Nov 2014 23:22:05 -0700	[thread overview]
Message-ID: <20141118062205.GA770@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1410170926220.2806@nanos>

Hi Thomas,

On Fri, Oct 17 2014 at 01:29 -0600, Thomas Gleixner wrote:
>On Fri, 10 Oct 2014, Lina Iyer wrote:
>> On Wed, Oct 08 2014 at 09:03 -0600, Thomas Gleixner wrote:
>> > On Thu, 25 Sep 2014, Lina Iyer wrote:
>> > > > How would a general "keep track of the targets of all interrupts in
>> > > > the system" mechanism make use of this?
>> > > Sorry, I do not understand your question.
>> > > PM QoS is only interested in the IRQs specified in the QoS request. If
>> > > there are no requests that need to be associated with an IRQ, then PM
>> > > QoS will not register for an affinity change notification.
>> >
>> > Right, and I really hate the whole per irq notifier. It's a rats nest
>> > of life time issues and other problems.
>> >
>> > It also does not tell you whether an irq is disabled, reenabled or
>> > removed, which will change the qos constraints as well unless you
>> > plaster all drivers with updates to qos for those cases.
>> >
>> > So what about adding a qos field to irq_data itself, have a function
>> > to update it and let the irq core keep track of the per cpu irq
>> > relevant qos constraints and provide an evaluation function or a
>> > notifier for the PM/idle code?
>>
>> If that isnt intrusive in the IRQ core, then we can make it work for PM
>> QoS. The issue that I am concerned is that, it might result in back and
>> forth between IRQ and PM QoS frameworks. If that doesnt happen, then we
>> are good with this approach.
>
>I can't tell that upfront, but I think it's worth to explore it.
>
I was able to review the options and I attempted a few methods, but
off-loading the QoS onto the IRQ framework, made it quite complex to
manage it. QoS values for each of the four constraints and the
constraints could be one of 3 types - min, max or sum, makes it a whole
lot of mess handling it in IRQ code.

I was able to get QoS to be notified of IRQ affinity changes without
using notifiers, but, I still am yet to find a way to modify QoS
requests on enable/disable of IRQ.

I will send the RFC of the new patchset, would be interested in taking a
look and let me know what you think.

Thanks,
Lina

WARNING: multiple messages have this Message-ID (diff)
From: lina.iyer@linaro.org (Lina Iyer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/4] irq: Allow multiple clients to register for irq affinity notification
Date: Mon, 17 Nov 2014 23:22:05 -0700	[thread overview]
Message-ID: <20141118062205.GA770@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1410170926220.2806@nanos>

Hi Thomas,

On Fri, Oct 17 2014 at 01:29 -0600, Thomas Gleixner wrote:
>On Fri, 10 Oct 2014, Lina Iyer wrote:
>> On Wed, Oct 08 2014 at 09:03 -0600, Thomas Gleixner wrote:
>> > On Thu, 25 Sep 2014, Lina Iyer wrote:
>> > > > How would a general "keep track of the targets of all interrupts in
>> > > > the system" mechanism make use of this?
>> > > Sorry, I do not understand your question.
>> > > PM QoS is only interested in the IRQs specified in the QoS request. If
>> > > there are no requests that need to be associated with an IRQ, then PM
>> > > QoS will not register for an affinity change notification.
>> >
>> > Right, and I really hate the whole per irq notifier. It's a rats nest
>> > of life time issues and other problems.
>> >
>> > It also does not tell you whether an irq is disabled, reenabled or
>> > removed, which will change the qos constraints as well unless you
>> > plaster all drivers with updates to qos for those cases.
>> >
>> > So what about adding a qos field to irq_data itself, have a function
>> > to update it and let the irq core keep track of the per cpu irq
>> > relevant qos constraints and provide an evaluation function or a
>> > notifier for the PM/idle code?
>>
>> If that isnt intrusive in the IRQ core, then we can make it work for PM
>> QoS. The issue that I am concerned is that, it might result in back and
>> forth between IRQ and PM QoS frameworks. If that doesnt happen, then we
>> are good with this approach.
>
>I can't tell that upfront, but I think it's worth to explore it.
>
I was able to review the options and I attempted a few methods, but
off-loading the QoS onto the IRQ framework, made it quite complex to
manage it. QoS values for each of the four constraints and the
constraints could be one of 3 types - min, max or sum, makes it a whole
lot of mess handling it in IRQ code.

I was able to get QoS to be notified of IRQ affinity changes without
using notifiers, but, I still am yet to find a way to modify QoS
requests on enable/disable of IRQ.

I will send the RFC of the new patchset, would be interested in taking a
look and let me know what you think.

Thanks,
Lina

  reply	other threads:[~2014-11-18  6:22 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 20:14 [PATCH v3 0/4] PM QoS: per-cpu PM QoS support Lina Iyer
2014-08-27 20:14 ` Lina Iyer
2014-08-27 20:14 ` [PATCH v3 1/4] QoS: Modify data structures and function arguments for scalability Lina Iyer
2014-08-27 20:14   ` Lina Iyer
2014-08-27 20:14 ` [PATCH v3 2/4] QoS: Enhance framework to support per-cpu PM QoS request Lina Iyer
2014-08-27 20:14   ` Lina Iyer
2014-08-27 20:14 ` [PATCH v3 3/4] irq: Allow multiple clients to register for irq affinity notification Lina Iyer
2014-08-27 20:14   ` Lina Iyer
2014-08-27 20:56   ` Thomas Gleixner
2014-08-27 20:56     ` Thomas Gleixner
2014-09-02 18:43     ` Lina Iyer
2014-09-02 18:43       ` Lina Iyer
2014-09-02 20:56       ` Thomas Gleixner
2014-09-02 20:56         ` Thomas Gleixner
     [not found]         ` <20140924221023.GD1004@ilina-mac.local>
2014-09-25 15:43           ` Lina Iyer
2014-09-25 15:43             ` Lina Iyer
2014-09-25 15:50         ` Lina Iyer
2014-09-25 15:50           ` Lina Iyer
2014-10-08 15:03           ` Thomas Gleixner
2014-10-08 15:03             ` Thomas Gleixner
2014-10-10 15:11             ` Lina Iyer
2014-10-10 15:11               ` Lina Iyer
2014-10-17  7:29               ` Thomas Gleixner
2014-10-17  7:29                 ` Thomas Gleixner
2014-11-18  6:22                 ` Lina Iyer [this message]
2014-11-18  6:22                   ` Lina Iyer
2014-09-25 20:35         ` Kevin Hilman
2014-09-25 20:35           ` Kevin Hilman
2014-09-26  9:29           ` Thomas Gleixner
2014-09-26  9:29             ` Thomas Gleixner
2014-09-26  9:40             ` Russell King - ARM Linux
2014-09-26  9:40               ` Russell King - ARM Linux
2014-09-26 15:10               ` Kevin Hilman
2014-09-26 15:10                 ` Kevin Hilman
2014-10-08 14:20               ` Thomas Gleixner
2014-10-08 14:20                 ` Thomas Gleixner
2014-08-27 20:14 ` [PATCH v3 4/4] QoS: Enable PM QoS requests to apply only on smp_affinity of an IRQ Lina Iyer
2014-08-27 20:14   ` Lina Iyer

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=20141118062205.GA770@linaro.org \
    --to=lina.iyer@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --cc=ulf.hansson@linaro.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 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.