public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kruchinin <dkruchinin@acm.org>
To: Steffen Klassert <steffen.klassert@secunet.com>,
	Herbert Xu <herbert@gondor.hengli.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] padata: cpumasks
Date: Wed, 14 Jul 2010 14:29:51 +0400	[thread overview]
Message-ID: <20100714142951.22817d0c@leibniz> (raw)

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.

-- 
W.B.R.
Dan Kruchinin

             reply	other threads:[~2010-07-14 10:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14 10:29 Dan Kruchinin [this message]
2010-07-19  6:04 ` [PATCH 0/3] padata: cpumasks Herbert Xu
2010-07-19  6:40   ` Steffen Klassert
2010-07-19  7:32     ` Herbert Xu
2010-07-20  6:47       ` [PATCH 0/4] padata/pcrypt: fixes Steffen Klassert
2010-07-20  6:48         ` [PATCH 1/4] padata: Fix cpu index counting Steffen Klassert
2010-07-20  6:49         ` [PATCH 2/4] padata: Allocate cpumask dependend recources in any case Steffen Klassert
2010-07-20  6:51         ` [PATCH 3/4] padata: Check for valid cpumasks Steffen Klassert
2010-07-20  6:52         ` [PATCH 4/4] crypto: pcrypt - Dont calulate a callback cpu on empty callback cpumask Steffen Klassert
2010-07-26  6:16         ` [PATCH 0/4] padata/pcrypt: fixes Herbert Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100714142951.22817d0c@leibniz \
    --to=dkruchinin@acm.org \
    --cc=akpm@linux-foundation.org \
    --cc=herbert@gondor.hengli.com.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox