Skip to content

Commit e619e18

Browse files
btw616jmberg-intel
authored andcommitted
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 <[email protected]> Acked-By: Anton Ivanov <[email protected]> Link: https://patch.msgid.link/[email protected] Signed-off-by: Johannes Berg <[email protected]>
1 parent b555cb6 commit e619e18

File tree

9 files changed

+11
-1319
lines changed

9 files changed

+11
-1319
lines changed

Documentation/virt/uml/user_mode_linux_howto_v2.rst

Lines changed: 6 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -147,18 +147,12 @@ The image hostname will be set to the same as the host on which you
147147
are creating its image. It is a good idea to change that to avoid
148148
"Oh, bummer, I rebooted the wrong machine".
149149

150-
UML supports two classes of network devices - the older uml_net ones
151-
which are scheduled for obsoletion. These are called ethX. It also
152-
supports the newer vector IO devices which are significantly faster
153-
and have support for some standard virtual network encapsulations like
154-
Ethernet over GRE and Ethernet over L2TPv3. These are called vec0.
155-
156-
Depending on which one is in use, ``/etc/network/interfaces`` will
157-
need entries like::
158-
159-
# legacy UML network devices
160-
auto eth0
161-
iface eth0 inet dhcp
150+
UML supports vector I/O high performance network devices which have
151+
support for some standard virtual network encapsulations like
152+
Ethernet over GRE and Ethernet over L2TPv3. These are called vecX.
153+
154+
When vector network devices are in use, ``/etc/network/interfaces``
155+
will need entries like::
162156

163157
# vector UML network devices
164158
auto vec0

arch/um/configs/i386_defconfig

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,6 @@ CONFIG_PACKET=y
5252
CONFIG_UNIX=y
5353
CONFIG_INET=y
5454
# CONFIG_IPV6 is not set
55-
CONFIG_UML_NET=y
5655
CONFIG_EXT4_FS=y
5756
CONFIG_QUOTA=y
5857
CONFIG_AUTOFS_FS=m

arch/um/configs/x86_64_defconfig

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,6 @@ CONFIG_PACKET=y
5151
CONFIG_UNIX=y
5252
CONFIG_INET=y
5353
# CONFIG_IPV6 is not set
54-
CONFIG_UML_NET=y
5554
CONFIG_EXT4_FS=y
5655
CONFIG_QUOTA=y
5756
CONFIG_AUTOFS_FS=m

arch/um/drivers/Kconfig

Lines changed: 5 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -124,35 +124,18 @@ endmenu
124124
menu "UML Network Devices"
125125
depends on NET
126126

127-
# UML virtual driver
128-
config UML_NET
129-
bool "Virtual network device"
130-
help
131-
While the User-Mode port cannot directly talk to any physical
132-
hardware devices, this choice and the following transport options
133-
provide one or more virtual network devices through which the UML
134-
kernels can talk to each other, the host, and with the host's help,
135-
machines on the outside world.
136-
137-
For more information, including explanations of the networking and
138-
sample configurations, see
139-
<http://user-mode-linux.sourceforge.net/old/networking.html>.
140-
141-
If you'd like to be able to enable networking in the User-Mode
142-
linux environment, say Y; otherwise say N. Note that you must
143-
enable at least one of the following transport options to actually
144-
make use of UML networking.
145-
146127
config UML_NET_VECTOR
147128
bool "Vector I/O high performance network devices"
148129
select MAY_HAVE_RUNTIME_DEPS
149130
help
150131
This User-Mode Linux network driver uses multi-message send
151132
and receive functions. The host running the UML guest must have
152133
a linux kernel version above 3.0 and a libc version > 2.13.
153-
This driver provides tap, raw, gre and l2tpv3 network transports
154-
with up to 4 times higher network throughput than the UML network
155-
drivers.
134+
This driver provides tap, raw, gre and l2tpv3 network transports.
135+
136+
For more information, including explanations of the networking
137+
and sample configurations, see
138+
<file:Documentation/virt/uml/user_mode_linux_howto_v2.rst>.
156139

157140
endmenu
158141

arch/um/drivers/Makefile

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@
77
# in to pcap.o
88

99
vector-objs := vector_kern.o vector_user.o vector_transports.o
10-
net-objs := net_kern.o net_user.o
1110
mconsole-objs := mconsole_kern.o mconsole_user.o
1211
hostaudio-objs := hostaudio_kern.o
1312
ubd-objs := ubd_kern.o ubd_user.o
@@ -29,7 +28,6 @@ obj-$(CONFIG_SSL) += ssl.o
2928
obj-$(CONFIG_STDERR_CONSOLE) += stderr_console.o
3029

3130
obj-$(CONFIG_UML_NET_VECTOR) += vector.o
32-
obj-$(CONFIG_UML_NET) += net.o
3331
obj-$(CONFIG_MCONSOLE) += mconsole.o
3432
obj-$(CONFIG_MMAPPER) += mmapper_kern.o
3533
obj-$(CONFIG_BLK_DEV_UBD) += ubd.o

0 commit comments

Comments
 (0)