From: Laszlo Ersek <lersek@redhat.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
James Harper <james.harper@bendigoit.com.au>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>
Subject: Re: Features and bug-fixes that went in Linux 3.2
Date: Thu, 12 Jan 2012 18:02:46 +0100 [thread overview]
Message-ID: <4F0F1236.6010705@redhat.com> (raw)
In-Reply-To: <1326148662.29084.77.camel@dagon.hellion.org.uk>
On 01/09/12 23:37, Ian Campbell wrote:
> On Mon, 2012-01-09 at 22:26 +0000, James Harper wrote:
>>> - Initial work laid out for netback page-flipping (also called zero-copying).
>>
>> Isn't this how it used to work originally?
>
> Some of the original infrastructure for doing this was not upstreamable
> (the PageForeign stuff) so while upstream netback I decided to go with a
> simpler/less-intrusive copying mode so we could have some sort of
> networking support in mainline.
>
> I've been working on re-laying the necessary infrastructure to allow for
> page flipping/mapping mode in upstream (as well as fixing another
> generic class of bug) -- you can see the "skb frag destructor" patches
> on the netdev list.
(Ultimately I found it here:
http://lwn.net/Articles/474791/
.)
Ian, do you think the NFS fix in
http://article.gmane.org/gmane.linux.nfs/45955
for problem
http://marc.info/?l=linux-nfs&m=122424132729720&w=2
would be technically feasible to port to 2.6.18, based on the existing
PageForeign stuff instead of parts 1-5 of the series?
Thanks
Laszlo
next prev parent reply other threads:[~2012-01-12 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 21:30 Features and bug-fixes that went in Linux 3.2 Konrad Rzeszutek Wilk
2012-01-09 22:26 ` James Harper
2012-01-09 22:37 ` Ian Campbell
2012-01-12 17:02 ` Laszlo Ersek [this message]
2012-01-12 17:23 ` Ian Campbell
2012-01-10 8:47 ` Fantu
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=4F0F1236.6010705@redhat.com \
--to=lersek@redhat.com \
--cc=Ian.Campbell@citrix.com \
--cc=james.harper@bendigoit.com.au \
--cc=konrad.wilk@oracle.com \
--cc=pbonzini@redhat.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.