netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Hartmann <richih.mailinglist@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	linux-ppp@vger.kernel.org
Subject: Re: [Patch] fix packet loss and massive ping spikes with PPP multi-link
Date: Fri, 26 Mar 2010 17:39:27 +0100	[thread overview]
Message-ID: <v2v2d460de71003260939w4877df7em9e3084a315b0962f@mail.gmail.com> (raw)
In-Reply-To: <20100326160226.0159ac3b@lxorguk.ukuu.org.uk>

On Fri, Mar 26, 2010 at 17:02, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> You should be able to manage that I'm sure:

Hopefully. We will see :)


> MODULE_PARM_DESC(ml_expode, "Set this to zero to disabling multilink \
>        fragmentation when talking to cisco devices");

To be exact, this is not a Linux vs. Cisco issue, but a Linux vs. world
issue.

At least the last-level support of Telefonica and QSC was definite and
adamant about not enabling fragmentation on _any_ PPP multi-link, ever.

Also, I am not sure if it would not be better to default to no
fragmentation and enable it optionally. I am aware that changing default
behaviour is always a bit of a problem but to the best of my knowledge
enabling fragmentation is a bug in any and all real-world applications.


Richard

  parent reply	other threads:[~2010-03-26 16:39 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 [this message]
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
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=v2v2d460de71003260939w4877df7em9e3084a315b0962f@mail.gmail.com \
    --to=richih.mailinglist@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ppp@vger.kernel.org \
    --cc=netdev@vger.kernel.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).