General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] ADSL, ATM drivers, bloat, education & confusion
Date: Sun, 7 Jun 2015 14:29:30 +0100	[thread overview]
Message-ID: <5574473A.7030106@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <439DCDC5-13C9-4B8E-89A8-90977F90258A@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]



On 06/06/15 19:14, Sebastian Moeller wrote:
>> Apparenly it's under my control but I'm fighting my own lack of abilities, trying to sprint a marathon before I can even crawl.  Looking at kernel sources when I can barely get 'hello world' to compile & run is asking for trouble :-)  About a day ago I didn't know what an SKB was. https://www.coverfire.com/articles/queueing-in-the-linux-network-stack/ has been a revelation.
> 	This sounds like you embark on fixing the del driver in your modem; more power to you then.
I thank you for your wishes.  The reality is that I don't have a clue :-(  I'm looking at package/kernel/lantiq/ltq-atm/src/ltq_atm.c and seeing stuff that looks like allocating buffers, setting 'mailboxes' (I'm guessing a semaphore type mechanism to tell firmware/hardware that there's a buffer waiting and it would be ever so nice if you could put it on the wire please) but I now doubt that the 'simple 7 lines or so' related to "netdev_tx_sent_queue" and friends are really as simple as that.

I suspect ADSL will be a forgotten technology by the time I understand 'C' and Linux kernels well enough to have a chance :-)


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4791 bytes --]

  reply	other threads:[~2015-06-07 13:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-06 13:38 Kevin Darbyshire-Bryant
2015-06-06 13:53 ` Jonathan Morton
2015-06-06 14:30   ` Sebastian Moeller
2015-06-11 11:24     ` Jesper Dangaard Brouer
2015-06-11 11:57       ` Sebastian Moeller
2015-06-11 14:14         ` Tristan Seligmann
2015-06-11 21:03           ` Sebastian Moeller
2015-06-12  6:45             ` Jesper Dangaard Brouer
2015-06-06 15:04   ` Sebastian Moeller
2015-06-06 14:29 ` Sebastian Moeller
2015-06-06 15:46   ` Kevin Darbyshire-Bryant
2015-06-06 15:50     ` Dave Taht
2015-06-06 18:14     ` Sebastian Moeller
2015-06-07 13:29       ` Kevin Darbyshire-Bryant [this message]
2015-06-11 11:16   ` Jesper Dangaard Brouer
2015-06-11 11:51     ` Sebastian Moeller

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=5574473A.7030106@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    /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