On 05/24/2012 03:05 PM, Jeff Darcy wrote:
On 05/24/2012 03:10 AM, Xavier Hernandez wrote:
preparent and postparent have the attributes (modification time, size,
permissions, ...) of the parent directory of the file being modified
before and after the modification is done.
Thank you, Xavi. :)
On 05/24/2012 03:10 AM, Xavier Hernandez wrote:
> preparent and postparent have the attributes (modification time, size,
> permissions, ...) of the parent directory of the file being modified
> before and after the modification is done.
Thank you, Xavi. :) If you really want to have some fun,
On 05/24/2012 03:31 AM, Emmanuel Dreyfus wrote:
Jeff Darcy wrote:
in the protocol/server xlator, there are many occurences where
callbacks have a struct iatt for preparent and postparent. What are
these for?
NFS needs them to support its style of caching.
Let me rephrase: what information is
Jeff Darcy wrote:
> > in the protocol/server xlator, there are many occurences where
> > callbacks have a struct iatt for preparent and postparent. What are
> > these for?
>
> NFS needs them to support its style of caching.
Let me rephrase: what information is stored in preparent and postparent
On Wed, 23 May 2012 16:58:02 +
Emmanuel Dreyfus wrote:
> in the protocol/server xlator, there are many occurences where
> callbacks have a struct iatt for preparent and postparent. What are
> these for?
NFS needs them to support its style of caching.
_
Hi
in the protocol/server xlator, there are many occurences where callbacks
have a struct iatt for preparent and postparent. What are these for?
Is it a normal behavior to have different things in preparent and
postparent?
--
Emmanuel Dreyfus
m...@netbsd.org
___
