From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] performance patches (v3)
Date: Mon, 13 Dec 2010 01:18:14 +0100 [thread overview]
Message-ID: <201012130118.14949.lindner_marek@yahoo.de> (raw)
Hi,
the performance patches progress step by step. A few patches already went into
the repository the rest is waiting for more review. Thanks to Sven's feedback
quite some bugs were squashed.
Changes since v2:
* code rebased on top of the trunk
* some more neigh_node protected by reference counters
* call_rcu and kref_put race condition fixed
Known issues:
* bonding / alternating candidates are not secured by refcounting [see
find_router()] - ideas welcome
Regards,
Marek
next reply other threads:[~2010-12-13 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 0:18 Marek Lindner [this message]
2010-12-13 0:18 ` [B.A.T.M.A.N.] [PATCH 1/5] batman-adv: protect neigh_nodes used outside of rcu_locks with refcounting Marek Lindner
2010-12-13 0:18 ` [B.A.T.M.A.N.] [PATCH 2/5] batman-adv: protect each hash row with rcu locks Marek Lindner
2010-12-13 0:18 ` [B.A.T.M.A.N.] [PATCH 3/5] batman-adv: protect originator nodes with reference counters Marek Lindner
2010-12-13 0:18 ` [B.A.T.M.A.N.] [PATCH 4/5] batman-adv: protect ogm counter arrays with spinlock Marek Lindner
2010-12-13 0:18 ` [B.A.T.M.A.N.] [PATCH 5/5] batman-adv: remove orig_hash spinlock Marek Lindner
2010-12-30 2:09 ` [B.A.T.M.A.N.] [PATCH] batman-adv: protect bonding with rcu locks Simon Wunderlich
2011-01-16 11:35 ` Marek Lindner
2011-01-16 11:36 ` [B.A.T.M.A.N.] [PATCH] batman-adv: protect bonding with rcu locks (proposal) Marek Lindner
2011-01-16 17:07 ` [B.A.T.M.A.N.] [PATCH] batman-adv: protect bonding with rcu locks Simon Wunderlich
2011-01-19 20:07 ` [B.A.T.M.A.N.] performance patches (v3) Marek Lindner
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=201012130118.14949.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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;
as well as URLs for NNTP newsgroup(s).