Messages in this thread | | | Subject | Re: [OFFTOPIC] f_pos ? | From | FabF <> | Date | Tue, 06 Jul 2004 22:51:24 +0200 |
| |
On Tue, 2004-07-06 at 21:58, Maneesh Soni wrote: > On Sun, Jul 04, 2004 at 07:31:29PM +0000, FabF wrote: > > Hi, > > > > I try to understand how readdir process works and I can't understand > > f_pos management : > > > > Having in mind things work that way : > > > > user : ls > > glibc : > > open (->sys_open) > > getdentries64 (->sys_getdentries64) > > > > kernel: > > sys_getdentries64 > > ->vfs_readdir > > ->ext2_readdir > > > > At that point, I don't understand why ext2_readdir is playing with > > filp->f_pos .... It should be 0 ...Why does it care about offset ? > > > > I think it may not be 0 all the time. A seekdir() could change could change > the offset to non-zero. > btw, someone could tell why old ext2 readdir had "do the readahead" feature ; current ext3 as well but new ext2 implementation doesn't ???
Regards, FabF
> Thanks > Maneesh
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |