Re: struct dirent.d_reclen

2009-09-02 Thread Christopher Faylor
On Tue, Sep 01, 2009 at 07:10:20PM -0600, Eric Blake wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >According to Christopher Faylor on 9/1/2009 5:37 PM: >> Maybe you mean d_namlen? > >Yes; serves me right for confusing readdir(2) and readdir(3) man pages. > >>It is not a given that addin

Re: struct dirent.d_reclen

2009-09-01 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 9/1/2009 7:10 PM: > According to Christopher Faylor on 9/1/2009 5:37 PM: >> Maybe you mean d_namlen? > > Yes; serves me right for confusing readdir(2) and readdir(3) man pages. Actually, it looks like Linux has only d_recle

Re: struct dirent.d_reclen

2009-09-01 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Christopher Faylor on 9/1/2009 5:37 PM: > Maybe you mean d_namlen? Yes; serves me right for confusing readdir(2) and readdir(3) man pages. > It is not a given that adding d_reclen would speed anything up since it > cause every single pro

Re: struct dirent.d_reclen

2009-09-01 Thread Christopher Faylor
On Tue, Sep 01, 2009 at 05:39:02PM +, Eric Blake wrote: >Wish list (probably post 7.1): As long as we are making struct dirent more >like >Linux with the recent addition of d_type, we should probably also burn two of >the remaining 3 __d_unused1 bytes to declare unsigned short d_reclen, whos

struct dirent.d_reclen

2009-09-01 Thread Eric Blake
Wish list (probably post 7.1): As long as we are making struct dirent more like Linux with the recent addition of d_type, we should probably also burn two of the remaining 3 __d_unused1 bytes to declare unsigned short d_reclen, whose value is always strlen(d_name), so that applications could get