At 1/3/2004 06:57 PM +0000, viro _at_ parcelfarce.linux.theplanet.co.uk wrote: >On Sat, Jan 03, 2004 at 01:39:41PM -0500, Bill Davidsen wrote: >>Moving the definitions is fine, but some user programs, like backup >>programs, do benefit from direct interpretation of the inode. Clearly >>that's not a normal user program, but this information is not only useful >>inside the kernel. > >No, they do not. They care about on-disk structures, not the in-core ones >fs driver happens to build. They may if trying to do an online backup of open files, especially if attempting to maintain transactional integrity (i.e. make the backup logically atomic). -- Jeff Woods <kazrak+kernel _at_ cesmail.net> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups: References:
- Re: Should struct inode be made available to userspace?Bill Davidsen
- Re: Should struct inode be made available to userspace?viro
- Prev by Date: Re: inode_cache / dentry_cache not being reclaimed aggressively enough on low-memory PCs
- Next by Date: Re: Should struct inode be made available to userspace?
- Previous by thread: Re: Should struct inode be made available to userspace?
- Next by thread: Re: Should struct inode be made available to userspace?
- Indexes:[Main][Thread]