From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] [PATCHv2 no pgp] batman-adv: receive packets directly using skbs
Date: Thu, 31 Dec 2009 12:17:55 +0100 [thread overview]
Message-ID: <20091231111755.GA1884@lunn.ch> (raw)
In-Reply-To: <20091229154328.GA17851@WGT634U>
> I try to summarize where each lock is used so we can decide if it is ok to
> revert some of them to spin_lock again. This should also resolve a request I
> got from Andrew some time ago.
Hi Sven
Thanks for this.
[...]
> So it is complete correct to use irqsave everywhere (as you have commited it
> now).
This also means we don't need to worry about the order we take
spinlocks in resulting in deadlocks. Since we disable interrupts, it
is not possible for some other thread to be holding a lock we need.
Andrew
prev parent reply other threads:[~2009-12-31 11:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-27 17:23 [B.A.T.M.A.N.] [PATCHv2] batman-adv: receive packets directly using skbs Simon Wunderlich
2009-12-28 15:10 ` [B.A.T.M.A.N.] [PATCHv2 no pgp] " Simon Wunderlich
2009-12-29 15:05 ` Simon Wunderlich
2009-12-29 15:43 ` Sven Eckelmann
2009-12-31 11:17 ` Andrew Lunn [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=20091231111755.GA1884@lunn.ch \
--to=andrew@lunn.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/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