From: Antonio Quartulli <ordex@autistici.org>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCHv3] batman-adv: postpone OGM preparation to sending time
Date: Thu, 3 Jan 2013 10:54:10 +0100 [thread overview]
Message-ID: <20130103095410.GC27589@ritirata.org> (raw)
In-Reply-To: <201301021944.21367.lindner_marek@yahoo.de>
[-- Attachment #1: Type: text/plain, Size: 2673 bytes --]
On Wed, Jan 02, 2013 at 07:44:21PM +0800, Marek Lindner wrote:
> On Wednesday, January 02, 2013 15:48:13 Antonio Quartulli wrote:
> > > > @@ -468,6 +442,7 @@ static void batadv_iv_ogm_aggregate(struct
> > > > batadv_forw_packet *forw_packet_aggr, memcpy(skb_buff, packet_buff,
> > > > packet_len);
> > > >
> > > > forw_packet_aggr->packet_len += packet_len;
> > > > forw_packet_aggr->num_packets++;
> > > >
> > > > + forw_packet_aggr->own |= own_packet;
> > > >
> > > > /* save packet direct link flag status */
> > > > if (direct_link) {
> > >
> > > Using "|= own_packet" isn't strictly necessary because
> > > "forw_packet_aggr->own" isn't a bit field.
> >
> > Well the point is that here own_packet could be false, but
> > forw_packet_aggr->own might already be true, so I didn't want to destroy
> > the original value.
>
> Good point. However, your "solution" is far from obvious. Either you make it
> more obvious or you should add a comment.
>
Oky. Will try to make it more clear and avoid obfuscated code :)
>
> > > Did you vigorously test this code ? Especially, multi-node with multiple
> > > interface setups are of interest. Also use different orig intervals to
> > > ensure it still works everywhere.
> >
> > I will try more topologies and in particular different orig intervals as
> > soon as I have the possibility
>
> Ok.
>
>
> > > The thing is: Throughout the code you can find the implicite assumption
> > > of the first aggregated packet being an "own packet" (if
> > > forw_packet_aggr->own is set). Therefore, you have to be very careful
> > > changing that logic. One function you definitely overlooked is
> > > batadv_iv_ogm_send_to_if() but there might be others.
>
> You did not comment this section. Hopefully it wasn't overlooked ?
no, it wasn't. I simply silently acknowledged your comment :)
>
>
> > > > +/**
> > > > + * batadv_iv_ogm_send - prepare an send an own OGM
> > > > + * @work: kernel work struct
> > > > + *
> > > > + * Prepare the OGM and immediately enqueue it for sending
> > > > + */
> > >
> > > prepare and send an own OGM
> > >
> > > ^^^
> >
> > well, technically it is enqueued, not sent..
>
> Your kernel doc states:
> batadv_iv_ogm_send - prepare an send an own OGM
>
> Therefore I proposed a fix:
> batadv_iv_ogm_send - prepare and send an own OGM
oh, right! I just read the line above your comment, not the rest.
>
> If you wish to reword it altogether that's also ok for me.
>
mh, maybe. Thanks²
Cheers,
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-01-03 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 11:14 [B.A.T.M.A.N.] [PATCHv3] batman-adv: postpone OGM preparation to sending time Antonio Quartulli
2012-12-26 10:08 ` Marek Lindner
2013-01-02 7:48 ` Antonio Quartulli
2013-01-02 11:44 ` Marek Lindner
2013-01-03 9:54 ` Antonio Quartulli [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=20130103095410.GC27589@ritirata.org \
--to=ordex@autistici.org \
--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