From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@open-mesh.net
Subject: Re: [B.A.T.M.A.N.] path selection
Date: Tue, 9 Jan 2007 12:45:42 +0100 (MET) [thread overview]
Message-ID: <200701091223.07813.lindner_marek@yahoo.de> (raw)
In-Reply-To: <200701082002.31400.axel@notmail.org>
Hi,
> However, in this case, that is not the best choice since every second
> packet send via A-c-D needs to be retransmitted on the link A-c, which
> would not be necessary if send via A-b-D .
> Don't know if you agree, ...is that reasonable? Also I don't have any
> simple approach in mind to solve this but it might be worth to reconsider.
I think you made a good point but I even would go a step further. Consider
this: A downloads a file from D thus using D-b-A (with 50% packet loss). But
each packet has to be acknowledged and every second acknowledgement is also
lost (via A-c-D) . That is why D will resend every second packet and the
throughput will suffer even more.
I think we should find a solution here but up to now I don't have a clue how
to do it.
Regards,
Marek
prev parent reply other threads:[~2007-01-09 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 19:02 [B.A.T.M.A.N.] path selection axel
2007-01-09 11:45 ` Marek Lindner [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=200701091223.07813.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/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