Searched hist:"6 ff8da08" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/fs/nfsd/ |
H A D | state.h | 6ff8da08 Fri Jun 04 19:04:45 CDT 2010 J. Bruce Fields <bfields@citi.umich.edu> nfsd4: Move callback setup to callback queue
Instead of creating the new rpc client from a regular server thread, set a flag, kick off a null call, and allow the null call to do the work of setting up the client on the callback workqueue.
Use a spinlock to ensure the callback work gets a consistent view of the callback parameters.
This allows, for example, changing the callback from contexts where sleeping is not allowed. I hope it will also keep the locking simple as we add more session and trunking features, by serializing most of the callback-specific work.
This also closes a small race where the the new cb_ident could be used with an old connection (or vice-versa).
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> 6ff8da08 Fri Jun 04 19:04:45 CDT 2010 J. Bruce Fields <bfields@citi.umich.edu> nfsd4: Move callback setup to callback queue Instead of creating the new rpc client from a regular server thread, set a flag, kick off a null call, and allow the null call to do the work of setting up the client on the callback workqueue. Use a spinlock to ensure the callback work gets a consistent view of the callback parameters. This allows, for example, changing the callback from contexts where sleeping is not allowed. I hope it will also keep the locking simple as we add more session and trunking features, by serializing most of the callback-specific work. This also closes a small race where the the new cb_ident could be used with an old connection (or vice-versa). Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
|
H A D | nfs4callback.c | 6ff8da08 Fri Jun 04 19:04:45 CDT 2010 J. Bruce Fields <bfields@citi.umich.edu> nfsd4: Move callback setup to callback queue
Instead of creating the new rpc client from a regular server thread, set a flag, kick off a null call, and allow the null call to do the work of setting up the client on the callback workqueue.
Use a spinlock to ensure the callback work gets a consistent view of the callback parameters.
This allows, for example, changing the callback from contexts where sleeping is not allowed. I hope it will also keep the locking simple as we add more session and trunking features, by serializing most of the callback-specific work.
This also closes a small race where the the new cb_ident could be used with an old connection (or vice-versa).
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> 6ff8da08 Fri Jun 04 19:04:45 CDT 2010 J. Bruce Fields <bfields@citi.umich.edu> nfsd4: Move callback setup to callback queue Instead of creating the new rpc client from a regular server thread, set a flag, kick off a null call, and allow the null call to do the work of setting up the client on the callback workqueue. Use a spinlock to ensure the callback work gets a consistent view of the callback parameters. This allows, for example, changing the callback from contexts where sleeping is not allowed. I hope it will also keep the locking simple as we add more session and trunking features, by serializing most of the callback-specific work. This also closes a small race where the the new cb_ident could be used with an old connection (or vice-versa). Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
|
H A D | nfs4state.c | 6ff8da08 Fri Jun 04 19:04:45 CDT 2010 J. Bruce Fields <bfields@citi.umich.edu> nfsd4: Move callback setup to callback queue
Instead of creating the new rpc client from a regular server thread, set a flag, kick off a null call, and allow the null call to do the work of setting up the client on the callback workqueue.
Use a spinlock to ensure the callback work gets a consistent view of the callback parameters.
This allows, for example, changing the callback from contexts where sleeping is not allowed. I hope it will also keep the locking simple as we add more session and trunking features, by serializing most of the callback-specific work.
This also closes a small race where the the new cb_ident could be used with an old connection (or vice-versa).
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> 6ff8da08 Fri Jun 04 19:04:45 CDT 2010 J. Bruce Fields <bfields@citi.umich.edu> nfsd4: Move callback setup to callback queue Instead of creating the new rpc client from a regular server thread, set a flag, kick off a null call, and allow the null call to do the work of setting up the client on the callback workqueue. Use a spinlock to ensure the callback work gets a consistent view of the callback parameters. This allows, for example, changing the callback from contexts where sleeping is not allowed. I hope it will also keep the locking simple as we add more session and trunking features, by serializing most of the callback-specific work. This also closes a small race where the the new cb_ident could be used with an old connection (or vice-versa). Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
|