[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <beb409e3-0c13-b817-dfa3-15792a341130@wanadoo.fr>
Date: Sun, 25 Jun 2023 22:14:49 +0200
From: Christophe JAILLET <christophe.jaillet@...adoo.fr>
To: Jakub Kicinski <kuba@...nel.org>,
Julia Lawall <Julia.Lawall@...ia.fr>
Cc: Veerasenareddy Burru <vburru@...vell.com>, keescook@...omium.org,
kernel-janitors@...r.kernel.org,
Abhijit Ayarekar <aayarekar@...vell.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, corbet@....net
Subject: Re: [PATCH 02/26] octeon_ep: use array_size
Le 25/06/2023 à 00:28, Jakub Kicinski a écrit :
> On Fri, 23 Jun 2023 23:14:33 +0200 Julia Lawall wrote:
>> - oq->buff_info = vzalloc(oq->max_count * OCTEP_OQ_RECVBUF_SIZE);
>> + oq->buff_info = vzalloc(array_size(oq->max_count, OCTEP_OQ_RECVBUF_SIZE));
>
> vcalloc seems to exist, is there a reason array_size() is preferred?
Hi,
just for your information, I've just sent [1].
CJ
[1]:
https://lore.kernel.org/all/3484e46180dd2cf05d993ff1a78b481bc2ad1f71.1687723931.git.christophe.jaillet@wanadoo.fr/
Powered by blists - more mailing lists