All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Shrivastava <viveks@cs.wisc.edu>
To: Alasdair G Kergon <agk@redhat.com>
Cc: linux-LVM@redhat.com
Subject: Re: [linux-lvm] Relationship between Device Mapper and LVM2
Date: Sun, 03 Apr 2005 23:14:32 -0500	[thread overview]
Message-ID: <4250BF28.7050704@cs.wisc.edu> (raw)
In-Reply-To: <20050401151721.GC14307@agk.surrey.redhat.com>

Dear Sir,
         Thanks a lot for your timely response. It has helped us a lot. 
Just one last query. When a user program issues a read command from a 
file residing on a logical volume, how does the call actually gets 
mapped onto the hard disk. We believe that the kernel passes the 
"generic" command to the device mapper which then makes the final 
translation on the basis of mapping tables stored with it. We just 
wanted to be sure that LVM2 code does figure in the translation of the 
read requests from the user applications to the disk.

Thanking you in advance,
Vivek

Alasdair G Kergon wrote:
> On Fri, Apr 01, 2005 at 01:11:51AM -0600, Vivek Shrivastava wrote:
> 
>>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.
> 
>  
> http://people.redhat.com/agk/talks/FOSDEM_2005/
> 
> esp.  http://people.redhat.com/agk/talks/FOSDEM_2005/img3.gif
>       http://people.redhat.com/agk/talks/FOSDEM_2005/img4.gif
> 
> Alasdair

      reply	other threads:[~2005-04-04  4:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01  7:11 [linux-lvm] Relationship between Device Mapper and LVM2 Vivek Shrivastava
2005-04-01 15:17 ` Alasdair G Kergon
2005-04-04  4:14   ` Vivek Shrivastava [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=4250BF28.7050704@cs.wisc.edu \
    --to=viveks@cs.wisc.edu \
    --cc=agk@redhat.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.