From: Ido Yariv <ido@wizery.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Laight <David.Laight@ACULAB.COM>,
"David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
James Morris <jmorris@namei.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Patrick McHardy <kaber@trash.net>,
Nandita Dukkipati <nanditad@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ido Yariv <idox.yariv@intel.com>
Subject: Re: [PATCH] net: tcp: Fix a PTO timing granularity issue
Date: Wed, 27 May 2015 12:54:03 -0400 [thread overview]
Message-ID: <20150527165403.GC558@WorkStation.home> (raw)
In-Reply-To: <1432743816.4060.404.camel@edumazet-glaptop2.roam.corp.google.com>
Hi Eric,
On Wed, May 27, 2015 at 09:23:36AM -0700, Eric Dumazet wrote:
> On Wed, 2015-05-27 at 11:23 -0400, Ido Yariv wrote:
>
> > Signed-off-by: Ido Yariv <idox.yariv@intel.com>
> > ---
> > include/net/tcp.h | 9 +++++++++
> > net/ipv4/tcp_output.c | 2 +-
> > 2 files changed, 10 insertions(+), 1 deletion(-)
> >
> > diff --git a/include/net/tcp.h b/include/net/tcp.h
> > index 2bb2bad..86090b6 100644
> > --- a/include/net/tcp.h
> > +++ b/include/net/tcp.h
> > @@ -1751,4 +1751,13 @@ static inline void skb_set_tcp_pure_ack(struct sk_buff *skb)
> > skb->truesize = 2;
> > }
> >
> > +/* Convert msecs to jiffies, ensuring that the return value is always at least
> > + * 2. This can be used when setting tick-based timers to guarantee that they
> > + * won't expire right away.
> > + */
> > +static inline unsigned long tcp_safe_msecs_to_jiffies(const unsigned int m)
> > +{
> > + return max_t(u32, 2, msecs_to_jiffies(m));
> > +}
>
> Note that you can do slightly better if m is a constant at compile
> time ;)
>
> if (__builtin_constant_p(m) && m * 1000 >= 2 * HZ)
> return msecs_to_jiffies(m);
> return max_t(u32, 2, msecs_to_jiffies(m));
>
> Or something like that ?
That's a nice optimization ;)
However, I think that with Nicholas Mc Guire's recent changes to
msecs_to_jiffies (http://marc.info/?l=linux-kernel&m=143195210010666),
we should get this for free, no?
Cheers,
Ido.
next prev parent reply other threads:[~2015-05-27 16:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 14:25 [PATCH] net: tcp: Fix a PTO timing granularity issue Ido Yariv
2015-05-26 16:23 ` Eric Dumazet
2015-05-26 17:02 ` Ido Yariv
2015-05-26 17:13 ` Eric Dumazet
2015-05-26 17:55 ` Ido Yariv
2015-05-26 18:13 ` Eric Dumazet
2015-05-26 20:17 ` Ido Yariv
2015-05-27 11:36 ` David Laight
2015-05-27 13:41 ` Eric Dumazet
2015-05-27 14:40 ` Ido Yariv
2015-05-27 14:56 ` Eric Dumazet
2015-05-27 15:23 ` Ido Yariv
2015-05-27 16:23 ` Eric Dumazet
2015-05-27 16:54 ` Ido Yariv [this message]
2015-05-27 17:24 ` Eric Dumazet
2015-05-27 19:15 ` Ido Yariv
2015-05-28 4:37 ` Ido Yariv
2015-05-28 8:55 ` David Laight
2015-05-28 12:33 ` [PATCH v6] " Ido Yariv
2015-05-26 18:25 ` [PATCH] " Eric Dumazet
2015-05-26 19:39 ` Ido Yariv
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=20150527165403.GC558@WorkStation.home \
--to=ido@wizery.com \
--cc=David.Laight@ACULAB.COM \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=idox.yariv@intel.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=nanditad@google.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).