[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3b091dc8-47ae-48c2-b7e9-ee3deea6d5e9@redhat.com>
Date: Thu, 23 Oct 2025 12:17:20 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Daniel Borkmann <daniel@...earbox.net>, netdev@...r.kernel.org
Cc: bpf@...r.kernel.org, kuba@...nel.org, davem@...emloft.net,
razor@...ckwall.org, willemb@...gle.com, sdf@...ichev.me,
john.fastabend@...il.com, martin.lau@...nel.org, jordan@...fe.io,
maciej.fijalkowski@...el.com, magnus.karlsson@...el.com, dw@...idwei.uk,
toke@...hat.com, yangzhenze@...edance.com, wangdongdong.6@...edance.com
Subject: Re: [PATCH net-next v3 02/15] net: Implement
netdev_nl_bind_queue_doit
On 10/20/25 6:23 PM, Daniel Borkmann wrote:
> + tmp_rxq = __netif_get_rx_queue(dst_dev, dst_dev->real_num_rx_queues - 1);
> + if (tmp_rxq->peer && tmp_rxq->peer->dev != src_dev) {
> + err = -EOPNOTSUPP;
> + NL_SET_ERR_MSG(info->extack,
> + "Binding multiple queues from difference source devices not supported");
> + goto err_unlock_src_dev;
> + }
Why checking a single queue on dst/virtual device? Should the above
check be repeated for all the real_num_rx_queues?
/P
Powered by blists - more mailing lists