On Thu, 20 Feb 2014, Dan Williams wrote:
> On Thu, Feb 20, 2014 at 2:30 AM, Thomas Gleixner wrote:
> > That's 18 of 30 usage sites. Impressive
> >
> > We need to poke the relevant maintainers to get this solved.
> >
>
> Maybe also rename tasklet_disable() to tasklet_pause() to make it
>
On Thu, 20 Feb 2014, Dan Williams wrote:
On Thu, Feb 20, 2014 at 2:30 AM, Thomas Gleixner t...@linutronix.de wrote:
That's 18 of 30 usage sites. Impressive
We need to poke the relevant maintainers to get this solved.
Maybe also rename tasklet_disable() to tasklet_pause() to make it
On Thu, Feb 20, 2014 at 2:30 AM, Thomas Gleixner wrote:
> B1;3202;0cOn Wed, 19 Feb 2014, Dan Williams wrote:
>
>> Since commit 77873803363c "net_dma: mark broken" we no longer pin dma
>> engines active for the network-receive-offload use case. As a result
>> the ->free_chan_resources() that
B1;3202;0cOn Wed, 19 Feb 2014, Dan Williams wrote:
> Since commit 77873803363c "net_dma: mark broken" we no longer pin dma
> engines active for the network-receive-offload use case. As a result
> the ->free_chan_resources() that occurs after the driver self-test no
> longer has a NET_DMA induced
> Passes my testing, but would appreciate a tested-by.
Tested-by: Stanislav Fomichev
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
That was quick. Afflicted box is now a happy camper.
(gee, systemd isn't _completely_ evil, it dug up a bug;)
Tested-by: Mike Galbraith
On Wed, 2014-02-19 at 23:13 -0800, Dan Williams wrote:
> Since commit 77873803363c "net_dma: mark broken" we no longer pin dma
> engines active for the
That was quick. Afflicted box is now a happy camper.
(gee, systemd isn't _completely_ evil, it dug up a bug;)
Tested-by: Mike Galbraith bitbuc...@online.de
On Wed, 2014-02-19 at 23:13 -0800, Dan Williams wrote:
Since commit 77873803363c net_dma: mark broken we no longer pin dma
engines
Passes my testing, but would appreciate a tested-by.
Tested-by: Stanislav Fomichev stfomic...@yandex-team.ru
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
B1;3202;0cOn Wed, 19 Feb 2014, Dan Williams wrote:
Since commit 77873803363c net_dma: mark broken we no longer pin dma
engines active for the network-receive-offload use case. As a result
the -free_chan_resources() that occurs after the driver self-test no
longer has a NET_DMA induced
On Thu, Feb 20, 2014 at 2:30 AM, Thomas Gleixner t...@linutronix.de wrote:
B1;3202;0cOn Wed, 19 Feb 2014, Dan Williams wrote:
Since commit 77873803363c net_dma: mark broken we no longer pin dma
engines active for the network-receive-offload use case. As a result
the -free_chan_resources()
Since commit 77873803363c "net_dma: mark broken" we no longer pin dma
engines active for the network-receive-offload use case. As a result
the ->free_chan_resources() that occurs after the driver self-test no
longer has a NET_DMA induced ->alloc_chan_resources() to back it up. A
late firing irq
Since commit 77873803363c net_dma: mark broken we no longer pin dma
engines active for the network-receive-offload use case. As a result
the -free_chan_resources() that occurs after the driver self-test no
longer has a NET_DMA induced -alloc_chan_resources() to back it up. A
late firing irq can
12 matches
Mail list logo