4

I am new to the async feature provided in the .NET framework

so in my understanding the benefit provided by the async keyword is that when thread call an async method, it can return in the await point and resume the run properly.

my question is after it return from that point, what is the thread doing ? can it be used to run other task items in Thread pool, if so, there must be still context switches ? if not, why not just spin there ?

===== so there will be other threads to take over the not finished part of the async function, how does this context switch happen, like where are those states stored? and how does another thread take those states

zinking
  • 5,561
  • 5
  • 49
  • 81
  • similar topics: http://stackoverflow.com/questions/7032290/what-happens-to-an-awaiting-thread-in-c-sharp-async-ctp?rq=1 – zinking Aug 22 '13 at 07:06

2 Answers2

5

When your code hits an await expression (assuming the awaitable was not completed synchronously), control returns to the calling method, as if you had written return;.
(it returns a Task<T> that the caller can use to await the completion of the async part)

The calling method will then continue execution until it returns (it will usually return immediately as it too awaits the returned task), and so on until it reaches the top of the (user-facing portion of the) call stack.

Once it hits the top of the call stack, that thread will do whatever it naturally does.

If it's a UI thread, it will return to the message loop, keeping the UI responsive.

If it's a ThreadPool thread (or an ASP.Net worker thread), it will return to the pool and wait (synchronously) for more work.

If it's a "raw" thread (the Main thread in a console app, or a new Thread(), it will terminate.

SLaks
  • 868,454
  • 176
  • 1,908
  • 1,964
  • and what about the remaining awaited work to be done? other threads will pick up. how does this switch process happen ? – zinking Aug 22 '13 at 03:04
  • @zinking: Using `Task.ContinueWith()`, which takes a callback that captures the current state in something like a closure. See http://msmvps.com/blogs/jon_skeet/archive/tags/Eduasync/default.aspx – SLaks Aug 22 '13 at 03:30
1

Yes, the thread returns and can do other work.

As for why not just spin there, because it can do other work. There is no point in forcing a thread to remain idle when it has the opportunity to do work.

If you do not care which thread will actually continue doing the work, then you can use Task.ConfigureAwait, like this:

await foo.DoSomethingAsync().ConfigureAwait(continueOnCapturedContext: false);
Karl Anderson
  • 34,606
  • 12
  • 65
  • 80
  • `ConfigureAwait()` has nothing to do with what the thread does next. – SLaks Aug 22 '13 at 02:41
  • @SLaks - I was coming at this from the standpoint of the overall process, not just the one particular thread. I realize that was the OP's original question, but the natural progression of thinking would usually lead to what happens to the rest of the work that needs to be done. – Karl Anderson Aug 22 '13 at 03:07