[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100719060426.GA19696@gondor.apana.org.au>
Date: Mon, 19 Jul 2010 14:04:26 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Dan Kruchinin <dkruchinin@....org>
Cc: Steffen Klassert <steffen.klassert@...unet.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] padata: cpumasks
On Wed, Jul 14, 2010 at 02:29:51PM +0400, Dan Kruchinin wrote:
> This is my third attempt to send padata cpumasks patchset.
> The patchset includes fixes of all unclear things Steffen noted in previous two patchsets.
> Changes:
>
> 1) Make two cpumasks in padata instead of one. The first cpumask is used by parallel workers and
> another is used by the workers doing serialization. Two distinguish cpumasks perform to build
> configuration where CPUs used by parallel and serial workers aren't intersect. It significantly
> improves performance.
> Each padata instance now includes notifier chain which can be used by users interested in instance's
> cpumask(serial or parallel) change. If one of cpumask is changed an event is generated.
>
> 2) Add sysfs primitives to padata. Each padata instance contains kobject which can be embedded to any
> proper sysfs hierarchy. Padata kobject can be used to change or show serial or parallel cpumask.
>
> 3) Add sysfs representation to pcrypt. Pcrypt now creates /sys/kernel/pcrypt/[pencrypt|pdecrypt] during
> module loading phase. pencrypt and pdecrypt directories are represented by kobjects of padata instances
> that belongs to pencrypt and pdecrypt respectively. Using this sysfs interface user can change and read
> serial and parallel cpumasks of both instances.
All applied. Thanks!
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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