On Fri, Jul 31, 2015 at 06:56:33PM -0400, Benjamin Romer wrote:
> From: Neil Horman
>
> Switch the visornic over to use napi. Currently there is a kernel
> thread
> that sits and waits on a wait queue to get notified of incoming virtual
> interrupts. It would be nice if we could handle frame rec
On Sat, Aug 01, 2015 at 08:55:09AM -0700, Greg KH wrote:
> On Sat, Aug 01, 2015 at 09:36:19AM -0400, Neil Horman wrote:
> > On Fri, Jul 31, 2015 at 09:41:10PM -0400, Neil Horman wrote:
> > > On Fri, Jul 31, 2015 at 06:56:33PM -0400, Benjamin Romer wrote:
> > > > From: Neil Horman
> > > >
> > > >
On Sat, Aug 01, 2015 at 09:36:19AM -0400, Neil Horman wrote:
> On Fri, Jul 31, 2015 at 09:41:10PM -0400, Neil Horman wrote:
> > On Fri, Jul 31, 2015 at 06:56:33PM -0400, Benjamin Romer wrote:
> > > From: Neil Horman
> > >
> > > Switch the visornic over to use napi. Currently there is a kernel
>
On Fri, Jul 31, 2015 at 09:41:10PM -0400, Neil Horman wrote:
> On Fri, Jul 31, 2015 at 06:56:33PM -0400, Benjamin Romer wrote:
> > From: Neil Horman
> >
> > Switch the visornic over to use napi. Currently there is a kernel
> > thread
> > that sits and waits on a wait queue to get notified of inc
On Fri, Jul 31, 2015 at 06:56:33PM -0400, Benjamin Romer wrote:
> From: Neil Horman
>
> Switch the visornic over to use napi. Currently there is a kernel
> thread
> that sits and waits on a wait queue to get notified of incoming virtual
> interrupts. It would be nice if we could handle frame rec
From: Neil Horman
Switch the visornic over to use napi. Currently there is a kernel
thread
that sits and waits on a wait queue to get notified of incoming virtual
interrupts. It would be nice if we could handle frame reception using
the
standard napi processing instead. This patch creates our n
