| Commit message (Collapse) | Author | Age |
|\ |
|
| |
| |
| |
| | |
removed""
|
| | |
|
| |\
| | |
| | | |
All instances of exec_ctx being passed around in src/core removed
|
| | |
| | |
| | |
| | | |
varialbes in linux support MONOTONIC clock type)
|
| | | |
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
As a client of grpc I want to be aware of which threads are being
created by grpc, and giving them recognizable names makes it significantly
easier to diagnose what is going on in my programs.
This provides thread names for macOS and Linux. Adding support for other
platforms should be easy for platform specialists.
|
| |\
| |/
|/| |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Caching the start-time for GPR_CLOCK_REALTIME has been causing errors in
cases where the system time is changed (after caching the time). In such
cases, the following functions produce incorrect results (and are off by
how much ever the system time was changed)
grpc_millis_to_timespec() and grpc_timespec_to_millis_round_down()
This can cause problems especially when using the above functions to
get timer deadlines or completion queue timeouts.
(In the worst case scenarios, the timeouts/deadlines will always occur (if the
timeout inverval / deadline was less than the system change delta)
Ideally we should be reverting https://github.com/grpc/grpc/pull/11866
but since that is a large change (which introduced new APIs in
exec_ctx.cc), I am doing this change to effectively revert to the old
behavior (while still keeping the new APIs introduced in exec_ctx)
|
| | |\
| | |/
| |/| |
|
| | | |
|
| | |
| | |
| | |
| | | |
ExecCtx and some minor changes
|
| | | |
|
|\| | |
|
| |\ \ |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Lot's of manual work to make this merge work
|
| |/ / / |
|
| | | | |
|
| |/ / |
|
| | |\
| | |/
| |/| |
|
| | | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
src/core. exec_ctx is now a thread_local pointer of type ExecCtx instead of
grpc_exec_ctx which is initialized whenever ExecCtx is instantiated. ExecCtx
also keeps track of the previous exec_ctx so that nesting of exec_ctx is
allowed. This means that there is only one exec_ctx being used at any
time. Also, grpc_exec_ctx_finish is called in the destructor of the
object, and the previous exec_ctx is restored to avoid breaking current
functionality. The code still explicitly calls grpc_exec_ctx_finish
because removing all such instances causes the code to break.
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
Also converting to .cc
|