From: "David P. Reed" <dpreed@deepplum.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dave Taht <dave.taht@gmail.com>,
Cake List <cake@lists.bufferbloat.net>,
flent-users <flent-users@flent.org>
Subject: [Flent-users] Re: [Cake] centos 8 and cake and flent
Date: Sat, 8 May 2021 00:05:00 -0400 (EDT) [thread overview]
Message-ID: <1620446700.69329642@apps.rackspace.com> (raw)
In-Reply-To: <87tunfv8ef.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 2390 bytes --]
Fedora definitely has cake in its kernel, and eventually these kernel things get into RHEL and Centos.
FYI, my router/gateway to the Internet at home is based on Fedora Server Edition (Fedora 33, as I wait a little to upgrade my router/gateway after a new edition is released, as Fedora 34 was just put out). I've been running cake in it for years now, and it has given me no trouble. I started with it being added by use of DKMS when cake wasn't in the standard kernel yet. I had a glitch when it made it into the standard kernel and DKMS got confused and I had to figure out why the cake config wasn't working.
Now Fedora's not quite just an early availability for RHEL, but for kernel functionality it has been. I understand why for Enterprise use, RHEL is conservative about tracking the leading edge.
On Thursday, May 6, 2021 5:50pm, "Toke Høiland-Jørgensen via Cake" <cake@lists.bufferbloat.net> said:
> Dave Taht <dave.taht@gmail.com> writes:
>
> > Currently centos (and I assume redhat) is at 4.18. Cake went into 4.19
> > so I assume the next major
> > redhat/centos releases will have it.
>
> Note that the RHEL kernel version number is basically a complete
> fabrication; it's the version that the kernel was forked from, something
> like 30% of all commits are backported for each new upstream release,
> without changing the RHEL-kernel version number.
>
> Which means that all the Cake out-of-tree kernel version compatibility
> stuff is not going to work, because that works based on the kernel
> version number...
>
> > Is there a yum/rpm expert in the house? flent does not appear to be
> > packaged up for this (?),
>
> It's in Fedora: https://src.fedoraproject.org/rpms/flent - should be
> fairly straight-forward to add it to EPEL as well, but thus far no one
> has requested it... :)
>
> > neither is netperf or irtt. Is there a repo I could use?
>
> netperf is blocked on licensing:
> https://bugzilla.redhat.com/show_bug.cgi?id=1729939
>
> Since the re-licensing there may be a chance, but not sure what the
> procedure is when there's not a release with the new license.
>
> As for irtt, that should be pretty straight-forward to package.
>
> -Toke
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
[-- Attachment #2: Type: text/html, Size: 3561 bytes --]
prev parent reply other threads:[~2021-05-08 4:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 17:49 [Flent-users] " Dave Taht
2021-05-06 21:50 ` [Flent-users] " Toke Høiland-Jørgensen
2021-05-08 4:05 ` David P. Reed [this message]
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.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1620446700.69329642@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=flent-users@flent.org \
--cc=toke@toke.dk \
--subject='[Flent-users] Re: [Cake] centos 8 and cake and flent' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox