[Lustre-devel] OSD iterator interface

Nikita Danilov danilov at gmail.com
Mon Apr 6 00:43:01 PDT 2009

2009/4/6 Alex Zhuravlev <bzzz at sun.com>


> I agree with what Oleg said. I think there are two-stages processing here:
> 1) osd should be able to clean "value" from compatibility stuff like inodes
> 2) mdd should be able to store this value in own buffer in, possible, some
>   efficient form
> >>>>> di wang (dw) writes:


>  >>
>  >> Am I missing something stupid? Are there any objections, would
>  >> this break anything?

the  reason dt_it_ops have one-entry-at-a-time interface is that originally
iterators were able to update indices as well. *E.g.*, it was expected that
/orphan index processing would read one entry, handle it, and then delete it
from the index (a possibly mistaken belief in the virtue of simplicity and
evilness of premature optimization also played its rôle). Eventually all
existing use cases for the updating iterators were eliminated and ->set_*()
methods were dropped from dt_it_ops.

>  >>
>  >> Bye,
>  >> Oleg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20090406/5b040647/attachment.htm>

More information about the lustre-devel mailing list