[506] in Info-AFS_Redistribution
Re: asynch file store?
daemon@ATHENA.MIT.EDU (Lyle_Seaman@transarc.com)
Fri Dec 20 18:08:48 1991
Date: Fri, 20 Dec 1991 17:35:05 -0500 (EST)
From: Lyle_Seaman@transarc.com
To: Info-AFS@transarc.com
In-Reply-To: <EdIZgXA91HvQ4xLq9b@rchland.ibm.com>
I sent Paul a terse note, then decided that perhaps a broader audience
might be interested.
There are several ways that data gets written from the Cache Manager to
the file server. These are the ones that come to mind most readily.
1. based on a periodic timer
2. during attempts to reclaim LRU space in the cache
3. during/after close()
4. during fsync()
5. as a result of a FLUSH pioctl
Basically, what Paul was requesting is basically the same functionality
that fsync() provides, except that he probably wants a little more
asynchrony, and probably not any guarantees about completion, but it's
the easy way out. I think that if I were in Paul's shoes, I'd try
something like
fork
if not parent
exit
fi
which implicitly closes all of the child's files, thus pushing the data
back to the server, more-or-less asynchronously.
