;
linux-ker...@vger.kernel.org
Subject: Re: [PATCH RESEND V2 3/3] vdpa/mlx5: Use consistent RQT size
On Tue, Mar 29, 2022 at 12:21:09PM +0800, Jason Wang wrote:
From: Eli Cohen
The current code evaluates RQT size based on the configured number of
virtqueues. This can raise an issue
: Re: [PATCH RESEND V2 3/3] vdpa/mlx5: Use consistent RQT size
On Tue, Mar 29, 2022 at 12:21:09PM +0800, Jason Wang wrote:
From: Eli Cohen
The current code evaluates RQT size based on the configured number of
virtqueues. This can raise an issue in the following scenario:
Assume MQ was negotiated
; > Subject: Re: [PATCH RESEND V2 3/3] vdpa/mlx5: Use consistent RQT size
> >
> > On Tue, Mar 29, 2022 at 12:21:09PM +0800, Jason Wang wrote:
> > > From: Eli Cohen
> > >
> > > The current code evaluates RQT size based on the configured nu
On Tue, Mar 29, 2022 at 12:21:09PM +0800, Jason Wang wrote:
> From: Eli Cohen
>
> The current code evaluates RQT size based on the configured number of
> virtqueues. This can raise an issue in the following scenario:
>
> Assume MQ was negotiated.
> 1. mlx5_vdpa_set_map() gets called.
> 2.
From: Eli Cohen
The current code evaluates RQT size based on the configured number of
virtqueues. This can raise an issue in the following scenario:
Assume MQ was negotiated.
1. mlx5_vdpa_set_map() gets called.
2. handle_ctrl_mq() is called setting cur_num_vqs to some value, lower
than the
