From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: linux-mtd@lists.infradead.org,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Subject: Re: [PATCH] mtd: pxa3xx-nand: handle PIO in threaded interrupt
Date: Wed, 18 Feb 2015 18:16:17 +0100 [thread overview]
Message-ID: <87vbiz87j2.fsf@free.fr> (raw)
In-Reply-To: <20150218101646.GO25269@lukather> (Maxime Ripard's message of "Wed, 18 Feb 2015 11:16:46 +0100")
Maxime Ripard <maxime.ripard@free-electrons.com> writes:
> On Tue, Feb 17, 2015 at 09:06:57PM +0100, Robert Jarzmik wrote:
>> Change the handling of the data stage in the driver : don't pump data in
>> the top-half interrupt, but rather schedule a thread for non dma cases.
>>
>> This will enable latencies in the data pumping, especially if delays are
>> required. Moreover platform shall be more reactive as other interrupts
>> can be served while pumping data.
>>
>> No throughput degradation was observed, at least on the zylonite
>> platform, while a slight degradation was being expected.
>>
>> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
>
> Tested-by: Maxime Ripard <maxime.ripard@free-electrons.com>
>
> On a sidenote...
Thanks.
>> @@ -1672,7 +1688,8 @@ static int alloc_nand_resource(struct platform_device *pdev)
>> /* initialize all interrupts to be disabled */
>> disable_int(info, NDSR_MASK);
>>
>> - ret = request_irq(irq, pxa3xx_nand_irq, 0, pdev->name, info);
>> + ret = request_threaded_irq(irq, pxa3xx_nand_irq,
>> + pxa3xx_nand_irq_thread, 0, pdev->name, info);
>
> Using IRQF_ONESHOT would allow you not to do the interrupt enable /
> disable dance.
Yes, that's a very good point. Would your Tested-by still hold with this change ?
Cheers.
--
Robert
WARNING: multiple messages have this Message-ID (diff)
From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: pxa3xx-nand: handle PIO in threaded interrupt
Date: Wed, 18 Feb 2015 18:16:17 +0100 [thread overview]
Message-ID: <87vbiz87j2.fsf@free.fr> (raw)
In-Reply-To: <20150218101646.GO25269@lukather> (Maxime Ripard's message of "Wed, 18 Feb 2015 11:16:46 +0100")
Maxime Ripard <maxime.ripard@free-electrons.com> writes:
> On Tue, Feb 17, 2015 at 09:06:57PM +0100, Robert Jarzmik wrote:
>> Change the handling of the data stage in the driver : don't pump data in
>> the top-half interrupt, but rather schedule a thread for non dma cases.
>>
>> This will enable latencies in the data pumping, especially if delays are
>> required. Moreover platform shall be more reactive as other interrupts
>> can be served while pumping data.
>>
>> No throughput degradation was observed, at least on the zylonite
>> platform, while a slight degradation was being expected.
>>
>> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
>
> Tested-by: Maxime Ripard <maxime.ripard@free-electrons.com>
>
> On a sidenote...
Thanks.
>> @@ -1672,7 +1688,8 @@ static int alloc_nand_resource(struct platform_device *pdev)
>> /* initialize all interrupts to be disabled */
>> disable_int(info, NDSR_MASK);
>>
>> - ret = request_irq(irq, pxa3xx_nand_irq, 0, pdev->name, info);
>> + ret = request_threaded_irq(irq, pxa3xx_nand_irq,
>> + pxa3xx_nand_irq_thread, 0, pdev->name, info);
>
> Using IRQF_ONESHOT would allow you not to do the interrupt enable /
> disable dance.
Yes, that's a very good point. Would your Tested-by still hold with this change ?
Cheers.
--
Robert
next prev parent reply other threads:[~2015-02-18 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 20:06 [PATCH] mtd: pxa3xx-nand: handle PIO in threaded interrupt Robert Jarzmik
2015-02-17 20:06 ` Robert Jarzmik
2015-02-18 10:16 ` Maxime Ripard
2015-02-18 10:16 ` Maxime Ripard
2015-02-18 17:16 ` Robert Jarzmik [this message]
2015-02-18 17:16 ` Robert Jarzmik
2015-02-19 11:17 ` Maxime Ripard
2015-02-19 11:17 ` Maxime Ripard
2015-02-18 11:42 ` Ezequiel Garcia
2015-02-18 16:09 ` Robert Jarzmik
2015-02-18 16:09 ` Robert Jarzmik
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=87vbiz87j2.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=maxime.ripard@free-electrons.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.