diff options
| author | Tiwei Bie <tiwei.btw@antgroup.com> | 2025-05-03 13:17:10 +0800 |
|---|---|---|
| committer | Johannes Berg <johannes.berg@intel.com> | 2025-05-05 10:26:59 +0200 |
| commit | e619e18ed462bded8e8f12672a37053d39451404 (patch) | |
| tree | 1daf00ef33e3f941db0c43e3d84120e1da58a505 /Documentation/virt | |
| parent | b555cb66583e99158cfef8e91c025252cefae55b (diff) | |
| download | linux-e619e18ed462bded8e8f12672a37053d39451404.tar.gz linux-e619e18ed462bded8e8f12672a37053d39451404.tar.bz2 linux-e619e18ed462bded8e8f12672a37053d39451404.zip | |
um: Remove legacy network transport infrastructure
All legacy network transports have been removed. Vector transports
provide the same capabilities with significantly higher network
throughput. There is no reason to keep the legacy network transport
infrastructure anymore. Remove it to reduce the maintenance burden.
Signed-off-by: Tiwei Bie <tiwei.btw@antgroup.com>
Acked-By: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Link: https://patch.msgid.link/20250503051710.3286595-4-tiwei.btw@antgroup.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'Documentation/virt')
| -rw-r--r-- | Documentation/virt/uml/user_mode_linux_howto_v2.rst | 18 |
1 files changed, 6 insertions, 12 deletions
diff --git a/Documentation/virt/uml/user_mode_linux_howto_v2.rst b/Documentation/virt/uml/user_mode_linux_howto_v2.rst index 60f35ed748b2..c37e8e594d12 100644 --- a/Documentation/virt/uml/user_mode_linux_howto_v2.rst +++ b/Documentation/virt/uml/user_mode_linux_howto_v2.rst @@ -147,18 +147,12 @@ The image hostname will be set to the same as the host on which you are creating its image. It is a good idea to change that to avoid "Oh, bummer, I rebooted the wrong machine". -UML supports two classes of network devices - the older uml_net ones -which are scheduled for obsoletion. These are called ethX. It also -supports the newer vector IO devices which are significantly faster -and have support for some standard virtual network encapsulations like -Ethernet over GRE and Ethernet over L2TPv3. These are called vec0. - -Depending on which one is in use, ``/etc/network/interfaces`` will -need entries like:: - - # legacy UML network devices - auto eth0 - iface eth0 inet dhcp +UML supports vector I/O high performance network devices which have +support for some standard virtual network encapsulations like +Ethernet over GRE and Ethernet over L2TPv3. These are called vecX. + +When vector network devices are in use, ``/etc/network/interfaces`` +will need entries like:: # vector UML network devices auto vec0 |