From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Logan Subject: Re: EXPORT SYMBOL for alloc_vm_area Date: Thu, 26 Jan 2006 15:55:13 +0000 Message-ID: <43D8F0E1.10909@symantec.com> References: <43D762AB.2010702@symantec.com> <20060125142541.GC24849@granada.merseine.nu> <20060125202648.GA6794@us.ibm.com> <43D89BBC.2060306@symantec.com> <20060126153752.GA3421@granada.merseine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20060126153752.GA3421@granada.merseine.nu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Muli Ben-Yehuda Cc: xen-devel@lists.xensource.com, Jon Mason List-Id: xen-devel@lists.xenproject.org Muli Ben-Yehuda wrote: >On Thu, Jan 26, 2006 at 09:51:56AM +0000, Nick Logan wrote: > > > >>Some background to my questions. I am currently investigating the port >>on the Veritas volume manager and filesystem to the xen architecture. >>The logical approach is to use the volume manager in Dom0 and the >>filesystem in DomU and this can currently be done using the vbd driver. >>However the filesystem in DomU then just sees the volume as a disk >>partition and is unable to make use of a number of private functions >>supplied by the volume manager to provide the filesystem with additional >>functionality and performance. Therefore I am investigating the >>implementation of a virtual volume driver that would provide those >>private functions in DomU. There is no need for this driver to be >>included in the xen source, hence the need for a loadable driver. >> >> > >Considering that Xen drivers will end up in the Linux tree in the >(hopefully) not too distant future, and the Linux community's well >known aversion for out of tree modules, please consider submitting >it. It will make your life a whole lot easier in the long run. > >Cheers, >Muli > > Thanks for the suggestion. I'll certainly consider submitting it as it clearly will have to be a GPL module, but as the associated filesystem and volume manager are not in the tree I'd like to have the option of having it out of the tree. Nick