From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>,
Cake List <cake@lists.bufferbloat.net>,
flent-users <flent-users@flent.org>
Subject: [Flent-users] Re: centos 8 and cake and flent
Date: Thu, 06 May 2021 23:50:48 +0200 [thread overview]
Message-ID: <87tunfv8ef.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw4pgohtn7HkqjYgrBHayKxoBUpmGU=52YWfaG4FTdyMWQ@mail.gmail.com>
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
next prev parent reply other threads:[~2021-05-06 21:50 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 ` Toke Høiland-Jørgensen [this message]
2021-05-08 4:05 ` [Flent-users] Re: [Cake] " David P. Reed
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=87tunfv8ef.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=flent-users@flent.org \
/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