[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACGkMEsag0xGcGxPnaou3wiO8iJBL4Pxecj6Vd-KEN7otQX5aQ@mail.gmail.com>
Date: Mon, 24 Oct 2022 10:01:18 +0800
From: Jason Wang <jasowang@...hat.com>
To: Angus Chen <angus.chen@...uarmicro.com>
Cc: mst@...hat.com, virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, lingshan.zhu@...el.com
Subject: Re: [PATCH v2] vDPA: rename get_vq_num_max to get_vq_size_max
On Mon, Oct 24, 2022 at 9:56 AM Angus Chen <angus.chen@...uarmicro.com> wrote:
>
> The get_vq_num_max of vdpa_config_ops is mean get the max size of vq,not
> the max number of vq,it is kind of confused,rename it.
> And get_vq_num_min rename to get_vq_size_min,
> set_vq_num rename to set_vq_size,
> rename implement of this ops also.
>
> Signed-off-by: Angus Chen <angus.chen@...uarmicro.com>
> ---
Not a native sparker. But num_max came from virtqueue structure:
/*
...
* @num_max: the maximum number of elements supported by the device.
...
*/
struct virtqueue {
...
unsigned int num_max;
...
};
Thanks
Powered by blists - more mailing lists