General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Neil Davies <neil.davies@pnsol.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] ADSL2+ interleaving (Re: CFP: Workshop on Reducing Internet Latency)
Date: Tue, 10 Dec 2013 08:07:37 +0000	[thread overview]
Message-ID: <53680E91-D6BA-4F1A-893C-A08A40E5224E@pnsol.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1312100858320.24602@uplift.swm.pp.se>

Don't have direct access to the DSLAM, but do have access to that information in the modem - and yes and there appears to be a large change in certain frequency buckets.

The loss rates appear to vary with the offered load - i.e the "loss" only occurs if there was real packet data in that frequency band


On 10 Dec 2013, at 08:04, Mikael Abrahamsson <swmike@swm.pp.se> wrote:

> On Tue, 10 Dec 2013, Neil Davies wrote:
> 
>> We've seen this even when we've played with the settings through the customer portal (I'm' in the UK - the provisioning portal allows many such changes).
>> 
>> Are you capturing any evidence of DSL modem state when this occurs?
> 
> Well, we saw the problems mostly on medium-short spans, such as 1000-1500 meters. The packet loss wasn't as high as 20%, but it was consistant over time and showed up as errored seconds. I do not work there anymore, and this was 7 years ago.
> 
> Interleaving spans bits over longer period of time, so if you're running fast mode and you get a 1ms "hit" on the link, the FEC (forward error correction) gets too many bits corrupted and gets overwhelmed. If one instead has 16ms interleaving, a lot fewer bits from one packet gets corrupted, and FEC can correct the errors.
> 
> So your theory about line noise on specific frequencies is probably correct, you're not getting a big enough hit to trigger a re-train, but you're getting enough bit errors to cause post-FEC errors and thus packet loss. A re-train probably identifies the noise on those frequencies and uses them less.
> 
> In our DSLAM we could see the frequency band profile via a show command, have you done this?
> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se


  reply	other threads:[~2013-12-10  8:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  9:54 [Bloat] CFP: Workshop on Reducing Internet Latency Mat Ford
2013-05-30  2:56 ` Dave Taht
2013-06-04 17:54   ` Jim Gettys
2013-06-11 10:51 ` Matthew Ford
2013-12-09 12:49 ` Matthew Ford
2013-12-10  6:48   ` Mikael Abrahamsson
2013-12-10  7:54     ` Neil Davies
2013-12-10  8:04       ` [Bloat] ADSL2+ interleaving (Re: CFP: Workshop on Reducing Internet Latency) Mikael Abrahamsson
2013-12-10  8:07         ` Neil Davies [this message]
2013-12-10  8:48     ` [Bloat] CFP: Workshop on Reducing Internet Latency MUSCARIELLO Luca IMT/OLN
2013-12-10  9:36       ` Mikael Abrahamsson
2013-12-10  9:40         ` MUSCARIELLO Luca IMT/OLN

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53680E91-D6BA-4F1A-893C-A08A40E5224E@pnsol.com \
    --to=neil.davies@pnsol.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=swmike@swm.pp.se \
    /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