[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87f182c6-82a3-d696-72e4-ddaa781a655b@cambridgegreys.com>
Date: Tue, 10 Dec 2019 07:14:40 +0000
From: Anton Ivanov <anton.ivanov@...bridgegreys.com>
To: Richard Weinberger <richard@....at>,
Brendan Higgins <brendanhiggins@...gle.com>
Cc: Johannes Berg <johannes.berg@...el.com>,
Jeff Dike <jdike@...toit.com>,
linux-um <linux-um@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
davidgow <davidgow@...gle.com>
Subject: Re: [RFC v1 1/2] um: drivers: remove support for UML_NET_PCAP
On 10/12/2019 00:02, Richard Weinberger wrote:
> ----- Ursprüngliche Mail -----
>> Von: "Brendan Higgins" <brendanhiggins@...gle.com>
>>> IMHO we should at least mark them as "obsolete" and start preparing to
>>> remove them.
>>
>> Alright, I will send a patch out which marks the other network drivers
>> as "obsolete".
>>
>> Clarification: Should I mark all UML network devices as "obsolete"
>> except for NET_VECTOR? Daemon and MCAST looked to me (I am not a
>> networking expert), like they might not be covered by vector.
>
> No. Why?
>
> Thanks,
> //richard
>
> _______________________________________________
> linux-um mailing list
> linux-um@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-um
>
At least pcap and vde are maintenance issues. They do not even build today.
Off the top of my head, daemon needs fixes to the switch - it has an
O(n) performance hit for n="number of ports" as well as a few other issues.
Tap has a fully functional replacement
Pcap has a fully functional replacement
mcast for 2 instances is functionally equivalent to running l2tp or gre
back-to-back.
IMHO we can start marking some of them as obsolete.
--
Anton R. Ivanov
Cambridgegreys Limited. Registered in England. Company Number 10273661
https://www.cambridgegreys.com/
Powered by blists - more mailing lists