* sleeping in async RPC task's rpc_call_ops
@ 2017-02-16 13:29 Benjamin Coddington
0 siblings, 0 replies; only message in thread
From: Benjamin Coddington @ 2017-02-16 13:29 UTC (permalink / raw)
To: Trond Myklebust; +Cc: Linux NFS Mailing List
Hi Trond,
I understand that it is considered bad form for async tasks to sleep, but I
do not understand why. Aren't async tasks running as scheduled work, and thus
allowed to sleep? My understanding is that a workqueue can detect a
sleeping worker and add another, if needed.
The context is that I am coming back around to the problem of having an
unlock wait for I/O to complete in the face of the waiting process catching
a fatal signal, and I wondering why we cannot (for v4) wait on the iocounter
in the async unlock's rpc_call_prepare.
This question is asked in leiu of sending detestable patches.
Ben
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2017-02-16 13:29 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-02-16 13:29 sleeping in async RPC task's rpc_call_ops Benjamin Coddington
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).