From: Tobias Klauser <tklauser@distanz.ch>
To: Sven Eckelmann <sven.eckelmann@gmx.de>
Cc: devel@driverdev.osuosl.org, b.a.t.m.a.n@lists.open-mesh.org,
Greg Kroah-Hartman <gregkh@suse.de>,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>,
Marek Lindner <lindner_marek@yahoo.de>
Subject: Re: [B.A.T.M.A.N.] [PATCH] staging: batman-adv: Use linux/etherdevice.h address helper functions
Date: Wed, 3 Nov 2010 11:25:12 +0100 [thread overview]
Message-ID: <20101103102512.GD10579@distanz.ch> (raw)
In-Reply-To: <201011031112.20044.sven.eckelmann@gmx.de>
On 2010-11-03 at 11:12:12 +0100, Sven Eckelmann <sven.eckelmann@gmx.de> wrote:
> On Wednesday 03 November 2010 10:59:02 you wrote:
> > Replace custom ethernet address check functions by calls to the helpers
> > in linux/etherdevice.h
>
> Have you proven that the addresses are always two bytes aligned in memory?
> Afaik this function needs it.
I don't think they need to be two bytes aligned, but I might be wrong.
> > In one case where the address was tested for broadcast and multicast
> > address, the broadcast address check can be omitted as broadcast is also
> > a multicast address.
>
> We need to distinguish between these two types for different optimizations
> (research is currently done for multicast over mesh - but currently not part
> of batman-adv).
I was refering to the following part of the patch:
- if (is_bcast(ethhdr->h_dest) || is_mcast(ethhdr->h_dest)) {
+ if (is_multicast_ether_addr(ethhdr->h_dest)) {
I think this change should be legitimate as the same branch is done for
multicast and broadcast addresses.
Thanks
Tobias
next prev parent reply other threads:[~2010-11-03 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 9:59 [B.A.T.M.A.N.] [PATCH] staging: batman-adv: Use linux/etherdevice.h address helper functions Tobias Klauser
2010-11-03 10:12 ` Sven Eckelmann
2010-11-03 10:25 ` Tobias Klauser [this message]
2010-11-03 10:56 ` Sven Eckelmann
2010-11-03 11:04 ` Sven Eckelmann
2010-11-03 12:00 ` 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=20101103102512.GD10579@distanz.ch \
--to=tklauser@distanz.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=lindner_marek@yahoo.de \
--cc=siwu@hrz.tu-chemnitz.de \
--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