2002-10-04 16:55:15

by Mark Peloquin

[permalink] [raw]
Subject: Re: [Evms-devel] Re: [PATCH] EVMS core 1/4: evms.c


On Friday 04 October 2002 09:56, Christoph Hellwig wrote:

> > +/**
> > + * find_next_volume - locates first or next logical volume
> > + * @lv: current logical volume
> > + *
> > + * returns the next logical volume or NULL
> > + **/
>
> All user of this look like they better used list_for_each?
>
> > +
> > +/**
> > + * find_next_volume_safe - locates first or next logical volume (safe
> > for removes) + * @next_lv: ptr to next logical volume
> > + *
> > + * returns the next logical volume or NULL
> > + **/
>
> Dito with list_for_each_safe

This was done to abstract the storage/lookup
method. Currently with only 256 minors per major
a simply kernel list is adequate, however once
the kernel goes to 20-bit minors a list will not
be sufficient.



2002-10-04 16:59:21

by Christoph Hellwig

[permalink] [raw]
Subject: Re: [Evms-devel] Re: [PATCH] EVMS core 1/4: evms.c

> This was done to abstract the storage/lookup
> method. Currently with only 256 minors per major
> a simply kernel list is adequate, however once
> the kernel goes to 20-bit minors a list will not
> be sufficient.

Before that happens you'll get nice private pointers in the higher
level objects so you don't need to do lookups in any fast-path
anymore..