Re: How long can an inode structure reside in the inode_cache? - read the code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>Maybe you should spend a week reading the code?  It can be a lot of
>fun, and you might even find a bug or two...

I'm not sure how serious this suggestion is, but it could be taken as as 
advice not to ask questions like this on the list, and I'd like to say 
that the questions are entirely appropriate.

It makes more sense to me to ask someone, via linux-fsdevel, who has 
already spent the week analyzing the code than to duplicate that effort.

Many people, including me, have difficulty extracting the big picture from 
Linux source code, and have very little fun trying.  Questions of object 
lifetimes and memory management are big-picture issues.  I can tell from 
reading lists such as linux-fsdevel that there are others who read Linux C 
code like they read a textbook.  (These are the folks who get irritated at 
excessive commenting and long variable names).  But for the rest of us, 
asking an expert shouldn't be discouraged.

--
Bryan Henderson                     IBM Almaden Research Center
San Jose CA                         Filesystems

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux