| commit | 2224c8e8bf9b9ffa9768247b8721b60b87ba28fe | [log] [tgz] |
|---|---|---|
| author | Zeling Feng <zeling@fuchsia.infra.roller.google.com> | Thu Feb 09 22:12:30 2023 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Feb 09 14:14:17 2023 -0800 |
| tree | e8c33212fedcc9f0cc2a86b0282786cf8219d302 | |
| parent | 1481c75879939aaa3346443c3e1a39d984ced0a9 [diff] |
[roll] Roll fuchsia [netstack3] Introduce MTU and ethernet::MaxFrameSize types The use of MTU in netstack3 is overloaded in that the network-device reports the maximum frame size instead of maximum transmit unit, so when installing a network device, we should can use the reported frame size but when an upper layer protocol queries about MTU info, we need to adjust accordingly. Giving MTU and frame size their own types instead of plain `u32`s to allow more clarity. Original-Fixed: 120974 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/797704 Original-Revision: ba6d83a882c43fc7e02782712dd3124e8cca7683 GitOrigin-RevId: f67e304f3bff02bdb7827f23f4d0ffc5c0a35bc0 Change-Id: I81431cce435cd5a9f5b1cfc753beab8dfdc68c9c
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.