On 05/26/2015 07:31 PM, Dan Williams wrote:
> [ adding Boaz as this discussion has implications for ore_raid ]
>
<>
>> You're not talking about deprecating it, you're talking about removing
>> it entirely.
>
> True, and adding more users makes that removal more difficult. I'm
> willing to help o
On 03/11/2015 03:39 PM, Sasha Levin wrote:
> On 03/11/2015 08:40 AM, Steven Rostedt wrote:
>> On Wed, 11 Mar 2015 08:34:46 -0400
>> Sasha Levin wrote:
>>
Fair enough. We knew there are existing kmemcheck users, but KASan should
be
superior both in performance and the scope of bugs
(finally)
Thanks
Boaz
> commit 60e833d86a01ad9d8204a04b8db324106ab50395
> Author: Boaz Harrosh
> AuthorDate: Thu Jul 19 15:22:37 2012 +0300
> Commit: Boaz Harrosh
> CommitDate: Tue Apr 8 08:42:14 2014 +0300
>
> RFC: do_xor_speed Broken on UML do to jiffies
>
On 11/26/2013 12:37 PM, Yuanhan Liu wrote:
>
> If you like, I can add you into the build-notify list. Once the build
> finished, you might get an email like following:
>
> --yliu
Na, its fine. thanks though
Cheers
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-cr
On 11/25/2013 04:15 PM, Richard Weinberger wrote:
> On Fri, Nov 22, 2013 at 7:02 AM, Yuanhan Liu
> wrote:
>> Greetings,
>>
>> I got the below dmesg and the first bad commit is
>>
>> commit 20545536cd8ea949c61527b6395ec8c0d2c237b1
>> Author: Boaz Harrosh
On 11/25/2013 03:25 PM, Yuanhan Liu wrote:
>
> Hi Boaz,
>
> We are running an 0day kernel testing system. We will test all developers'
> tree we tracked in our system automatically. And obviously, linux-open-osd
> is in that list.
>
> This system can't tell whether a branch is experimental unles
On 11/22/2013 08:02 AM, Yuanhan Liu wrote:
> Greetings,
>
> I got the below dmesg and the first bad commit is
>
> commit 20545536cd8ea949c61527b6395ec8c0d2c237b1
> Author: Boaz Harrosh
> Date: Thu Jul 19 15:22:37 2012 +0300
>
> RFC: do_xor_speed Broken on UML d
On 10/10/2013 06:29 PM, Fengguang Wu wrote:
>
> I'm running kernel build/boot/performance tests for *all* the public
> kernel git trees I'm aware of. If this is not necessary for your tree
> or some of the branches, sorry I can remove them from the test pool.
>
>> I can see below:
>> Merge '
this patch, again it is so I can run exofs on UML which uses
xor.ko. If you use VMs or HW you do not have this problem.
Thanks
Boaz
> commit 20545536cd8ea949c61527b6395ec8c0d2c237b1
> Author: Boaz Harrosh
> Date: Thu Jul 19 15:22:37 2012 +0300
>
> RFC: do_xor_speed Broken
On 04/06/2012 11:43 PM, Dan Williams wrote:
> [adding Boaz since he also made an attempt at fixing this]
>
> http://marc.info/?l=linux-crypto-vger&m=13182924450&w=2
>
> ...I had meant to follow up on this, but was buried in 'isci' issues.
>
>
Sorry was traveling.
Yes I have an old fix f
e how I put several safety
guards, to never get hangs again.
And I think my time based approach is more accurate then
previous system.
UML guys please investigate the jiffies issue? what is
xor.ko not doing right?
Signed-off-by: Boaz Harrosh
---
crypto/xor.c |
On Mon, Oct 29 2007 at 22:16 +0200, Jens Axboe <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 26 2007, Herbert Xu wrote:
>> [CRYPTO] tcrypt: Move sg_init_table out of timing loops
>>
>> This patch moves the sg_init_table out of the timing loops for hash
>> algorithms so that it doesn't impact on the spee
12 matches
Mail list logo
