From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com, Andrew Warfield <andy@xensource.com>
Subject: Re: reasons/requirements for some of patches/linux-2.6.16.29/*
Date: Fri, 6 Oct 2006 13:09:48 +0100 [thread overview]
Message-ID: <20061006120948.GA5580@redhat.com> (raw)
In-Reply-To: <45262720.76E4.0078.0@novell.com>
On Fri, Oct 06, 2006 at 08:51:28AM +0100, Jan Beulich wrote:
> >>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 06.10.06 09:25 >>>
> >On 6/10/06 8:25 am, "Jan Beulich" <jbeulich@novell.com> wrote:
> >
> >> Could anyone give a description (and reason it is needed for Xen, if that's
> >> not obvious from the description) for each of
> >>
> >> blktap-aio-16_03_06.patch
> >
> >Not sure. Andrew Warfield or Julian Chesterfield probably will know. I would
> >guess it's probably a backport of AIO changes from a more recent kernel, but
> >I'm not certain about that.
>
> It's certainly not a backport (i.e. still needed in almost unchanged form in 2.6.18).
>
> >> net-gso-*.patch
> >
> >Backport of GSO patches from 2.6.17,18,... Done by Herbert Xu as part of his
> >big netfront/back reworking and upgrade. This will mostly go away when we
> >upgrade to 2.6.18.
>
> I understand that. But what I need is an understanding of why Xen needs this
> right away.
A significant performance increase. Without it, DomU -> Dom0 networking is far
less than baremetal wirespeed; With it, DomU -> Dom0 networking has parity
with baremetal wirespeed. Herbert's preso at the summit had a few more details
http://xensource.com/files/summit_3/rdd-tso-xen.pdf
Regards,
Dan
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2006-10-06 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 7:25 reasons/requirements for some of patches/linux-2.6.16.29/* Jan Beulich
2006-10-06 7:25 ` Keir Fraser
2006-10-06 7:51 ` Jan Beulich
2006-10-06 8:17 ` Keir Fraser
2006-10-06 15:34 ` Stefan Berger
2006-10-06 12:09 ` Daniel P. Berrange [this message]
2006-10-10 3:38 ` Herbert Xu
2006-10-07 1:08 ` Andrew Warfield
2006-10-09 15:31 ` Stephen C. Tweedie
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=20061006120948.GA5580@redhat.com \
--to=berrange@redhat.com \
--cc=andy@xensource.com \
--cc=jbeulich@novell.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.