All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jambunathan K <jambunathan@netxen.com>
To: xen-devel <xen-devel@lists.xensource.com>
Cc: Sanjeev Jorapur <sanjeev@netxen.com>, xen-users@lists.xensource.com
Subject: Intel VMDq & Xen Platform
Date: Wed, 26 Sep 2007 16:33:59 +0530	[thread overview]
Message-ID: <46FA3C9F.1030208@netxen.com> (raw)

Intel has a whitepaper on support for "Virtual Machine Device Queues" on their
82575 Gb adapters. There is a reference to improved figures in VMWare environment.

http://softwarecommunity.intel.com/isn/downloads/virtualization/pdfs/07-643_VMDq_WP_r01.pdf

>From the looks of it, the technology seems to be applicable to Xen's Split Drivers.

Can someone comment on the VMDq technology on Xen platform in terms of Xen's
readiness.

(I am posting this to Xen-Uses as well as the post might be of generic interest.)

Jambunathan K.

             reply	other threads:[~2007-09-26 11:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 11:03 Jambunathan K [this message]
2007-10-04  8:20 ` [Xen-users] Intel VMDq & Xen Platform Jambunathan K

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=46FA3C9F.1030208@netxen.com \
    --to=jambunathan@netxen.com \
    --cc=sanjeev@netxen.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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.