General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] The bigger picture: whats components are used together to fight bloat
Date: Thu, 16 May 2013 15:17:36 -0400	[thread overview]
Message-ID: <3551.1368731856@sandelman.ca> (raw)
In-Reply-To: <alpine.DEB.2.00.1305030643310.24367@uplift.swm.pp.se>


Thanks for the reply.

>>>>> "Mikael" == Mikael Abrahamsson <swmike@swm.pp.se> writes:
    >> I anticipate similar problems trying to provide VoIP over (initially:
    >> stationary) 3G.  Two providers have promised me that I'll be able to do PPP
    >> directly to the devices, but when they show me a price list, it's clearly
    >> for whole(re)sale.  I think the sales people don't understand that they are
    >> lying, so I have less details on this.

    Mikael> Even if you do ppp to the device, you're still not the bottleneck. Every 3G
    Mikael> pluggable device I'm aware of does its own scheduling and just
    Mikael> emulates/spoofs the ethernet/ppp layer so it's easier to integrate into the
    Mikael> operating system. I wouldn't be surprised if most phones were done the same
    Mikael> way, the OS of the system talks to the baseband part, but the baseband part
    Mikael> does its own queueing.

Most phones talk USB serial to the radio.  Many even use "AT" command
set...  Most "rocket sticks" contain the same radio, but it speaks
USB-ethernet instead of USB-serial, or sometimes it's a completely
proprietary (Windows only) interface.

    >> So the problem is that we can't always know what amount to shape things
    >> with.   As I am working with a vendor of CPE and access devices which
    >> says that they have an SDK, I attempting to put together a project to do
    >> measurements.  I will control the layer-3 devices at each end of the PPP(oE)
    >> link...

    Mikael> If you want to be able to do sane scheduling on 3GPP devices
    Mikael> then you need to 
    Mikael> interact with the APIs provided to do traffic prioritization the 3GPP
    Mikael> way. These are called "Traffic Flow Templates", but they
    Mikael> basically just sorts 
    Mikael> packets according to criteria into different parallell
    Mikael> queues (bearers) with 
    Mikael> different priority in the radio network. So you get a few FIFOs instead of
    Mikael> just one.

yes, I'm aware that there are multiple queues.  I have no idea at this
point if we will get to speak at that layer, I suspect that we will get
access to a single queue.

The 3G situation is a sometime in 3-quarters thing.
The PPPoE situation is next month :-)

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
	

  reply	other threads:[~2013-05-16 19:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02 11:43 Jeroen Balduyck
2013-05-02 13:51 ` Michael Richardson
2013-05-03  4:50   ` Mikael Abrahamsson
2013-05-16 19:17     ` Michael Richardson [this message]
2013-05-17  4:41       ` Mikael Abrahamsson

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=3551.1368731856@sandelman.ca \
    --to=mcr@sandelman.ca \
    --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