From: Gianluca Guida <gianluca.guida@eu.citrix.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: "herbert.van.den.bergh@oracle.com"
<herbert.van.den.bergh@oracle.com>,
"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>
Subject: Re: vnif socket buffer mistaken for pagetable page causes major performance problem
Date: Mon, 08 Jun 2009 10:11:15 +0100 [thread overview]
Message-ID: <4A2CD5B3.4090700@eu.citrix.com> (raw)
In-Reply-To: <2ee9aac0-0772-4306-a9e5-bf711cf2c2d8@default>
Hi,
Sorry for the late reply,
Dan Magenheimer wrote:
> A recent posting reminded me of this and, though the
> information is a bit vague, someone familiar with the
> shadow code might know just where to look to fix this,
> hopefully in time for 3.4 (if its not already fixed).
>
> One of our performance experts discovered a strange
> major network performance hit seen only under certain
> circumstances, IIRC mostly in HVM but sometimes in
> PV when migrating.
>
> With some help from Intel, it was determined that
> the heuristics used by shadow paging to determine
> whether a guest is modifying a pagetable page were
> getting fooled by the access pattern used by the
> code that copies data into a newly allocated socket
> buffer. As a result, many unnecessary vmenter/vmexits
> were happening.
>
> The workaround was to preallocate all socket buffer
> memory.
>
> That's all I've got, but we can try to answer questions
> if this isn't already a known fixed problem.
Can you be a little more specific about what is the performance loss, in
what workload, and what heuristic you found to be wrong in this case?
Thanks,
Gianluca
next prev parent reply other threads:[~2009-06-08 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 0:37 vnif socket buffer mistaken for pagetable page causes major performance problem Dan Magenheimer
2009-06-08 9:11 ` Gianluca Guida [this message]
2009-06-08 16:22 ` Herbert van den Bergh
2009-06-09 13:25 ` Gianluca Guida
2009-06-09 15:22 ` Herbert van den Bergh
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=4A2CD5B3.4090700@eu.citrix.com \
--to=gianluca.guida@eu.citrix.com \
--cc=dan.magenheimer@oracle.com \
--cc=herbert.van.den.bergh@oracle.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.