[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241216182001.557e2c19@kernel.org>
Date: Mon, 16 Dec 2024 18:20:01 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Anna Emese Nyiri <annaemesenyiri@...il.com>
Cc: netdev@...r.kernel.org, fejes@....elte.hu, edumazet@...gle.com,
pabeni@...hat.com, willemb@...gle.com, idosch@...sch.org, horms@...nel.org,
dsahern@...nel.org, linux-can@...r.kernel.org, socketcan@...tkopp.net,
mkl@...gutronix.de, linux-kselftest@...r.kernel.org, shuah@...nel.org,
tsbogend@...ha.franken.de, kaiyuanz@...gle.com,
James.Bottomley@...senPartnership.com, richard.henderson@...aro.org,
arnd@...db.de, almasrymina@...gle.com, asml.silence@...il.com,
linux-mips@...r.kernel.org, andreas@...sler.com, mattst88@...il.com,
kerneljasonxing@...il.com, sparclinux@...r.kernel.org,
linux-alpha@...r.kernel.org, linux-arch@...r.kernel.org, deller@....de,
vadim.fedorenko@...ux.dev, linux-parisc@...r.kernel.org
Subject: Re: [PATCH net-next v7 4/4] sock: Introduce SO_RCVPRIORITY socket
option
On Fri, 13 Dec 2024 09:44:57 +0100 Anna Emese Nyiri wrote:
> Add new socket option, SO_RCVPRIORITY, to include SO_PRIORITY in the
> ancillary data returned by recvmsg().
> This is analogous to the existing support for SO_RCVMARK,
> as implemented in commit <6fd1d51cfa253>
> ("net: SO_RCVMARK socket option for SO_MARK with recvmsg()").
Could you follow up with a test? The functionality is pretty
straightforward but it'd nonetheless be good to exercise it,
even if it's a trivial C program which sends a UDP packet to
itself over loopback?
Powered by blists - more mailing lists