From: David Miller <davem@davemloft.net>
To: mingo@elte.hu
Cc: herbert@gondor.apana.org.au, stefanr@s5r6.in-berlin.de,
Valdis.Kletnieks@vt.edu, jirislaby@gmail.com, akpm@osdl.org,
arjan@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: 2.6.17-rc5-mm3-lockdep -
Date: Sun, 11 Jun 2006 23:50:05 -0700 (PDT) [thread overview]
Message-ID: <20060611.235005.51843280.davem@davemloft.net> (raw)
In-Reply-To: <20060612063807.GA23939@elte.hu>
From: Ingo Molnar <mingo@elte.hu>
Date: Mon, 12 Jun 2006 08:38:07 +0200
> yeah. I'll investigate - it's quite likely that sk_receive_queue.lock
> will have to get per-address family locking rules - right?
That's right.
> Maybe it's enough to introduce a separate key for AF_UNIX alone (and
> still having all other protocols share the locking rules for
> sk_receive_queue.lock) , by reinitializing its spinlock after
> sock_init_data()?
AF_NETLINK and/or AF_PACKET might be in a similar situation
as AF_UNIX.
next prev parent reply other threads:[~2006-06-12 6:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 2:50 Valdis.Kletnieks
2006-06-06 7:01 ` Jiri Slaby
2006-06-06 12:48 ` Stefan Richter
2006-06-06 16:39 ` Stefan Richter
2006-06-07 7:12 ` Herbert Xu
2006-06-12 6:38 ` Ingo Molnar
2006-06-12 6:41 ` Herbert Xu
2006-06-12 6:57 ` [patch] undo AF_UNIX _bh locking changes and split lock-type instead Ingo Molnar
2006-06-12 7:03 ` Herbert Xu
2006-06-12 7:18 ` David Miller
2006-06-12 8:49 ` Ingo Molnar
2006-06-12 20:08 ` David Miller
2006-06-12 6:50 ` David Miller [this message]
2006-06-06 13:01 ` 2.6.17-rc5-mm3-lockdep - Valdis.Kletnieks
2006-06-06 13:45 ` Jiri Slaby
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=20060611.235005.51843280.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®