traced_probes: supply shmem size hints when connecting
The primary purpose of traced_probes is ftrace, which is
often relatively high bandwidth. Therefore it's better to
have a bigger shmem, and pack more data per tracing page.
Reminder that the first tracing session pins the shmem config
for the remainder of the traced<->traced_probes connection.
And the config-supplied hints take precedence. So these
values aren't guaranteed.
Bug: 146133021
Change-Id: I85ff6f6477c321a0c062be3b398933e7233867aa
diff --git a/test/end_to_end_integrationtest.cc b/test/end_to_end_integrationtest.cc
index 52947df..92e5416 100644
--- a/test/end_to_end_integrationtest.cc
+++ b/test/end_to_end_integrationtest.cc
@@ -414,7 +414,7 @@
const uint32_t kTestTimeoutMs = 30000;
TraceConfig trace_config;
- trace_config.add_buffers()->set_size_kb(16);
+ trace_config.add_buffers()->set_size_kb(32);
trace_config.set_duration_ms(kTestTimeoutMs);
auto* ds_config = trace_config.add_data_sources()->mutable_config();