[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: dreaddir/fxattr
- To: groenink@let.ruu.nl (Annius Groenink)
- Subject: Re: dreaddir/fxattr
- From: Julian Reschke <reschke@GOEDEL.UNI-MUENSTER.DE>
- Date: Wed, 19 Jan 94 14:53:30 MET DST
- Cc: mint@terminator.rs.itd.umich.edu (MiNT-Liste)
- In-reply-to: <199401191235.AA18775@ruulot.let.ruu.nl>; from "Annius Groenink" at Jan 19, 94 1:35 pm
- Organization: Westfaelische Wilhelms-Universitaet, Muenster, Germany Department of Mathematics
>
> >
> > Below is a first draft:
> >
> > Proposal for a combined call for Dreaddir/Fxattr:
> >
> > LONG Dreadattr( WORD len, LONG dirhandle, char *buf, WORD lflag, XATTR *xattr);
> >
> > len, dirhandle and buf are just like in Dreaddir. lflag and xattr
> > are the standard parameters for Fxattr.
> >
> > The only question I see is what to return when the directory entry
> > is available (Dreaddir succeeds), but the XATTR data aren't (Fxattr fails).
>
> Hello Julian.
>
> Sorry if I missed a point, but why would you combine the two functions,
> if the question you state above can be solved by calling the two of them
> separately? Does that speed things down that drastically? BTW, I agree
> that the Dreaddir method is very slow.
>
Because it minimizes the amout of kernel calls and adds the possibility
for faster implementations.
--
---------------------------------------------------
Julian F. Reschke, Hensenstr. 142, D-48161 Muenster
eMail: reschke@math.uni-muenster.de jr@ms.maus.de
___________________________________________________