From: Jarek Poplawski <jarkao2@o2.pl>
To: "Jeffrey V\. Merkey" <jmerkey@wolfmountaingroup.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Recursive spinlocks for Network Recursion Bugs in 2.6.18
Date: Tue, 12 Dec 2006 10:20:14 +0100 [thread overview]
Message-ID: <20061212092014.GA1922@ff.dom.local> (raw)
In-Reply-To: <457A6637.3060101@wolfmountaingroup.com>
On 09-12-2006 08:31, Jeffrey V. Merkey wrote:
>
>
> This code segment in /net/core/dev.c is a prime example of the need for
> recursive spin locks.
...
> Recursive spinlocks perform the logic
...
> LONG rspin_lock(rlock_t *rlock)
...
> LONG rspin_unlock(rlock_t *rlock)
...
Could you give some hint how this code from dev.c
should be changed to gain by this?
Jarek P.
prev parent reply other threads:[~2006-12-12 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 7:31 Recursive spinlocks for Network Recursion Bugs in 2.6.18 Jeffrey V. Merkey
2006-12-12 9:20 ` Jarek Poplawski [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=20061212092014.GA1922@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=jmerkey@wolfmountaingroup.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.