From: David Miller <davem@davemloft.net>
To: sven.eckelmann@gmx.de
Cc: netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [PATCHv5] net: Add batman-adv meshing protocol
Date: Fri, 24 Sep 2010 13:43:34 -0700 (PDT) [thread overview]
Message-ID: <20100924.134334.28812338.davem@davemloft.net> (raw)
In-Reply-To: <1284836610-26799-1-git-send-email-sven.eckelmann@gmx.de>
From: Sven Eckelmann <sven.eckelmann@gmx.de>
Date: Sat, 18 Sep 2010 21:03:30 +0200
> B.A.T.M.A.N. (better approach to mobile ad-hoc networking) is a routing
> protocol for multi-hop ad-hoc mesh networks. The networks may be wired or
> wireless. See http://www.open-mesh.org/ for more information and user space
> tools.
>
> Signed-off-by: Sven Eckelmann <sven.eckelmann@gmx.de>
The only thing remaining which I really don't like is this hash helper
library thing in here.
It's a terrible abstraction and very inefficient. Iteration uses
function calls, as does removal. Key comparisons use callbacks, via
indirection function pointers, also very inefficient.
Just use the "struct hlist_head" and "struct hlist_node" objects we
have generically already. Inline the list iteration, as well as the
key comparisons and the node linking/unlinking.
Otherwise if you think your hash helpers are so incredibly useful,
propose for their inclusion under lib/ on linux-kernel
But frankly, I wish you a lot of luck with that. :-)
next prev parent reply other threads:[~2010-09-24 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 19:03 [PATCHv5] net: Add batman-adv meshing protocol Sven Eckelmann
2010-09-24 20:43 ` David Miller [this message]
[not found] ` <20100924.134334.28812338.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2010-10-09 12:34 ` Sven Eckelmann
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=20100924.134334.28812338.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=netdev@vger.kernel.org \
--cc=sven.eckelmann@gmx.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;
as well as URLs for NNTP newsgroup(s).