From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Matteo Croce <mcroce@redhat.com>
Cc: "Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"Lorenzo Bianconi" <lorenzo.bianconi@redhat.com>,
"Saeed Mahameed" <saeedm@mellanox.com>,
"Tariq Toukan" <tariqt@mellanox.com>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Jonathan Lemon" <jonathan.lemon@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
brouer@redhat.com
Subject: Re: Created benchmarks modules for page_pool
Date: Tue, 28 Jan 2020 19:41:36 +0100 [thread overview]
Message-ID: <20200128194136.4dff1cb2@carbon> (raw)
In-Reply-To: <CAGnkfhy4O+VO9u+pGE83qmtce8+OR4Q2s1e9Wdupr-Bo5FU1fg@mail.gmail.com>
On Tue, 28 Jan 2020 17:22:47 +0100
Matteo Croce <mcroce@redhat.com> wrote:
> On Wed, Jan 22, 2020 at 1:09 PM Jesper Dangaard Brouer
> <brouer@redhat.com> wrote:
> > On Wed, 22 Jan 2020 12:42:05 +0200
> > > Interesting, i'll try having a look at the code and maybe run then on
> > > my armv8 board.
> >
> > That will be great, but we/you have to fixup the Intel specific ASM
> > instructions in time_bench.c (which we already discussed on IRC).
> >
>
> What does it need to work on arm64? Replace RDPMC with something generic?
Replacing the RDTSC. Hoping Ilias will fix it for ARM ;-)
You can also fix yourself via using get_cycles() include <linux/timex.h>.
If the ARCH doesn't have support it will just return 0.
Have you tried it out on your normal x86/Intel box?
Hint:
https://prototype-kernel.readthedocs.io/en/latest/prototype-kernel/build-process.html
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2020-01-28 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 16:09 Created benchmarks modules for page_pool Jesper Dangaard Brouer
2020-01-22 10:42 ` Ilias Apalodimas
2020-01-22 12:09 ` Jesper Dangaard Brouer
2020-01-28 16:22 ` Matteo Croce
2020-01-28 18:41 ` Jesper Dangaard Brouer [this message]
2020-01-29 9:07 ` Ilias Apalodimas
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=20200128194136.4dff1cb2@carbon \
--to=brouer@redhat.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jonathan.lemon@gmail.com \
--cc=lorenzo.bianconi@redhat.com \
--cc=mcroce@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=tariqt@mellanox.com \
--cc=toke@redhat.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).