Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Craig Tiller	2d00d50c59	[event_engine] Improve scaling in threadpool (#31234 ) * fixes * Automated change: Fix sanity tests * fix * fix * fix * fix * fixes * fixes * fix * fix-win * fix iwyu * fix * fix Co-authored-by: ctiller <ctiller@users.noreply.github.com>	2 years ago
AJ Heller	c0e5e35c7a	Replace EventEngine::Promise with grpc_core::Notification (#31027 ) * Replace EventEngine::Promise with grpc_core::Notification * remove promise.h * Automated change: Fix sanity tests * fix windows * fix iocp * fix client_test Co-authored-by: drfloob <drfloob@users.noreply.github.com>	2 years ago
Vignesh Babu	4e7f0e1eac	Update to the event engine poller interface (#30828 ) * change poller interface for posix event engine * update event_poller_posix_test * windows ee changes * update comment * remove unused deps * review comments * fix build issue * fix sanity * fix build * Automated change: Fix sanity tests * review comments * remove unused dep * sanity * fix typo and address review comments * review comments * Automated change: Fix sanity tests * fix typo in comment Co-authored-by: Vignesh2208 <Vignesh2208@users.noreply.github.com>	2 years ago
Craig Tiller	14c3839749	[event_engine] More robust ee::Promise<> implementation (#30977 ) * fix promise * iocp * iwyu * Automated change: Fix sanity tests Co-authored-by: ctiller <ctiller@users.noreply.github.com>	2 years ago
Craig Tiller	266d41d4d6	[fixit] Scale down large tests (#30674 ) We have many tests that create 100 threads or more, and mounting evidence that this is harmful to our CI environment. When the original code for many of these tests was written we ran our tests under run_tests, which had explicit handling for tracking the number of threads each test needed and making sure that we weren't over subscribing the test runner. Bazel has no such facility (and the facility in run_tests has since been removed) and so we need to adjust. This PR adjusts down a single test and is part of a series so that we can review and roll back easily if required.	2 years ago
AJ Heller	c752a6b25e	Reland: Windows IOCP implementation for the WindowsEventEngine (#30480 ) Reverts #30466, relanding #30389. Requires a cherrypick.	2 years ago
AJ Heller	9d4e0e17fe	Revert "Windows IOCP implementation for the WindowsEventEngine (#30389 )" (#30466 ) This reverts commit `52402afdd4`.	2 years ago
AJ Heller	52402afdd4	Windows IOCP implementation for the WindowsEventEngine (#30389 ) This is a partial fork of the windows iomgr code - specifically the IOCP and Socket pieces - with some improved architecture and encapsulation. And the start of a WindowsEventEngine. Once this code is used in a gRPC TCP context, I imagine a few issues will shake out. Also, getting sanitizers set up with MSVC will take a bit of work (see a commit referencing abseil and MSVC bugs to hack around). I forked the IomgrEventEngine's posix poller interfaces in the hope of negotiating compatibility between the platforms, but the interfaces diverged a fair bit, and I'm doubtful we'll be able to use these "pollers" generically in the same TCP code. Reunification might not happen, and that's probably fine, we'll see how similar the TCP code looks once it's fleshed out. I also extracted the IomgrEventEngine's timer piece into a separate component, usable by both engines.	2 years ago