From: "Arinzon, David" <darinzon@amazon.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
"Machulsky, Zorik" <zorik@amazon.com>,
"Matushevsky, Alexander" <matua@amazon.com>,
"Bshara, Saeed" <saeedb@amazon.com>,
"Wilson, Matt" <msw@amazon.com>,
"Liguori, Anthony" <aliguori@amazon.com>,
"Bshara, Nafea" <nafea@amazon.com>,
"Schmeilin, Evgeny" <evgenys@amazon.com>,
"Belgazal, Netanel" <netanel@amazon.com>,
"Saidi, Ali" <alisaidi@amazon.com>,
"Herrenschmidt, Benjamin" <benh@amazon.com>,
"Kiyanovski, Arthur" <akiyano@amazon.com>,
"Dagan, Noam" <ndagan@amazon.com>,
"Bernstein, Amit" <amitbern@amazon.com>,
"Agroskin, Shay" <shayagr@amazon.com>,
"Abboud, Osama" <osamaabb@amazon.com>,
"Ostrovsky, Evgeny" <evostrov@amazon.com>,
"Tabachnik, Ofir" <ofirt@amazon.com>,
"Machnikowski, Maciek" <maciek@machnikowski.net>,
Rahul Rameshbabu <rrameshbabu@nvidia.com>,
Gal Pressman <gal@nvidia.com>
Subject: RE: [PATCH v4 net-next 3/3] net: ena: Add PHC documentation
Date: Thu, 21 Nov 2024 18:59:19 +0000 [thread overview]
Message-ID: <322f671cadb946a3bd528aa5755bc378@amazon.com> (raw)
In-Reply-To: <Zz6973UqdRO1uV8L@hoboy.vegasvil.org>
> On Tue, Nov 19, 2024 at 08:45:52AM +0000, Arinzon, David wrote:
> > Our device limits the number of requests per client (VM) through
> throttling.
>
> So it sounds like this device provides time to VM guests?
>
> If so, you might consider generating an interrupt to provide a "virtual" PPS as
> some of the other VM solutions do. That way, you avoid all of those
> unwanted gettime() calls.
>
> HTH,
> Richard
Hi Richard,
AWS instances currently lack support for the 1PPS signal.
Currently, time information can only be accessed via the GetTime call.
Some instance families already provide this functionality,
with the solution designed to work consistently across both bare-metal and virtualized environments.
Thanks,
David
prev parent reply other threads:[~2024-11-21 18:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 9:59 [PATCH v4 net-next 0/3] PHC support in ENA driver David Arinzon
2024-11-14 9:59 ` [PATCH v4 net-next 1/3] net: ena: Add PHC support in the " David Arinzon
2024-11-14 9:59 ` [PATCH v4 net-next 2/3] net: ena: PHC silent reset David Arinzon
2024-11-14 9:59 ` [PATCH v4 net-next 3/3] net: ena: Add PHC documentation David Arinzon
2024-11-17 1:53 ` Richard Cochran
2024-11-17 2:00 ` Richard Cochran
2024-11-19 8:45 ` Arinzon, David
2024-11-21 4:58 ` Richard Cochran
2024-11-21 18:59 ` Arinzon, David [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=322f671cadb946a3bd528aa5755bc378@amazon.com \
--to=darinzon@amazon.com \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=amitbern@amazon.com \
--cc=benh@amazon.com \
--cc=davem@davemloft.net \
--cc=dwmw@amazon.co.uk \
--cc=edumazet@google.com \
--cc=evgenys@amazon.com \
--cc=evostrov@amazon.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=maciek@machnikowski.net \
--cc=matua@amazon.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=ndagan@amazon.com \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=ofirt@amazon.com \
--cc=osamaabb@amazon.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rrameshbabu@nvidia.com \
--cc=saeedb@amazon.com \
--cc=shayagr@amazon.com \
--cc=zorik@amazon.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;
as well as URLs for NNTP newsgroup(s).