From: Joe Thornber <joe@fib011235813.fsnet.co.uk>
To: Linux Mailing List <linux-kernel@vger.kernel.org>, linux-lvm@sistina.com
Subject: [PATCH] 2.5 version of device mapper submission
Date: Wed, 9 Oct 2002 19:12:59 +0100 [thread overview]
Message-ID: <20021009181259.GA25050@fib011235813.fsnet.co.uk> (raw)
The 2.5 port of device-mapper is available from:
bk://device-mapper.bkbits.net/2.5-stable
There are 6 changesets in here that are summarised at the end of this
email.
If you wish to use it you will need to install libdevmapper:
ftp://ftp.sistina.com/pub/LVM2/device-mapper/device-mapper-latest.tgz
and then either use dmsetup, or the LVM tools:
ftp://ftp.sistina.com/pub/LVM2/tools/LVM2.0-latest.tgz
Initial testing has been successful, though it hasn't been exercised
nearly as much as the stable 2.4 releases.
There is a chunk of ~50 lines in dm.c, which I have clearly labelled,
this is stop gap block splitting code that will be replaced with the
correct use of queue->merge_bvec_fn etc. However before I can make
this change there are a couple of other patches to the block layer
that I want to merge.
Since the feature freeze is looming I would appreciate it if this code
was merged now. Allowing me to patch/argue to get the extra
performance at my leisure. Good plan ?
Slightly more info available at: http://people.sistina.com/~thornber/
- Joe Thornber
ChangeSet@1.709, 2002-10-09 17:06:21+01:00, thornber@sistina.com
[mempool]
Most people use mempools in conjunction with slabs, this defines
a couple of utility functions for allocing/freeing.
ChangeSet@1.710, 2002-10-09 17:09:58+01:00, thornber@sistina.com
[vmalloc]
Introduce vcalloc, I only really want it to automate the size overflow
check when allocating arrays.
ChangeSet@1.711, 2002-10-09 17:28:44+01:00, thornber@sistina.com
[Device mapper]
The core of the device-mapper driver. No interface or target types
included as yet.
ftp://ftp.sistina.com/pub/LVM2/tools/LVM
ChangeSet@1.712, 2002-10-09 17:33:00+01:00, thornber@sistina.com
[Device mapper]
The linear target maps a contigous range of logical sectors onto an
contiguous range of physical sectors.
ChangeSet@1.713, 2002-10-09 17:36:55+01:00, thornber@sistina.com
[Device mapper]
The stripe target. Maps a range of logical sectors across many
physical volumes.
ChangeSet@1.714, 2002-10-09 17:41:10+01:00, thornber@sistina.com
[Device mapper]
Provide a traditional ioctl based interface to control device-mapper
from userland.
next reply other threads:[~2002-10-09 18:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 18:12 Joe Thornber [this message]
2002-10-09 18:31 ` [PATCH] 2.5 version of device mapper submission Andrew Morton
2002-10-09 18:44 ` Joe Thornber
2002-10-12 20:05 ` Alan Cox
2002-10-12 20:19 ` Alan Cox
2002-10-14 16:59 ` [linux-lvm] " Austin Gonyou
2002-10-14 17:11 ` Dave Jones
2002-10-14 17:13 ` [linux-lvm] Re: [PATCH] 2.5 version of device mapper submissi on Austin Gonyou
2002-10-14 17:56 ` [linux-lvm] Re: [PATCH] 2.5 version of device mapper submission Joe Thornber
2002-10-14 21:03 ` [linux-lvm] Re: [PATCH] 2.5 version of device mapper submissi on Austin Gonyou
2002-10-15 8:21 ` [linux-lvm] Re: [PATCH] 2.5 version of device mapper submission Jens Axboe
2002-10-15 9:32 ` Joe Thornber
2002-10-15 9:36 ` Jens Axboe
2002-10-15 10:20 ` Joe Thornber
2002-10-15 10:34 ` Jens Axboe
2002-10-15 14:52 ` Kevin Corry
2002-10-15 15:06 ` Kevin Corry
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=20021009181259.GA25050@fib011235813.fsnet.co.uk \
--to=joe@fib011235813.fsnet.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).