From: Steffen Klassert <steffen.klassert@secunet.com>
To: Dan Kruchinin <dkruchinin@acm.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Herbert Xu <herbert@gondor.hengli.com.au>
Subject: Re: [PATCH 1/3] padata: separate serial and parallel cpumasks
Date: Tue, 6 Jul 2010 09:46:41 +0200 [thread overview]
Message-ID: <20100706074641.GS10072@secunet.com> (raw)
In-Reply-To: <AANLkTil4pbOOVvhIKN1_sI8kNdBFFebMVEGEmqrb45YR@mail.gmail.com>
On Tue, Jul 06, 2010 at 11:40:11AM +0400, Dan Kruchinin wrote:
> >> >
> >>
> >> I think we can use RCU anyway. For instance we could use a structure
> >>
> >> struct pcrypt_cpumask {
> >> cpumask_var_t pmask;
> >> cpumask_var_t smask;
> >> };
> >>
> >> and add a pointer to a structure of that type to the instance context.
> >> Then we could use this pointer for RCU and replace the whole structure
> >> if a cpumask changes.
>
> But is pcrypt interested pmask? If it isn't, pmask field will be unused.
>
It's probaply not, in this case the struct could look like
struct pcrypt_cpumask {
cpumask_var_t smask;
};
next prev parent reply other threads:[~2010-07-06 7:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikeDE4hvZ3spyTBSHZsdQPc-2wlD5nTfb1aF-VD@mail.gmail.com>
2010-07-02 8:53 ` [PATCH 1/3] padata: separate serial and parallel cpumasks Steffen Klassert
[not found] ` <AANLkTinyPGjXjlvJxB8WYB3EYFBtANXMzpTdUixyBRHW@mail.gmail.com>
2010-07-02 9:17 ` Steffen Klassert
2010-07-02 9:32 ` Dan Kruchinin
2010-07-02 9:34 ` Dan Kruchinin
2010-07-02 11:11 ` Steffen Klassert
2010-07-02 13:01 ` Dan Kruchinin
2010-07-05 10:58 ` Steffen Klassert
[not found] ` <AANLkTimEgKGJ5pi7GzOnvP42ivJ4GCKX59LdKK0x4fnx@mail.gmail.com>
[not found] ` <20100706053612.GQ10072@secunet.com>
2010-07-06 5:44 ` Steffen Klassert
2010-07-06 7:40 ` Dan Kruchinin
2010-07-06 7:46 ` Steffen Klassert [this message]
2010-07-06 8:31 ` Dan Kruchinin
2010-07-06 13:28 ` Steffen Klassert
2010-07-06 16:30 ` Dan Kruchinin
2010-07-07 13:16 ` Steffen Klassert
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=20100706074641.GS10072@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=dkruchinin@acm.org \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@vger.kernel.org \
/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