On Tue, Jun 4, 2013 at 8:11 PM, Dan Williams wrote:
> On 6/4/13 12:25 AM, "Andy Shevchenko" wrote:
>>On Tue, Jun 4, 2013 at 2:29 AM, Jon Mason wrote:
>>> On Fri, May 31, 2013 at 11:22:10AM +0300, Andy Shevchenko wrote:
[]
>>> Since the testing is started immediately upon module
>>> insertion,
On 6/4/13 12:25 AM, "Andy Shevchenko" wrote:
>On Tue, Jun 4, 2013 at 2:29 AM, Jon Mason wrote:
>> On Fri, May 31, 2013 at 11:22:10AM +0300, Andy Shevchenko wrote:
>>> On Fri, May 17, 2013 at 8:54 PM, Jon Mason wrote:
>>> > dmatest would create a thread to stress XOR and PQ, if the
>>>capabilit
On Tue, Jun 4, 2013 at 2:29 AM, Jon Mason wrote:
> On Fri, May 31, 2013 at 11:22:10AM +0300, Andy Shevchenko wrote:
>> On Fri, May 17, 2013 at 8:54 PM, Jon Mason wrote:
>> > dmatest would create a thread to stress XOR and PQ, if the capability is
>> > present in the hardware. Add the ability to
On Fri, May 31, 2013 at 11:22:10AM +0300, Andy Shevchenko wrote:
> On Fri, May 17, 2013 at 8:54 PM, Jon Mason wrote:
> > dmatest would create a thread to stress XOR and PQ, if the capability is
> > present in the hardware. Add the ability to disable XOR and PQ by
> > disabling it if *_sources are
On Fri, May 17, 2013 at 8:54 PM, Jon Mason wrote:
> dmatest would create a thread to stress XOR and PQ, if the capability is
> present in the hardware. Add the ability to disable XOR and PQ by
> disabling it if *_sources are set to zero.
Sorry, didn't comment this earlier.
Those threads are ind
dmatest would create a thread to stress XOR and PQ, if the capability is
present in the hardware. Add the ability to disable XOR and PQ by
disabling it if *_sources are set to zero.
Signed-off-by: Jon Mason
---
drivers/dma/dmatest.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
6 matches
Mail list logo