From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
NetDev <netdev@vger.kernel.org>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
Herbert Xu <herbert@gondor.apana.org.au>,
Vladislav Bolkhovitin <vst@vlnb.net>,
Xen-devel <xen-devel@lists.xensource.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Using splice to carry Xen granted pages through the network stack?
Date: Wed, 18 Mar 2009 17:04:52 -0700 [thread overview]
Message-ID: <49C18C24.6000601@goop.org> (raw)
Hi Jens,
In a thread from December last year ("Support for zero-copy TCP transmit
of user space data") you suggested using the splice machinery as a way
to implement zero-copy transmit for iscsi data.
I have a similar problem relating to doing zero-copy transmit of pages
granted from another Xen domain. These are pages which are in some ways
similar to device mappings (they have no struct page unless we jump
through some hoops to give them one, for example) which are given to us
by another domain (virtual machine)'s network stack since they contain
data they want to transmit through our stack. Once the stack has
finished with the pages we need to get them back to return to the
original domain (and definitely not let them get freed into the normal
kernel pool).
I've been looking a little bit at the splice stuff to work out how it
might be useful in this case. One issue struct page; I guess we really
can't get away from having one for granted pages and still get the full
value of using splice (especially I can see also see it being useful on
the block side of the world as well). So, we can jump through hoops for
that.
But the general plumbing of splice into the network stack seems to have
been an open issue since you introduced it 3 years ago (using as a
reference http://lwn.net/Articles/181169/). Has any work been done on
this aspect since? What would need to be done to do it? Would it mean
wiring up a pipe_buffer_operations to operate with something like
Rusty's skb_shared_info destructor?
Thanks,
J
next reply other threads:[~2009-03-19 0:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 0:04 Jeremy Fitzhardinge [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-15 17:14 Using splice to carry Xen granted pages through the network stack? Jeremy Fitzhardinge
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=49C18C24.6000601@goop.org \
--to=jeremy@goop.org \
--cc=herbert@gondor.apana.org.au \
--cc=jens.axboe@oracle.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=vst@vlnb.net \
--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 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).