All of lore.kernel.org
 help / color / mirror / Atom feed
* reg. stale post attributes
@ 2016-05-26  8:35 Satya Prakash GS
  0 siblings, 0 replies; only message in thread
From: Satya Prakash GS @ 2016-05-26  8:35 UTC (permalink / raw)
  To: linux-nfs

Hi,

I have been going through NFS client code and looks like most of the
file operations get post attributes and client applies them after
checking for freshness. How does this scheme work when 2 ops modify
the same attribute on the server ? If op1 and op2 replies come out of
order from server or are applied on server out of order how does the
logic for freshness ensure that the client has the correct attributes.
Sorry, I am not a kernel expert and I could not quote examples for op1
and op2, I am trying to understand the behaviour from the file system
perspective logically.

Thanks,
Satya.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-05-26  8:35 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-05-26  8:35 reg. stale post attributes Satya Prakash GS

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.