From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PV-ops][PATCH 0/2] VNIF: Using smart polling instead of event notification.
Date: Wed, 30 Sep 2009 16:41:59 -0700 [thread overview]
Message-ID: <4AC3ECC7.1090007@goop.org> (raw)
In-Reply-To: <EADF0A36011179459010BDF5142A457501CEB99EA5@pdsmsx502.ccr.corp.intel.com>
On 09/30/09 11:17, Xu, Dongxiao wrote:
> Resend the patch and CC Jeremy.
>
> One of the VNIF driver's scalability issues is the high event
> channel frequency. It's highly related to physical NIC's interrupt
> frequency in dom0, which could be 20K HZ in some situation. The
> high frequency event channel notification makes the guest and dom0
> CPU utilization at a high value, especially in multi-VM cases.
> The following two patches uses smart polling mechanism to
> replace event notification to reduce the CPU Utilization.
>
> Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
>
I'm having difficulty applying these because they're in quoted-printable
MIME format. Could you resend them as attachments?
Thanks,
J
next prev parent reply other threads:[~2009-09-30 23:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 18:17 [PV-ops][PATCH 0/2] VNIF: Using smart polling instead of event notification Xu, Dongxiao
2009-09-30 23:41 ` Jeremy Fitzhardinge [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-01 0:11 Xu, Dongxiao
2009-10-01 0:21 ` Jeremy Fitzhardinge
2009-09-30 7:21 Xu, Dongxiao
2009-09-30 7:54 ` Keir Fraser
2009-09-30 17:33 ` Xu, Dongxiao
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=4AC3ECC7.1090007@goop.org \
--to=jeremy@goop.org \
--cc=dongxiao.xu@intel.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.