On Thu, Aug 14, 2008 at 06:44:33PM -0700, david@lang.hm wrote:According to Eric Paris the clean/dirty state is only stored in memory. We could use the extended attribute interface as a way of not defining a new system call, or some other interface, but I'm not sure it's such a great match given that the extended attributes interface are designed for persistent data. I agree that doesn't actually work very well for the tracker use case, where you the clean/dirty bit to be persistent (in case the tracker is disabled due to the fact you are running on battery, for example, and then you reboot). - Ted --
| Mark Lord | 2.6.25-rc8: FTP transfer errors |
| Kamalesh Babulal | Re: 2.6.23-rc6-mm1 |
| Greg Kroah-Hartman | [PATCH 025/196] paride: Convert from class_device to device for block/paride |
| Stephen Rothwell | Announce: Linux-next (Or Andrew's dream :-)) |
git: | |
| Linus Torvalds | Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49 |
| David Miller | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
