public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
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.] [PATCH] batman-adv: layer2 unicast packet fragmentation enhancements
Date: Sun, 12 Sep 2010 01:56:19 +0200	[thread overview]
Message-ID: <201009120156.20364.lindner_marek@yahoo.de> (raw)
In-Reply-To: <201009111126.38504.sven.eckelmann@gmx.de>

On Saturday 11 September 2010 11:26:37 Sven Eckelmann wrote:
> Is it possible to split the patch in those parts? It would make it easier
> to read it and understand the patches later.

I'm not sure that will do much good. He managed to reorganize the code and 
thereby remove redundancies. The second patch would probably be no bigger than 
3-5 lines of code.


> > -	/* packet for me */
> > -	if (is_my_mac(unicast_packet->dest)) {
> > -		interface_rx(recv_if->soft_iface, skb, hdr_size);
> > -		return NET_RX_SUCCESS;
> > -	}
> > -
> 
> There are different parts of the patch which makes ma a little bit curious
> - for example: why it is possible to drop that check entirely? Could that
> be an extra patch with an explanation why that can be dropped? Is it only
> valid in context of the new fragmentation handling? ...

I ran into the same question as it looks a bit odd here but if you apply the 
patch it all looks good. As I said: it seems he managed to purge quite a bit 
of redundancy (fragmented and non-fragmented packets are almost identical 
after all).

Cheers,
Marek

  reply	other threads:[~2010-09-11 23:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 16:47 [B.A.T.M.A.N.] batman-adv: unicast fragmentation enhancements Andreas Langer
2010-09-10 16:48 ` [B.A.T.M.A.N.] [PATCH] batman-adv: layer2 unicast packet " Andreas Langer
2010-09-11  9:26   ` Sven Eckelmann
2010-09-11 23:56     ` Marek Lindner [this message]
2010-09-12 20:11       ` Sven Eckelmann
2010-09-13 15:45         ` Andreas Langer
2010-09-12  1:14     ` Andreas Langer

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=201009120156.20364.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