From: Dave Taht <dave.taht@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: Cake List <cake@lists.bufferbloat.net>,
Loganaden Velvindron <loganaden@gmail.com>
Subject: Re: [Cake] CAKE related iproute2 & kernel patches - keeping things in sync
Date: Sun, 29 Jul 2018 16:42:15 -0700 [thread overview]
Message-ID: <CAA93jw6gC2O2zJzBK2Azk6wA2HkUsfYMk2uJ-_MuWqFyu=3UFw@mail.gmail.com> (raw)
In-Reply-To: <942CB8C5-81AD-4359-8DEB-77603EB91D1F@darbyshire-bryant.me.uk>
On Sun, Jul 29, 2018 at 3:05 AM Kevin Darbyshire-Bryant
<kevin@darbyshire-bryant.me.uk> wrote:
>
> To whom it may concern (Dave) ;-)
>
> This is a general plea that when patches are submitted to upstream please can we also commit them to our current development repositories.
Mea culpa. I was hiding under my desk expecting the 10GigE+ world to
unite and march upon me, torches ablaze and, while gearing up for
battle there, collecting data on how bql and split-gso interacted at
various speeds, I didn't expect davem to just take the darn patch.
I have this whole lovely, giant, rant ,and plots that I'm not gonna be
motivated to finish now.
This does raise a long term point however in that as we go mainline
more tweaks and patches *will* arrive
via normal linux kernel processes from others. Do you want maintainership there?
> 4.19 isn’t even released yet, so most people, including Openwrt, get cake via our 'out of tree’ repositories. This is also a good idea from a point of view of testing. I appreciate the latest changes are of ‘one line’ type variety and so mostly harmless but ideally it should at least be in our own out of tree repo’s first/at the same time.
>
> I had to submit the latest ‘split-gso by default’ patch, accepted to upstream, manually to our own cake repo for Toke to commit. I note with some distress that there’s an ‘iproute2’ upstream patch pending to enable the userspace side of the same thing that currently is NOT in the ‘tc-adv’ repo.
>
> Dare I also suggest that a man page update would be appreciated by iproute2-next too.
I started reviewing the man page's gobble of troff, started writing a
tuning section (and decided that needed a web page), went looking for
other missing keywords, and... we haven't heard from logan in a
while... my back is covered with black jube jells and dust bunnies
from hiding under my desk.
and I dunno, has anyone read the man page lately? There's a HUGE
opportunity to bikeshed there.
> The above would make the ‘Cake for Openwrt’ maintainer very happy ;-)
>
>
> Cheers,
>
> Kevin D-B
>
> 012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-07-29 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 10:05 Kevin Darbyshire-Bryant
2018-07-29 23:42 ` Dave Taht [this message]
2018-07-30 15:07 ` Kevin Darbyshire-Bryant
2018-07-30 15:41 ` Loganaden Velvindron
2018-07-30 17:23 ` [Cake] man page bikeshed Dave Taht
2018-07-30 17:39 ` Dave Taht
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6gC2O2zJzBK2Azk6wA2HkUsfYMk2uJ-_MuWqFyu=3UFw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
--cc=loganaden@gmail.com \
/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