From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Xen 4.4 development update Date: Mon, 19 Aug 2013 15:08:43 +0300 Message-ID: <20130819120843.GL2924@reaktio.net> References: <20130815130227.GB7042@zion.uk.xensource.com> <520CEED102000078000EC339@nat28.tlf.novell.com> <20130815132428.GD7042@zion.uk.xensource.com> <521203A8.8000300@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <521203A8.8000300@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: Ian Jackson , Wei Liu , Jan Beulich , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Mon, Aug 19, 2013 at 12:38:16PM +0100, George Dunlap wrote: > > * However, blktap is unmaintained. Unless someone steps up to add > the functionality (which is not recommended as it would probably te > a waste of effort), it will continue to require a modprobe. On newer > systems, without blktap, the modprobe will be harmless. So for > blktap, the modprobe will have to remain for the forseeable future. > What I've been wondering.. XenServer is shipping with and using blktap, so there must be someone maintaining blktap at Citrix? I also understand blktap is on the way out and will be replaced with qdisc in the future.. -- Pasi