From: 'Christoph Paasch' <christoph.paasch@uclouvain.be>
To: David Laight <David.Laight@ACULAB.COM>
Cc: David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Doug Leith <doug.leith@nuim.ie>,
Neal Cardwell <ncardwell@google.com>
Subject: Re: [PATCH net] tcp: Fix integer-overflows in TCP vegas
Date: Wed, 23 Jul 2014 13:18:02 +0200 [thread overview]
Message-ID: <20140723111802.GB6387@cpaasch-mac> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1727BEDC@AcuExch.aculab.com>
On 23/07/14 - 08:38:30, David Laight wrote:
> From: Of Christoph Paasch
> > In vegas we do a multiplication of the cwnd and the rtt. This
> > may overflow and thus their result is stored in a u64. However, we first
> > need to cast the cwnd so that actually 64-bit arithmetic is done.
> >
> > Cc: Doug Leith <doug.leith@nuim.ie>
> > Fixes: 8d3a564da34e (tcp: tcp_vegas cong avoid fix)
> > Signed-off-by: Christoph Paasch <christoph.paasch@uclouvain.be>
> > ---
> > net/ipv4/tcp_vegas.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/net/ipv4/tcp_vegas.c b/net/ipv4/tcp_vegas.c
> > index 9a5e05f27f4f..6a4bdea2a0fb 100644
> > --- a/net/ipv4/tcp_vegas.c
> > +++ b/net/ipv4/tcp_vegas.c
> > @@ -218,7 +218,7 @@ static void tcp_vegas_cong_avoid(struct sock *sk, u32 ack, u32 acked)
> > * This is:
> > * (actual rate in segments) * baseRTT
> > */
> > - target_cwnd = tp->snd_cwnd * vegas->baseRTT / rtt;
> > + target_cwnd = (u64)tp->snd_cwnd * vegas->baseRTT / rtt;
>
> Won't that add a reference to the 64bit divide function?
Yes, you are right. Sorry... (that's what happens if one only tests on a
64-bit system... :S )
> If snd_cwnd is small then maybe:
> target_cwnd = (256u * vegas->baseRTT) / rtt * tp->snd_cwnd / 256u;
> If large I think low bits are always zero so:
> target_cwnd = (256u * vegas->baseRTT) / rtt * (tp->snd_cwnd / 256u);
> Possibly with a different power of 2...
I realize that baseRTT is always smaller or equal to rtt.
Thus, target_cwnd will always be <= snd_cwnd. So, I think target_cwnd does not
need to be a u64.
I think that it would be safer to do do_div(). That way no matter what the
difference between baseRTT and rtt, we always set the correct value. Otherwise
we might set target_cwnd to 0, while with a do_div it would not.
But a do_div might be more costly than your solution.
What do you (or others) think?
Cheers,
Christoph
next prev parent reply other threads:[~2014-07-23 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 21:36 [PATCH net] tcp: Fix integer-overflows in TCP vegas Christoph Paasch
2014-07-22 21:58 ` Neal Cardwell
2014-07-23 8:38 ` David Laight
2014-07-23 11:18 ` 'Christoph Paasch' [this message]
2014-07-23 21:53 ` David Miller
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=20140723111802.GB6387@cpaasch-mac \
--to=christoph.paasch@uclouvain.be \
--cc=David.Laight@ACULAB.COM \
--cc=davem@davemloft.net \
--cc=doug.leith@nuim.ie \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.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