You should take this to the device mapper list, but I'll try here.
For lurkers, this drawing may be helpful:
http://www.thomas-krenn.com/en/oss/linux-io-stack-diagram/linux-io-stack-diagram_v1.0.pdf
On Wed, May 8, 2013 at 11:15 AM, neha naik wrote:
> Hi Greg,
> Thanks for the information. I ha
Hi Greg,
Thanks for the information. I have another question :).
Is there some less flexibility if we use device mapper target?
For example in block device driver you can use the api such that it won't
use the OS io scheduler, so the io comes directly to the block device
driver through the
The block layers can be layered both ways. DM is the newer
infrastructure and was created in the early days of 2.6
If what I was writing could fit into a dm-target, that is what I would do.
There are significant projects like drbd and mdraid that are not
dm-targets, but I think their is a long t
Hi Neha,
LVM uses device mapper. Advantages of using device mapper is that you can
stack different dm-targets on each other.
I am really not aware of block device drivers.
May be Greg can help us understand the actual pros and cons.
Thanks,
Gaurav
On Wed, May 1, 2013 at 9:45 PM, neha naik wr
Hi Gaurav,
I went through your blog and it is really informative. But after reading
that i realized that i have a question:
If I want to write a block device driver which is going to sit on lvm
(and do some functionality on top of it) then should i go for the block
device driver api
or write i
Hi Amit,
I had compiled some notes on my blog.
Here are some links on writing your own device mapper target.
http://techgmm.blogspot.in/p/writing-your-own-device-mapper-target.html
Concept of device mapper target.
http://techgmm.blogspot.in/p/device-mapper-layer-explored-every.html
Thanks,
Gaura
Hi
On Mon, Apr 29, 2013 at 9:51 AM, amit mehta wrote:
> On Sun, Apr 28, 2013 at 5:24 PM, Greg Freemyer
> wrote:
>> A nice diagram of the overall storage subsystem is at
>> http://www.thomas-krenn.com/en/oss/linux-io-stack-diagram.html
>>
>> Dm is just a single block in it, but it can help to s
On Mon, Apr 29, 2013 at 12:51 PM, amit mehta wrote:
> On Sun, Apr 28, 2013 at 5:24 PM, Greg Freemyer
> wrote:
>> A nice diagram of the overall storage subsystem is at
>> http://www.thomas-krenn.com/en/oss/linux-io-stack-diagram.html
>>
>> Dm is just a single block in it, but it can help to see
On Sun, Apr 28, 2013 at 5:24 PM, Greg Freemyer wrote:
> A nice diagram of the overall storage subsystem is at
> http://www.thomas-krenn.com/en/oss/linux-io-stack-diagram.html
>
> Dm is just a single block in it, but it can help to see where it fits in
> overall.
>
> Btw: that diagram doesn't sho
Kumar Amit Mehta wrote:
>I'm looking for information on device-mapper, the kernel space utility
>for
>Logical Volume Management (LVM2). It seems that the relevant code
>resides under
>drivers/md and a lot of other information is under
>Documentation/device-mapper/
>That's fine, but is there an
I'm looking for information on device-mapper, the kernel space utility for
Logical Volume Management (LVM2). It seems that the relevant code resides under
drivers/md and a lot of other information is under Documentation/device-mapper/
That's fine, but is there any other document that gives more fi
11 matches
Mail list logo
