lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9c3a7c20903191008y5262a991ufefd17254075c977@mail.gmail.com>
Date:	Thu, 19 Mar 2009 10:08:59 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org,
	neilb@...e.de, maciej.sosnowski@...el.com
Subject: Re: [PATCH 00/13] Asynchronous raid6 acceleration (part 1 of 2)

On Wed, Mar 18, 2009 at 4:43 PM, Andi Kleen <andi@...stfloor.org> wrote:
> Dan Williams <dan.j.williams@...el.com> writes:
>
>> This series constitutes the pieces of the raid6 acceleration work that are
>> aimed at the next merge window.  It implements:
>> 1/ An api for asynchronous raid6 parity generation and recovery routines
>
> Could you please comment a bit how well the default load balancing works. If
> I write a single stream from a single CPU will it use multiple CPU
> cores in the system to do the RAID6 work?

No, that is an item for the todo list.  This implementation is only
asynchronous when a raid6 hardware offload resource is available, when
this is not the case it runs synchronous/single-threaded.  In general
the api is meant to inherit the load balancing of the caller.  For
md/raid6 this is currently always single threaded for writes and
degraded reads regardless of the number of requesting threads.

This work does make some progress towards multithreaded raid6 in that
calculations can now be preempted (i.e. no longer performed under the
stripe spin_lock).

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ