netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gregory Haskins <ghaskins@novell.com>
To: "alacrityvm-devel@lists.sourceforge.net"
	<alacrityvm-devel@lists.sourceforge.net>,
	alacrityvm-users@lists.sourceforge.net
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: [ANNOUNCE] AlacrityVM v0.2 is released
Date: Thu, 05 Nov 2009 21:44:12 -0500	[thread overview]
Message-ID: <4AF38D7C.40604@novell.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

We (the AlacrityVM team) are pleased to announce the availability of the
v0.2 release.  There are numerous tweaks, fixes, and features that we
have added since the v0.1 days.  Here are a few of the key highlights.

*) VENET support:
   *) zero-copy transmits (guest memory is paged directly to the
physical adapter on the host, where applicable)
   *) "SAR offloading" (essentially bi-directional GSO with "64k MTU")
   *) pre-mapped descriptors to reduce latency
   *) pre-loading of mmu context to reduce latency

*) shm-signal's are now routable (e.g. future MQ support)

*) vbus is optionally managed in its entirely from the rebundled qemu
   *) "-net venet-tap" will fully initialize the interface
internally..no more scripting!

*) vbus components are automatically reaped when the guest exits, even
if the exit is not clean.

We will update the performance numbers ASAP and announce any changes.
For further details, please visit our wiki:

http://developer.novell.com/wiki/index.php/AlacrityVM

Kind Regards,
-Greg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]

                 reply	other threads:[~2009-11-06  2:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4AF38D7C.40604@novell.com \
    --to=ghaskins@novell.com \
    --cc=alacrityvm-devel@lists.sourceforge.net \
    --cc=alacrityvm-users@lists.sourceforge.net \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).