From: Nick Logan <nick_logan@symantec.com>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: xen-devel@lists.xensource.com, Jon Mason <jdmason@us.ibm.com>
Subject: Re: EXPORT SYMBOL for alloc_vm_area
Date: Thu, 26 Jan 2006 15:55:13 +0000 [thread overview]
Message-ID: <43D8F0E1.10909@symantec.com> (raw)
In-Reply-To: <20060126153752.GA3421@granada.merseine.nu>
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
prev parent reply other threads:[~2006-01-26 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Ezkwr-000797-RL@host-192-168-0-1-bcn-london>
2006-01-25 11:36 ` Xen-devel Digest, Vol 11, Issue 86 Nick Logan
2006-01-25 11:40 ` EXPORT SYMBOL for alloc_vm_area Nick Logan
2006-01-25 14:25 ` Re: Xen-devel Digest, Vol 11, Issue 86 Muli Ben-Yehuda
2006-01-25 20:26 ` Jon Mason
2006-01-26 9:51 ` EXPORT SYMBOL for alloc_vm_area Nick Logan
2006-01-26 15:37 ` Muli Ben-Yehuda
2006-01-26 15:55 ` Nick Logan [this message]
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=43D8F0E1.10909@symantec.com \
--to=nick_logan@symantec.com \
--cc=jdmason@us.ibm.com \
--cc=mulix@mulix.org \
--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 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.