From: Richard MUSIL <richard.musil@st.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] GENETLINK: Global lock refined to family granularity
Date: Mon, 31 Mar 2008 18:14:40 +0200 [thread overview]
Message-ID: <47F10DF0.2040102@st.com> (raw)
In-Reply-To: <20080331122648.GA20815@postel.suug.ch>
On 31.3.2008 14:26, Thomas Graf wrote:
> * Richard MUSIL <richard.musil@st.com> 2008-03-31 13:21
>> It takes two locks, instead of one. I do not see, how it could be less
>> (in terms of synchronization primitives - but not necessarily mutexes)
>> if I want that level of granularity. Might be more efficient with RCU
>> lists (but I do not know), but complexity remains the same.
>
> The synchronization mutex in genl_recv() remains and you add an
> additional global mutex genl_fam_lock and a per family lock. That's
> 2 vs 6 lock operations. It is possible to use RCU to manage the
Shame on me, I should know better (what my patch is doing). You are
right, the global lock in genl_recv remains. I guess my further
arguments are now irrelevant.
Concerning the RCU lists, I am also for better solution, the problem is,
I have never used them before, so the probability I will do it right, is
far small - but I may give it try.
<skipped the most since it is no longer relevant>
> I'm not against the idea, I just feel that the gains in your patch in
> its current form do not justify the additional locking and complextity
> costs. Combined with parallel processing and RCU lists it would be a
> no brainer and probably merged instantly.
Ok, I will see, what I can do.
Richard
prev parent reply other threads:[~2008-03-31 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 12:05 [PATCH] GENETLINK: Global lock refined to family granularity Richard MUSIL
2008-03-28 3:29 ` David Miller
2008-03-31 10:33 ` Thomas Graf
2008-03-31 11:21 ` Richard MUSIL
2008-03-31 12:26 ` Thomas Graf
2008-03-31 16:14 ` Richard MUSIL [this message]
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=47F10DF0.2040102@st.com \
--to=richard.musil@st.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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;
as well as URLs for NNTP newsgroup(s).