mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julian Anastasov <ja@ssi.bg>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Simon Horman <horms@verge.net.au>, Arnd Bergmann <arnd@arndb.de>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Jiri Wiesner <jwiesner@suse.de>,
	netdev@vger.kernel.org, lvs-devel@vger.kernel.org,
	netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ipvs: use div_s64 for signed division
Date: Thu, 15 Dec 2022 21:01:59 +0200 (EET)	[thread overview]
Message-ID: <e1fea67-7425-f13d-e5bd-3d80d9a8afb8@ssi.bg> (raw)
In-Reply-To: <20221215170324.2579685-1-arnd@kernel.org>


	Hello,

On Thu, 15 Dec 2022, Arnd Bergmann wrote:

> From: Arnd Bergmann <arnd@arndb.de>
> 
> do_div() is only well-behaved for positive numbers, and now warns
> when the first argument is a an s64:
> 
> net/netfilter/ipvs/ip_vs_est.c: In function 'ip_vs_est_calc_limits':
> include/asm-generic/div64.h:222:35: error: comparison of distinct pointer types lacks a cast [-Werror]
>   222 |         (void)(((typeof((n)) *)0) == ((uint64_t *)0));  \
>       |                                   ^~
> net/netfilter/ipvs/ip_vs_est.c:694:17: note: in expansion of macro 'do_div'
>   694 |                 do_div(val, loops);

	net-next already contains fix for this warning
and changes val to u64.

> Convert to using the more appropriate div_s64(), which also
> simplifies the code a bit.
> 
> Fixes: 705dd3444081 ("ipvs: use kthreads for stats estimation")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>  net/netfilter/ipvs/ip_vs_est.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/net/netfilter/ipvs/ip_vs_est.c b/net/netfilter/ipvs/ip_vs_est.c
> index ce2a1549b304..dbc32f8cf1f9 100644
> --- a/net/netfilter/ipvs/ip_vs_est.c
> +++ b/net/netfilter/ipvs/ip_vs_est.c
> @@ -691,15 +691,13 @@ static int ip_vs_est_calc_limits(struct netns_ipvs *ipvs, int *chain_max)
>  		}
>  		if (diff >= NSEC_PER_SEC)
>  			continue;
> -		val = diff;
> -		do_div(val, loops);
> +		val = div_s64(diff, loops);

	On CONFIG_X86_32 both versions execute single divl
for our case but div_s64 is not inlined. I'm not expert in
this area but if you think div_u64 is more appropriate then
post another patch. Note that now val is u64 and
min_est is still s32 (can be u32).

>  		if (!min_est || val < min_est) {
>  			min_est = val;
>  			/* goal: 95usec per chain */
>  			val = 95 * NSEC_PER_USEC;
>  			if (val >= min_est) {
> -				do_div(val, min_est);
> -				max = (int)val;
> +				max = div_s64(val, min_est);
>  			} else {
>  				max = 1;
>  			}
> -- 
> 2.35.1

Regards

--
Julian Anastasov <ja@ssi.bg>


  reply	other threads:[~2022-12-15 19:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 17:03 Arnd Bergmann
2022-12-15 19:01 ` Julian Anastasov [this message]
2022-12-16 10:10   ` Pablo Neira Ayuso
2022-12-16 11:24     ` Arnd Bergmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e1fea67-7425-f13d-e5bd-3d80d9a8afb8@ssi.bg \
    --to=ja@ssi.bg \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=coreteam@netfilter.org \
    --cc=horms@verge.net.au \
    --cc=jwiesner@suse.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvs-devel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pablo@netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®