[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20150129.143229.481822772678018170.davem@davemloft.net>
Date: Thu, 29 Jan 2015 14:32:29 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: xander.huff@...com
Cc: gregkh@...e.de, jeff.westfahl@...com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, jaeden.amero@...com,
ben.shelton@...com, brad.mouring@...com, rich.tollerton@...com
Subject: Re: [PATCH 1/2] driver core: add device_poll interface
From: Xander Huff <xander.huff@...com>
Date: Mon, 26 Jan 2015 16:46:32 -0600
> From: Jeff Westfahl <jeff.westfahl@...com>
>
> Add the device_poll interface to the driver core. This is a generic
> interface that any struct device can take advantage of to dynamically
> switch between using interrupts and polling. Many drivers can be easily
> modified to take advantage of this feature if desired.
>
> This interface is most likely to be used along with the RT patch. It has
> only been used thus far on Ethernet interfaces. Even with the standard
> RT change to threaded interrupts for all devices, some RT applications
> can be sensitive to even the minimal hardware interrupt that still occurs
> with threaded interrupt handlers. The device_poll interface can be used
> to completely eliminate all hardware interrupts for a device and the
> associated jitter.
>
> This is a standalone feature that should be submitted for review and
> possible inclusion in mainline, or maybe in the RT patch.
>
> Signed-off-by: Jeff Westfahl <jeff.westfahl@...com>
There is no reason any device driver needs to explicitly add support
for a feature like this.
Implement this at the IRQ handler level, and run the IRQ handler
itself from the poll thread.
No driver changes at all.
Sorry, I'm not applying this series, drivers already have to implement
too many things explicitly these days.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists