All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>,
	Felipe Franciosi <felipe.franciosi@citrix.com>,
	George Dunlap <George.Dunlap@citrix.com>,
	Jonathan Ludlam <Jonathan.Ludlam@citrix.com>
Cc: Dave Scott <Dave.Scott@citrix.com>, Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Wen Congyang <wency@cn.fujitsu.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Ian Jackson <Ian.Jackson@citrix.com>,
	Yang Hongyang <yanghy@cn.fujitsu.com>
Subject: Re: [PATCH RFC 0/4] tools: Upstream blktap "2.5" as an external repo
Date: Thu, 26 Mar 2015 17:12:15 +0000	[thread overview]
Message-ID: <55143DEF.9060709@citrix.com> (raw)
In-Reply-To: <55143C60.2000907@eu.citrix.com>

On 26/03/15 17:05, George Dunlap wrote:
> On 03/26/2015 04:25 PM, Felipe Franciosi wrote:
>>> Another thing I'd like to explore (since this took all of about an afternoon to get
>>> working) is what it would take to switch to using
>>> blktap3 instead.  As I understand from my conversations with the XenServer
>>> team, they use a kernel module in XenServer when mounting an image in dom0
>>> for scalability reasons; but there's no reason XenProject need to do the same
>>> thing.
>> Today, to access virtual disks in dom0 we use the blktap2 kernel module that Jonathan Ludlam mentioned. This provides a block device (in /dev/xen/blktap-2/tapdev<minor>). In the (somewhat distant) past, we actually had blkfront in dom0.
> OK -- so the XenServer blktap2 kernel module is definitely being
> maintained.  That's good to know.
>
>> What is also needed to get blktap3 working is a gntdev supporting grant copy. I believe this is the order they are applied in 3.10:
>> https://github.com/xenserver/linux-3.x.pg/blob/master/master/0001-xen-install-xen-gntdev.h-and-xen-gntalloc.h.patch
>> https://github.com/xenserver/linux-3.x.pg/blob/master/master/xen-gntdev-grant-copy.patch
>> https://github.com/xenserver/linux-3.x.pg/blob/master/master/0002-xen-gntdev-mark-userspace-PTEs-as-special-on-x86-PV-.patch
>> https://github.com/xenserver/linux-3.x.pg/blob/master/master/0003-xen-gntdev-provide-a-set-of-pages-for-the-VMA.patch
>>
>> The _main_ difference between tapdisk2 and 3 is that tapdisk3 can connect directly to blkfront. It does all I/O via grant copies which has some implications in the way memory is handled in dom0.
> Right, I didn't realize blktap3 also required kernel changes.  Are those
> reasonably upstream-able, and is there any plan by the XenServer team to
> upstream them?

They are all in Linux 3.19 iirc.  These are not patches for blktap3 
specially; they are all patches fixing the use of userspace grant maps 
with /dev/xen/gnttab, which never functioned correctly in the past.

~Andrew

  reply	other threads:[~2015-03-26 17:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 12:46 [PATCH RFC 0/4] tools: Upstream blktap "2.5" as an external repo George Dunlap
2015-03-26 12:46 ` [PATCH RFC 1/4] build: Reorganize and briefly document "external repo" template in tools/Makefile George Dunlap
2015-03-30  9:07   ` Ian Campbell
2015-03-26 12:46 ` [PATCH RFC 2/4] build: Download and build extnernal blktap2.5 repo George Dunlap
2015-03-26 12:55   ` Ian Campbell
2015-03-26 14:04     ` George Dunlap
2015-03-30 14:33   ` Wei Liu
2015-03-30 14:41     ` Ian Campbell
2015-03-30 14:46       ` George Dunlap
2015-03-30 14:50       ` Andrew Cooper
2015-03-30 14:43     ` George Dunlap
2015-03-30 15:38       ` Wei Liu
2015-03-31  9:55         ` George Dunlap
2015-03-31 10:40           ` Stefano Stabellini
2015-03-31 11:10             ` George Dunlap
2015-03-31 12:02               ` Ian Campbell
2015-03-31 12:03               ` Ian Campbell
2015-03-26 12:46 ` [PATCH RFC 3/4] libxl: Use XenServer's blktap2.5 George Dunlap
2015-03-26 12:46 ` [PATCH RFC 4/4] tools: Remove in-tree blktap2 George Dunlap
2015-03-26 13:50 ` [PATCH RFC 0/4] tools: Upstream blktap "2.5" as an external repo George Dunlap
2015-03-26 15:47 ` Jon Ludlam
2015-03-26 16:08   ` George Dunlap
2015-03-26 16:25     ` Felipe Franciosi
2015-03-26 17:05       ` George Dunlap
2015-03-26 17:12         ` Andrew Cooper [this message]
2015-03-26 17:23           ` George Dunlap
2015-03-26 18:06             ` Felipe Franciosi
2015-03-26 16:42     ` Jon Ludlam

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=55143DEF.9060709@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Dave.Scott@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=Jonathan.Ludlam@citrix.com \
    --cc=felipe.franciosi@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=wency@cn.fujitsu.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yanghy@cn.fujitsu.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.