[netstack] don't eagerly log any Cobalt events

...obviating the need for package `schedule` and eliminating one
potential flake in netstack_cobalt_integration_test, where the call to
connect() would notify newSocketNotifications, logging events to cobalt
before the corresponding call to accept() was observed.

These eager calls to LogCobaltEvents were useful when they made the
difference between netstack_cobalt_integration_test running in 60s vs
1s, but are less useful now, when the test takes ~240 seconds
regardless.

As a further simplification, we can remove the newSocketNotifications
chan entirely (and inline socketMetadata's type Netstack pointer into
its containing structs) at the small cost of only observing the current
socket count to update socketCountMax every 60 seconds (vs on every
socket creation).

Bug: 44207
Change-Id: I968aa7707bc76cd6db677552f2765eb94f6dc069
9 files changed
tree: 3c3a1d910d7167ea93dbee297f9194d15dabc052
  1. .clang-format
  2. .clang-tidy
  3. .dir-locals.el
  4. .gitattributes
  5. .gitignore
  6. .gn
  7. .style.yapf
  8. AUTHORS
  9. BUILD.gn
  10. CODE_OF_CONDUCT.md
  11. CONTRIBUTING.md
  12. LICENSE
  13. OWNERS
  14. PATENTS
  15. README.md
  16. boards/
  17. build/
  18. bundles/
  19. docs/
  20. examples/
  21. garnet/
  22. peridot/
  23. products/
  24. rustfmt.toml
  25. scripts/
  26. sdk/
  27. src/
  28. third_party/
  29. tools/
  30. zircon/
README.md

Fuchsia

Pink + Purple == Fuchsia (a new operating system)

What is Fuchsia?

Fuchsia is a modular, capability-based operating system. Fuchsia runs on modern 64-bit Intel and ARM processors.

Fuchsia is an open source project with a code of conduct that we expect everyone who interacts with the project to respect.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See fuchsia.dev.