[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6845547-59e8-4b4e-9a8d-926bad117410@openvpn.net>
Date: Tue, 5 Mar 2024 16:52:59 +0100
From: Antonio Quartulli <antonio@...nvpn.net>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, Jakub Kicinski <kuba@...nel.org>,
Sergey Ryazanov <ryazanov.s.a@...il.com>, Paolo Abeni <pabeni@...hat.com>,
Eric Dumazet <edumazet@...gle.com>
Subject: Re: [PATCH net-next v2 06/22] ovpn: introduce the ovpn_peer object
On 04/03/2024 22:52, Andrew Lunn wrote:
> On Mon, Mar 04, 2024 at 04:08:57PM +0100, Antonio Quartulli wrote:
>> An ovpn_peer object holds the whole status of a remote peer
>> (regardless whether it is a server or a client).
>>
>> This includes status for crypto, tx/rx buffers, napi, etc.
>>
>> Only support for one peer is introduced (P2P mode).
>> Multi peer support is introduced with a later patch.
>>
>> Along with the ovpn_peer, also the ovpn_bind object is introcued
>
> introduced
>
> > +/* Translate skb->protocol value to AF_INET or AF_INET6 */
>> +static inline unsigned short skb_protocol_to_family(const struct sk_buff *skb)
>> +{
>> + switch (skb->protocol) {
>> + case htons(ETH_P_IP):
>> + return AF_INET;
>> + case htons(ETH_P_IPV6):
>> + return AF_INET6;
>> + default:
>> + return 0;
>
> That feels like the sort of thing which should already exist
> somewhere. But a quick search did not find it...
Do you think we have a similar pattern in other drivers?
If so, it may be worth implementing this functionality in a kernel header.
Regards,
>
> Andrew
--
Antonio Quartulli
OpenVPN Inc.
Powered by blists - more mailing lists