Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Ryan Mounce <ryan@mounce.com.au>
Cc: Michael Welzl <michawe@ifi.uio.no>,
	ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] osx ecn
Date: Wed, 28 Aug 2019 17:55:37 -0700	[thread overview]
Message-ID: <CAA93jw5aJDMJxx+xdTy16XCCbafrEy-+DPTT7Ua9_ZY9Lm+xFA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7aegs3dat+QKoQ2=-MfzBRg2HtpKORBGpncdKb+hLXLw@mail.gmail.com>

fq_codel on osx ethernet (I'd only seen it on wifi before)

https://discussions.apple.com/thread/250589601

On Wed, Aug 28, 2019 at 4:45 PM Dave Taht <dave.taht@gmail.com> wrote:
>
> Very cool, thank you for jailbreaking.
>
> I'm a little puzzled over the cwr/ece ratio?
>
> 25 times received congestion experienced (CE) notification
> 37 times CWR was sent in response to ECE
> 619 times sent ECE notification
> 1029 connections received CE atleast once
>
> And um, er, while you are here busting your warranty for the sake of
> science, I'm dying to know what
>
>  netstat -I each_interface_you_have_especially_lte -qq
>
> shows. They have a really short queue and some form of flow control
> and I've never seen anything trigger except though a vm
>
> my laptop:
>
> en0:
>
>      [ sched:  FQ_CODEL  qlength:    0/128 ]
>
>      [ pkts:          0  bytes:          0  dropped pkts:   1087 bytes: 177812 ]
>
> =====================================================
>
>      [ pri: VO (1)      srv_cl: 0x400180        quantum: 600    drr_max: 8 ]
>
>      [ queued pkts: 0   bytes: 0 ]
>
>      [ dequeued pkts: 36767     bytes: 5237639 ]
>
>      [ budget: 0        target qdelay: 10.00 msec       update
> interval:100.00 msec ]
>
>      [ flow control: 0  feedback: 0     stalls: 0       failed: 0 ]
>
>      [ drop overflow: 0 early: 0        memfail: 0      duprexmt:0 ]
>
>      [ flows total: 0   new: 0  old: 0 ]
>
>      [ throttle on: 0   off: 0  drop: 0 ]
>
> =====================================================
>
>      [ pri: VI (2)      srv_cl: 0x380100        quantum: 3000   drr_max: 6 ]
>
>      [ queued pkts: 0   bytes: 0 ]
>
>      [ dequeued pkts: 96836     bytes: 36619772 ]
>
>      [ budget: 0        target qdelay: 10.00 msec       update
> interval:100.00 msec ]
>
>      [ flow control: 0  feedback: 0     stalls: 0       failed: 0 ]
>
>      [ drop overflow: 0 early: 0        memfail: 0      duprexmt:0 ]
>
>      [ flows total: 0   new: 0  old: 0 ]
>
>      [ throttle on: 0   off: 0  drop: 0 ]
>
> =====================================================
>
>      [ pri: BE (7)      srv_cl: 0x0     quantum: 1500   drr_max: 4 ]
>
>      [ queued pkts: 0   bytes: 0 ]
>
>      [ dequeued pkts: 5212250   bytes: 2820548356 ]
>
>      [ budget: 0        target qdelay: 10.00 msec       update
> interval:100.00 msec ]
>
>      [ flow control: 30 feedback: 30    stalls: 0       failed: 0 ]
>
>      [ drop overflow: 0 early: 0        memfail: 0      duprexmt:0 ]
>
>      [ flows total: 0   new: 0  old: 0 ]
>
>      [ throttle on: 0   off: 0  drop: 0 ]
>
> On Wed, Aug 28, 2019 at 4:29 PM Ryan Mounce <ryan@mounce.com.au> wrote:
> >
> > On Wed, 28 Aug 2019 at 04:30, Michael Welzl <michawe@ifi.uio.no> wrote:
> >>
> >>
> >>
> >> On Aug 27, 2019, at 8:36 PM, Dave Taht <dave.taht@gmail.com> wrote:
> >>
> >> On Mon, Aug 26, 2019 at 11:54 PM Michael Welzl <michawe@ifi.uio.no> wrote:
> >>
> >>
> >> run it as root - strange, yes, but then the output is very different.
> >>
> >> cheers,
> >> michael
> >>
> >>
> >> Sent from my iPhone
> >>
> >>
> >> speaking of iphones I have no idea what they do nowadays, any odds you
> >> could do a packet
> >> cap either on it or at a server or via wifi on a middlebox
> >>
> >>
> >> I wouldn’t know … but I can guess: some years ago, I did a “jailbreak” on my iPhone, and as a result, I could ssh into it.
> >> So I’m guessing: if you do this with a current one, you can probably still ssh into it and then perhaps run netstat.
> >>
> >> Cheers,
> >> Michael
> >
> >
> > You sure can :)
> >
> > https://gist.github.com/rmounce/74dd5e92e6304688219024349bfaad0e
> >
> > -Ryan
> >
> >>
> > --
> > Regards,
> > Ryan Mounce
> >
> > ryan@mounce.com.au
> > 0415 799 929
> >
> > Sent from mobile
>
>
>
> --
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-205-9740



-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

  reply	other threads:[~2019-08-29  0:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27  2:03 Dave Taht
2019-08-27  6:47 ` Mikael Abrahamsson
2019-08-27  6:54   ` Michael Welzl
2019-08-27  7:02     ` Mikael Abrahamsson
2019-08-27 18:20       ` Dave Taht
2019-08-27 18:36     ` Dave Taht
2019-08-27 19:00       ` Michael Welzl
2019-08-28 23:29         ` Ryan Mounce
2019-08-28 23:45           ` Dave Taht
2019-08-29  0:55             ` Dave Taht [this message]
2019-08-29  3:28               ` Mikael Abrahamsson
2019-08-29  4:43                 ` Dave Taht
2019-08-29 10:30                   ` Mikael Abrahamsson
2019-08-29  8:08             ` Jonathan Morton
2019-08-29 10:39             ` Ryan Mounce
2019-08-27  6:58 ` Sebastian Moeller
2019-08-27  7:05   ` Jonathan Morton
2019-08-27  7:52     ` 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/ecn-sane.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=CAA93jw5aJDMJxx+xdTy16XCCbafrEy-+DPTT7Ua9_ZY9Lm+xFA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=michawe@ifi.uio.no \
    --cc=ryan@mounce.com.au \
    /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