From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: layer2 unicast packet fragmentation
Date: Tue, 6 Jul 2010 21:13:11 +0200 [thread overview]
Message-ID: <201007062113.12980.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <20100706185729.GB18453@lunn.ch>
[-- Attachment #1: Type: Text/Plain, Size: 837 bytes --]
Andrew Lunn wrote:
> On Tue, Jul 06, 2010 at 07:39:56PM +0200, Antonio Quartulli wrote:
> > Hi all, Hi Andreas,
> >
> > > +#define FRAG_TIMEOUT 60000 /* purge frag list entrys after time in
> > > ms */
> >
> > Why did you choose a so large timeout? Is there a particular reason for
> > that?
> >
> > I think that in 60 seconds an host could receive a very large amount of
> > "orphan" packets in case of a bad link causing memory problems.
>
> It will not cause memory problems. The linked list is limited to
> FRAG_BUFFER_SIZE (6) segments.
He didn't say that it will take all available system memory. There is still
the problem that the 6 slots per originator (so the memory per originator)
could be full when we have a bad link and a too big waiting time for missing
fragments.
Best regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-07-06 19:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 15:58 [B.A.T.M.A.N.] batman adv unicast fragmentation (version 4) Andreas Langer
2010-07-06 15:59 ` [B.A.T.M.A.N.] [PATCH 1/2] batctl: layer2 unicast packet fragmentation Andreas Langer
2010-07-06 15:59 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: " Andreas Langer
2010-07-06 17:07 ` Andrew Lunn
2010-07-06 18:06 ` Andreas Langer
2010-07-06 17:39 ` Antonio Quartulli
2010-07-06 18:17 ` Andreas Langer
2010-07-06 18:57 ` Andrew Lunn
2010-07-06 19:13 ` Sven Eckelmann [this message]
2010-07-06 19:50 ` Marek Lindner
2010-07-07 10:40 ` Marek Lindner
-- strict thread matches above, loose matches on Subject: below --
2010-07-07 17:30 [B.A.T.M.A.N.] batman adv unicast fragmentation (version 5) Andreas Langer
2010-07-07 17:32 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: layer2 unicast packet fragmentation Andreas Langer
2010-07-09 14:51 ` Sven Eckelmann
2010-07-05 21:42 [B.A.T.M.A.N.] batman adv unicast fragmentation (version 3) Andreas Langer
2010-07-05 21:44 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: layer2 unicast packet fragmentation Andreas Langer
2010-06-30 18:58 [B.A.T.M.A.N.] batman adv unicast fragmentation Andreas Langer
2010-06-30 19:00 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: layer2 unicast packet fragmentation Andreas Langer
2010-07-05 0:37 ` Sven Eckelmann
2010-07-05 12:53 ` 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=201007062113.12980.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.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).