All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Warfield <andrew.warfield@gmail.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Steve Traugott <stevegt@terraluna.org>, xen-devel@lists.sourceforge.net
Subject: Re: AFS-based VBD backend
Date: Thu, 23 Dec 2004 12:36:30 +0000	[thread overview]
Message-ID: <eacc82a4041223043670114d0e@mail.gmail.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D12318A@liverpoolst.ad.cl.cam.ac.uk>

> The blocktap backend driver is what you want. I'm not sure of it's
> current state, but the plan is to enable you to terminate a blk device
> channel in user-space.

The driver currently does this.  There is a rather dated version of it
in the unstable tree...  It lets you either terminate a blkif
connection in userspace of a tap domain, or intercept in-flight
requests by proxying them to user-space before they are passed along
to a normal backend.  Data pages provided by the front end are mapped
up to user space by the tap driver, so there is no copying along that
path.

I've got a newer and more, um, robust ;) version of the blktap stuff
in my repository... it's a bit tied up with some of the other device
channel updates that we have been looking at lately though -- so it's
not in a state to integrate directly to the public trees.  I'd imagine
that much of this stuff should be ready to go into unstable in the
next few weeks...  hopefully along with a nettap as well.

Steve, if you need the tap more urgently than this, I can likely sort
out an interim version.  If you can wait until early january though,
that might be best.

> A future revision of blocktap could use kiovec's to avoid having to copy
> data into user space, and thus would give good performance.

arranging direct i/o to the mapped data pages is clearly the thing to
do.  I'll take a look at the kvec stuff over the next few weeks as
well.

a.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  parent reply	other threads:[~2004-12-23 12:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-23 11:41 AFS-based VBD backend Ian Pratt
2004-12-23 12:23 ` Steve Traugott
2004-12-23 12:36 ` Andrew Warfield [this message]
2004-12-23 13:48   ` Steve Traugott
2004-12-23 13:59     ` Andrew Warfield
2005-01-18  0:35     ` Steve Traugott
  -- strict thread matches above, loose matches on Subject: below --
2004-12-23 13:38 Ian Pratt
2005-01-04  2:54 ` Steve Traugott
2005-01-04  2:59   ` Kris Van Hees
2004-12-23 12:31 Ian Pratt
2004-12-23 13:17 ` Steve Traugott
2004-12-23  8:55 Steve Traugott
2004-12-23 10:37 ` Luciano Miguel Ferreira Rocha
2004-12-23 10:42   ` Keir Fraser
2004-12-23 10:56     ` Luciano Miguel Ferreira Rocha
2004-12-23 12:39       ` Steve Traugott
2004-12-23 11:58     ` Steve Traugott
2004-12-23 11:18   ` Steve Traugott
2004-12-28 19:21 ` Johannes Formann

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=eacc82a4041223043670114d0e@mail.gmail.com \
    --to=andrew.warfield@gmail.com \
    --cc=andrew.warfield@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=stevegt@terraluna.org \
    --cc=xen-devel@lists.sourceforge.net \
    /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.