From: Paul Mackerras <paulus@samba.org>
To: Ben McKeegan <ben@netservers.co.uk>
Cc: netdev@vger.kernel.org, linux-ppp@vger.kernel.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"Alexander E. Patrakov" <patrakov@gmail.com>,
Richard Hartmann <richih.mailinglist@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Patch] fix packet loss and massive ping spikes with PPP multi-link
Date: Sat, 29 May 2010 12:16:24 +1000 [thread overview]
Message-ID: <20100529021624.GA2538@brick.ozlabs.ibm.com> (raw)
In-Reply-To: <4BB31E00.8060204@netservers.co.uk>
On Wed, Mar 31, 2010 at 11:03:44AM +0100, Ben McKeegan wrote:
> I needed to do something similar a while back and I took a very
> different approach, which I think is more flexible. Rather than
> implement a new round-robin scheduler I simply introduced a target
> minimum fragment size into the fragment size calculation, as a per
> bundle parameter that can be configured via a new ioctl. This
> modifies the algorithm so that it tries to limit the number of
> fragments such that each fragment is at least the minimum size. If
> the minimum size is greater than the packet size it will not be
> fragmented all but will instead just get sent down the next
> available channel.
>
> A pppd plugin generates the ioctl call allowing this to be tweaked
> per connection. It is more flexible in that you can still have the
> larger packets fragmented if you wish.
I like this a lot better than the other proposed patch. It adds less
code because it uses the fact that ppp_mp_explode() already has a
round-robin capability using the ppp->nxchan field, plus it provides a
way to control it per bundle via pppd.
If you fix up the indentation issues (2-space indent in some of the
added code -- if you're using emacs, set c-basic-offset to 8), I'll
ack it and hopefully DaveM will pick it up.
Paul.
next prev parent reply other threads:[~2010-05-29 2:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 15:50 [Patch] fix packet loss and massive ping spikes with PPP multi-link Richard Hartmann
2010-03-26 16:02 ` Alan Cox
2010-03-26 16:33 ` Joe Perches
2010-03-26 16:39 ` Richard Hartmann
2010-03-26 16:59 ` David Miller
2010-03-26 17:04 ` David Miller
2010-03-26 17:04 ` James Carlson
2010-03-26 17:00 ` Alexander E. Patrakov
2010-03-26 17:04 ` Alan Cox
2010-03-31 10:03 ` Ben McKeegan
2010-05-29 2:16 ` Paul Mackerras [this message]
2010-05-29 9:06 ` Richard Hartmann
2010-05-31 13:39 ` Richard Hartmann
2010-05-31 16:20 ` Ben McKeegan
2010-06-02 14:55 ` Ben McKeegan
2010-06-02 15:04 ` [PATCH] ppp_generic: fix multilink fragment sizes Ben McKeegan
2010-06-02 15:17 ` Paoloni, Gabriele
2010-06-02 15:31 ` David Miller
2010-06-02 15:55 ` Ben McKeegan
2010-06-03 8:41 ` Paoloni, Gabriele
2010-06-03 9:14 ` Ben McKeegan
2010-11-08 14:05 ` [Patch] fix packet loss and massive ping spikes with PPP multi-link Richard Hartmann
2010-11-15 12:07 ` Richard Hartmann
2010-06-01 10:20 ` Richard Hartmann
2010-06-01 11:18 ` Ben McKeegan
2010-06-01 11:28 ` Richard Hartmann
2010-06-01 22:15 ` David Miller
2010-03-31 9:01 ` Richard Hartmann
2010-05-25 9:52 ` Richard Hartmann
[not found] ` <4BFBA3F2.2000301@bfs.de>
[not found] ` <AANLkTilnueP5HIfX03soMCYE93jubL000rpiOCN1xB2-@mail.gmail.com>
[not found] ` <4BFC0942.2030103@bfs.de>
2010-05-26 8:47 ` Richard Hartmann
2010-05-28 7:28 ` walter harms
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=20100529021624.GA2538@brick.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ben@netservers.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patrakov@gmail.com \
--cc=richih.mailinglist@gmail.com \
/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).