All of lore.kernel.org
 help / color / mirror / Atom feed
From: Austin Gonyou <austin@coremetrics.com>
To: linux-lvm@sistina.com
Cc: Linux Mailing List <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@redhat.com>
Subject: Re: [linux-lvm] [Patch] Latest device-mapper snapshot
Date: Wed Oct 23 13:01:02 2002	[thread overview]
Message-ID: <1035395934.14726.12.camel@ubergeek> (raw)
In-Reply-To: <20021023102503.GA25925@fib011235813.fsnet.co.uk>

YAY!!! :) I will try asap. :-D I will also try with qla2200's and see if
I can break it! :)

On Wed, 2002-10-23 at 05:25, Joe Thornber wrote:
> New patchballs are available here:
> 
> http://people.sistina.com/~thornber/patches/2.5-stable/
> 
> Including a diff against 2.5.44-ac1.  There are a lot of changes in
> here compared to the last release, however most of these are due to
> code refactoring rather than bug fixes.  Highlights include:
> 
> o) Make the changes recommended by Christoph Hellwig and others:
>    http://marc.theaimsgroup.com/?l=linux-kernel&m=103462345119681&w=2
> 
> o) Add reference count to struct mapped_device, and struct dm_table.
> 
> o) Hide the above two structs in their respective .c file
> 
> o) Move all locking of struct mapped_device into dm.c (we can do this
> now because
>    of the reference counting).
> 
> o) Remove the name and uuid field from struct mapped device, these are
> really
>    only used by the interface as a way of refering to devices.
> 
> o) Nobody needs to lookup from kdev_t -> struct mapped_device, so remove
>    that hash table (thanks to Al Viros recent bdev->bd_disk stuff).
> 
> o) dm.c has no need of the dm-hash.c file any more, so merge dm-hash.c
> into
>    dm-ioctl.c (the fs interface uses the dcache for lookups).
> 
> 
> There are still open issues that prevent things working perfectly:
> 
> o) The gendisk hash table is getting confused when removing a device.
> eg, if
>    I create 3 devices with minors (1, 2, 3).  Then remove minor 2,
> get_gendisk 
>    will remove minor == 3. (Or I've done something really stupid).
> 
> o) Splitting pages still doesn't work, this is a generic block layer
>    thing rather than dm.  In practise I can only trigger this with
>    striped targets.  So stick to linear targets for now.
> 
> 
> Filesystem interface to follow before the end of the week.
> 
> - Joe
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

WARNING: multiple messages have this Message-ID (diff)
From: Austin Gonyou <austin@coremetrics.com>
To: linux-lvm@sistina.com
Cc: Linux Mailing List <linux-kernel@vger.kernel.org>,
	Alan Cox <alan@redhat.com>
Subject: Re: [linux-lvm] [Patch] Latest device-mapper snapshot
Date: 23 Oct 2002 12:58:54 -0500	[thread overview]
Message-ID: <1035395934.14726.12.camel@ubergeek> (raw)
In-Reply-To: <20021023102503.GA25925@fib011235813.fsnet.co.uk>

YAY!!! :) I will try asap. :-D I will also try with qla2200's and see if
I can break it! :)

On Wed, 2002-10-23 at 05:25, Joe Thornber wrote:
> New patchballs are available here:
> 
> http://people.sistina.com/~thornber/patches/2.5-stable/
> 
> Including a diff against 2.5.44-ac1.  There are a lot of changes in
> here compared to the last release, however most of these are due to
> code refactoring rather than bug fixes.  Highlights include:
> 
> o) Make the changes recommended by Christoph Hellwig and others:
>    http://marc.theaimsgroup.com/?l=linux-kernel&m=103462345119681&w=2
> 
> o) Add reference count to struct mapped_device, and struct dm_table.
> 
> o) Hide the above two structs in their respective .c file
> 
> o) Move all locking of struct mapped_device into dm.c (we can do this
> now because
>    of the reference counting).
> 
> o) Remove the name and uuid field from struct mapped device, these are
> really
>    only used by the interface as a way of refering to devices.
> 
> o) Nobody needs to lookup from kdev_t -> struct mapped_device, so remove
>    that hash table (thanks to Al Viros recent bdev->bd_disk stuff).
> 
> o) dm.c has no need of the dm-hash.c file any more, so merge dm-hash.c
> into
>    dm-ioctl.c (the fs interface uses the dcache for lookups).
> 
> 
> There are still open issues that prevent things working perfectly:
> 
> o) The gendisk hash table is getting confused when removing a device.
> eg, if
>    I create 3 devices with minors (1, 2, 3).  Then remove minor 2,
> get_gendisk 
>    will remove minor == 3. (Or I've done something really stupid).
> 
> o) Splitting pages still doesn't work, this is a generic block layer
>    thing rather than dm.  In practise I can only trigger this with
>    striped targets.  So stick to linear targets for now.
> 
> 
> Filesystem interface to follow before the end of the week.
> 
> - Joe
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


  reply	other threads:[~2002-10-23 13:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23  5:25 [linux-lvm] [Patch] Latest device-mapper snapshot Joe Thornber
2002-10-23 10:25 ` Joe Thornber
2002-10-23 13:01 ` Austin Gonyou [this message]
2002-10-23 17:58   ` [linux-lvm] " Austin Gonyou
2002-10-25  4:52 ` [linux-lvm] " Joe Thornber
2002-10-25  9:52   ` Joe Thornber
  -- strict thread matches above, loose matches on Subject: below --
2002-10-23 11:55 [linux-lvm] " Greg Freemyer
2002-10-24  2:41 ` Heinz J . Mauelshagen
2002-10-24  3:36 ` Joe Thornber

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=1035395934.14726.12.camel@ubergeek \
    --to=austin@coremetrics.com \
    --cc=alan@redhat.com \
    --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 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.