Searched hist:"5445 b1fbd123420bffed5e629a420aa2a16bf849" (Results 1 – 5 of 5) sorted by relevance
| /openbmc/linux/fs/nfs/ |
| H A D | delegation.h | diff 5445b1fbd123420bffed5e629a420aa2a16bf849 Sat Sep 05 18:06:58 CDT 2015 Trond Myklebust <trond.myklebust@primarydata.com> NFSv4: Respect the server imposed limit on how many changes we may cache
The NFSv4 delegation spec allows the server to tell a client to limit how
much data it cache after the file is closed. In return, the server
guarantees enough free space to avoid ENOSPC situations, etc.
Prior to this patch, we assumed we could always cache aggressively after
close. Unfortunately, this causes problems with servers that set the
limit to 0 and therefore do not offer any ENOSPC guarantees.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
|
| H A D | nfs4file.c | diff 5445b1fbd123420bffed5e629a420aa2a16bf849 Sat Sep 05 18:06:58 CDT 2015 Trond Myklebust <trond.myklebust@primarydata.com> NFSv4: Respect the server imposed limit on how many changes we may cache
The NFSv4 delegation spec allows the server to tell a client to limit how
much data it cache after the file is closed. In return, the server
guarantees enough free space to avoid ENOSPC situations, etc.
Prior to this patch, we assumed we could always cache aggressively after
close. Unfortunately, this causes problems with servers that set the
limit to 0 and therefore do not offer any ENOSPC guarantees.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
|
| H A D | delegation.c | diff 5445b1fbd123420bffed5e629a420aa2a16bf849 Sat Sep 05 18:06:58 CDT 2015 Trond Myklebust <trond.myklebust@primarydata.com> NFSv4: Respect the server imposed limit on how many changes we may cache
The NFSv4 delegation spec allows the server to tell a client to limit how
much data it cache after the file is closed. In return, the server
guarantees enough free space to avoid ENOSPC situations, etc.
Prior to this patch, we assumed we could always cache aggressively after
close. Unfortunately, this causes problems with servers that set the
limit to 0 and therefore do not offer any ENOSPC guarantees.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
|
| H A D | file.c | diff 5445b1fbd123420bffed5e629a420aa2a16bf849 Sat Sep 05 18:06:58 CDT 2015 Trond Myklebust <trond.myklebust@primarydata.com> NFSv4: Respect the server imposed limit on how many changes we may cache
The NFSv4 delegation spec allows the server to tell a client to limit how
much data it cache after the file is closed. In return, the server
guarantees enough free space to avoid ENOSPC situations, etc.
Prior to this patch, we assumed we could always cache aggressively after
close. Unfortunately, this causes problems with servers that set the
limit to 0 and therefore do not offer any ENOSPC guarantees.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
|
| H A D | internal.h | diff 5445b1fbd123420bffed5e629a420aa2a16bf849 Sat Sep 05 18:06:58 CDT 2015 Trond Myklebust <trond.myklebust@primarydata.com> NFSv4: Respect the server imposed limit on how many changes we may cache
The NFSv4 delegation spec allows the server to tell a client to limit how
much data it cache after the file is closed. In return, the server
guarantees enough free space to avoid ENOSPC situations, etc.
Prior to this patch, we assumed we could always cache aggressively after
close. Unfortunately, this causes problems with servers that set the
limit to 0 and therefore do not offer any ENOSPC guarantees.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
|