All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Shrivastava <viveks@cs.wisc.edu>
To: dm@uk.sistina.com, linux-LVM@sistina.com
Subject: [linux-lvm] Relationship between Device Mapper and LVM2
Date: Fri, 01 Apr 2005 01:11:51 -0600	[thread overview]
Message-ID: <424CF437.1050607@cs.wisc.edu> (raw)

Dear Sir,
        We are trying to do some work on LVM2, by trying to make it more 
dynamic and suitable for virtual machines. We have a very fundamental 
doubt as follows:

Is LVM2 based on top of "device mapper" and uses "device mapper" as the 
underlying layer of support for writing /reading on the disk. Or Device 
mapper is placed between the kernel and the LVM2. Aslo if possible 
please tell us the entry point of kernel into the device mapper.

Any suggestions on this topic will be highly appreciated.

Thanks,
Vivek

             reply	other threads:[~2005-04-01  7:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01  7:11 Vivek Shrivastava [this message]
2005-04-01 15:17 ` [linux-lvm] Relationship between Device Mapper and LVM2 Alasdair G Kergon
2005-04-04  4:14   ` Vivek Shrivastava

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=424CF437.1050607@cs.wisc.edu \
    --to=viveks@cs.wisc.edu \
    --cc=dm@uk.sistina.com \
    --cc=linux-LVM@sistina.com \
    --cc=linux-lvm@redhat.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.