memory-infra: Assemble dump results in service

services/resource_coordinator/public/interfaces/memory/memory_instrumentation.mojom

Index: services/resource_coordinator/public/interfaces/memory/memory_instrumentation.mojom
diff --git a/services/resource_coordinator/public/interfaces/memory/memory_instrumentation.mojom b/services/resource_coordinator/public/interfaces/memory/memory_instrumentation.mojom
index aa1a583efda3b000e943ae2936c3da2c8f2d1964..01c268cfecff2b9145ca03c8cd9c2a09f4a186ce 100644
--- a/services/resource_coordinator/public/interfaces/memory/memory_instrumentation.mojom
+++ b/services/resource_coordinator/public/interfaces/memory/memory_instrumentation.mojom
@@ -63,7 +63,9 @@ struct ProcessMemoryDump {
   OSMemDump os_dump;
   ChromeMemDump chrome_dump;
 
-  // TODO(hjd): add the computed Consistent Memory Metrics footprints here.
+  // This is roughly private, anonymous, non-discardable, resident or swapped
+  // memory. For more details, see https://goo.gl/3kPb9S.
+  uint32 private_footprint = 0;
 
   // This is used only in the use-case (1) and only on Linux/CrOS to get
   // around sandboxing. See crbug.com/461788 .