| Commit message (Collapse) | Author | Age |
|\
| |
| | |
Connection backoff interop test client and server
|
| |\ |
|
|\ \ \
| | |/
| |/|
| | |
| | | |
Conflicts:
Makefile
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
vsprojects/Grpc.mak
vsprojects/grpc.sln
vsprojects/grpc/grpc.vcxproj
vsprojects/grpc_cpp_plugin/grpc_cpp_plugin.vcxproj
vsprojects/grpc_csharp_ext/grpc_csharp_ext.vcxproj
vsprojects/grpc_csharp_plugin/grpc_csharp_plugin.vcxproj
vsprojects/grpc_objective_c_plugin/grpc_objective_c_plugin.vcxproj
vsprojects/grpc_python_plugin/grpc_python_plugin.vcxproj
vsprojects/grpc_ruby_plugin/grpc_ruby_plugin.vcxproj
vsprojects/grpc_unsecure/grpc_unsecure.vcxproj
|
| | |\ \
| | | | |
| | | | | |
Regenerating project files and massaging VS project files.
|
| | | | | |
|
|\ \ \ \ \
| | |/ / /
| |/| | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
tepid-tarantula
|
| | |_|/ /
| |/| | | |
|
| | |\ \ \
| | |/ / /
| |/| | | |
|
| | | | | |
|
| | |/ /
| |/| | |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently, if two threads call grpc_completion_queue_pluck on the same
completion queue for different tags, there is a 50% chance that we
deliver the completion wakeup to the wrong poller - forcing the correct
poller to wait until its polling times out before it can return an event
up to the application.
This change tweaks our polling interfaces so that we can indeed wake a
specific poller.
Nothing has been performance tuned yet. It's definitely sub-optimal in a
number of places. Wakeup file-descriptors should be recycled. We should
have a path that avoids calling poll() followed by epoll(). We can
probably live without it right at the second though.
This code will fail on Windows at least (I'll do that port when I'm in the office and have a Windows
machine).
|
| | |\
| |_|/
|/| | |
|
|\ \ \
| | | |
| | | | |
changes to allow VS solution/project generation and grpc.mak generation for c++ tests
|
|\ \ \ \
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | | |
sometimes-its-good-just-to-check-in-with-each-other
Conflicts:
src/core/iomgr/tcp_server_windows.c
|
| |\ \ \
| | | | |
| | | | | |
Dynamic-sized thread pool
|
| |\ \ \ \
| | | | | |
| | | | | | |
Fake transport security to private
|
| |_|_|_|/
|/| | | | |
|
| | | |\ \
| | |_|/ /
| |/| | | |
|
| | | | | |
|
|\| | | |
| | | | |
| | | | |
| | | | | |
sometimes-its-good-just-to-check-in-with-each-other
|
| |\ \ \ \
| | | | | |
| | | | | | |
Census record stats API
|
| | | |/ / |
|
| | | | | |
|
| | |/ /
| |/| | |
|
| | | | |
|
|\| | |
| | | |
| | | |
| | | | |
sometimes-its-good-just-to-check-in-with-each-other
|
| |\ \ \
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | | |
dgquintas-decompression
Conflicts:
Makefile
vsprojects/Grpc.mak
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
sometimes-its-good-just-to-check-in-with-each-other
|
| | |\ \ \
| | |/ / /
| |/| | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | |\ \ \ \ |
|
| | | |_|_|/
| | |/| | | |
|
| | | | | |\
| | | | |_|/
| | | |/| | |
|
|\ \ \ \ \ \
| | |_|/ / /
| |/| | | |
| | | | | | |
sometimes-its-good-just-to-check-in-with-each-other
|
| |\ \ \ \ \
| | | | | | |
| | | | | | | |
Make thread_pool.h a public header
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
appropriate
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Initial plumbing work; needs tests and more client_channel
implementation.
|
| | | | | |\
| |_|_|_|_|/
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
# Conflicts:
# Makefile
# include/grpc++/client_context.h
# include/grpc++/server_context.h
# src/cpp/client/client_context.cc
# src/cpp/server/server_context.cc
# vsprojects/Grpc.mak
|
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | | |
Rename ThreadPool -> FixedSizeThreadPool to allow for later introduction
of DynamicSizeThreadPool
|
| | | | | |
|
| | |\ \ \
| | |/ / /
| |/| | | |
|
| | |/ /
| | | |
| | | |
| | | |
| | | | |
Use it to validate that arithmetic on time types makes even some vague
kind of sense.
|
|\| | | |
|
| | | | |
|
| |\ \ \
| | | | |
| | | | | |
Make naming a little more consistent
|
| | | | |
| | | | |
| | | | |
| | | | | |
Tests not yet included.
|
| | |/ / |
|