[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9c3a7c20903211514p60fda2fbhc5039c16f708e81d@mail.gmail.com>
Date: Sat, 21 Mar 2009 15:14:24 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Ilya Yanok <yanok@...raft.com>,
"H. Peter Anvin" <h.peter.anvin@...el.com>,
"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"neilb@...e.de" <neilb@...e.de>,
"Sosnowski, Maciej" <maciej.sosnowski@...el.com>,
Yuri Tikhonov <yur@...raft.com>
Subject: Re: [PATCH 06/13] async_tx: add support for asynchronous GF
multiplication
On Sat, Mar 21, 2009 at 12:15 PM, H. Peter Anvin <hpa@...or.com> wrote:
> Why does it? I don't see why you'd need to cover the vector-vector case
> at all, since it doesn't appear anywhere in the algorithms. Certainly
> going backwards from a vector-vector set to derive if you can do a
> scalar-vector multiply when you should have known that in the first
> place is not really useful.
>
>>
>> Looking closer, the only other caller, async_pq_zero_sum, can be
>> deleted because it has no users. So async_pq can become a static
>> routine in async_r6recov.
>>
>
> That's another issue entirely, of course :)
>
...ah, but now I see your point and the root cause of the problem.
The caller needs to be modified to only require scalar multiplication
even in this corner case.
Thanks,
Dan
--
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