public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Radu Rendec <rrendec@arista.com>
To: linux-kernel@vger.kernel.org
Subject: Impact of CONFIG_PARAVIRT=y / mmap benchmark
Date: Tue, 28 Mar 2017 18:17:32 +0100	[thread overview]
Message-ID: <1490721452.1907.25.camel@arista.com> (raw)

Hi,

I'm trying to assess the performance impact of enabling PARAVIRT (and
XEN) in a custom kernel configuration. I came across a very old thread
(https://lkml.org/lkml/2009/5/13/449) on this topic and the conclusion
back then was that the performance impact was (arguably) around 1%.

Does anyone still have a copy of Ingo Molnar's mmap-perf.c program (the
old link is broken)? Would it still be relevant to use it for measuring
performance in case of PARAVIRT?

Last but not least, has anyone looked into PARAVIRT performance more
recently?

Thank you!

Best regards,
Radu Rendec

             reply	other threads:[~2017-03-28 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 17:17 Radu Rendec [this message]
2017-03-29 15:54 ` Impact of CONFIG_PARAVIRT=y / mmap benchmark Randy Dunlap
2017-03-29 18:05   ` Ingo Molnar
2017-03-31 10:03     ` Radu Rendec
2017-03-31 17:02       ` Randy Dunlap

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=1490721452.1907.25.camel@arista.com \
    --to=rrendec@arista.com \
    --cc=linux-kernel@vger.kernel.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