Searched hist:e908bcf4f1a271e7c264dcbffc5881ced8bfacee (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/include/net/ |
| H A D | af_rxrpc.h | diff e908bcf4f1a271e7c264dcbffc5881ced8bfacee Thu Oct 04 03:54:29 CDT 2018 David Howells <dhowells@redhat.com> rxrpc: Allow the reply time to be obtained on a client call
Allow the epoch value to be queried on a server connection. This is in the
rxrpc header of every packet for use in routing and is derived from the
client's state. It's also not supposed to change unless the client gets
restarted.
AFS can make use of this information to deduce whether a fileserver has
been restarted because the fileserver makes client calls to the filesystem
driver's cache manager to send notifications (ie. callback breaks) about
conflicting changes from other clients. These convey the fileserver's own
epoch value back to the filesystem.
Signed-off-by: David Howells <dhowells@redhat.com>
|
| /openbmc/linux/net/rxrpc/ |
| H A D | af_rxrpc.c | diff e908bcf4f1a271e7c264dcbffc5881ced8bfacee Thu Oct 04 03:54:29 CDT 2018 David Howells <dhowells@redhat.com> rxrpc: Allow the reply time to be obtained on a client call
Allow the epoch value to be queried on a server connection. This is in the
rxrpc header of every packet for use in routing and is derived from the
client's state. It's also not supposed to change unless the client gets
restarted.
AFS can make use of this information to deduce whether a fileserver has
been restarted because the fileserver makes client calls to the filesystem
driver's cache manager to send notifications (ie. callback breaks) about
conflicting changes from other clients. These convey the fileserver's own
epoch value back to the filesystem.
Signed-off-by: David Howells <dhowells@redhat.com>
|