From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: Isaac Boukris <iboukris@gmail.com>, users@dpdk.org
Subject: Re: Accuracy of rte_get_tsc_hz() compared to linux
Date: Fri, 20 Sep 2024 07:36:57 -0700 [thread overview]
Message-ID: <20240920073657.342332a7@hermes.local> (raw)
In-Reply-To: <CAJFAV8yp=nLPNpmOXmJw70=DZdrMY9gbeePgbmx2yGbHpia7kg@mail.gmail.com>
On Fri, 20 Sep 2024 09:26:05 +0200
David Marchand <david.marchand@redhat.com> wrote:
> On Fri, Sep 20, 2024 at 12:22 AM Stephen Hemminger
> <stephen@networkplumber.org> wrote:
> > Sigh. exposing tsc frequency through sysfs is a Redhat extension
> > that never got merged upstream.
>
> Counter sight :-).
>
> Not sure where this assertion comes from.
> I see no trace of this downstream: RH policy is "upstream first".
>
I missed the driver stuff in original mail and assumed that
since it wasn't in upstream (or Debian) that it came from Redhat. Sorry.
It would be good if kernel exposed it, and there was a proposal
to do that, but it seemed to die from "no one should ever need or care about that"
https://lwn.net/Articles/388263/
next prev parent reply other threads:[~2024-09-20 14:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 22:04 Isaac Boukris
2024-09-18 23:27 ` Stephen Hemminger
2024-09-19 9:37 ` Isaac Boukris
2024-09-19 12:26 ` Isaac Boukris
2024-09-19 13:04 ` Isaac Boukris
2024-09-19 18:33 ` Isaac Boukris
2024-09-19 21:53 ` Stephen Hemminger
2024-09-19 22:02 ` Stephen Hemminger
2024-09-19 22:21 ` Stephen Hemminger
2024-09-20 3:19 ` Isaac Boukris
2024-09-20 14:39 ` Stephen Hemminger
2024-09-20 15:06 ` Isaac Boukris
2024-09-20 7:26 ` David Marchand
2024-09-20 14:36 ` Stephen Hemminger [this message]
2024-09-20 15:11 ` Isaac Boukris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240920073657.342332a7@hermes.local \
--to=stephen@networkplumber.org \
--cc=david.marchand@redhat.com \
--cc=iboukris@gmail.com \
--cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).