From: Vallish Vaidyeshwara <vallish@amazon.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: David Miller <davem@davemloft.net>, <shuah@kernel.org>,
"Linux Kernel Network Developers" <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Eduardo Valentin <eduval@amazon.com>, <anchalag@amazon.com>
Subject: Re: [PATCH RESEND 1/2] net: enable high resolution timer mode to timeout datagram sockets
Date: Tue, 22 Aug 2017 11:14:34 +0000 [thread overview]
Message-ID: <20170822111433.GA102755@amazon.com> (raw)
In-Reply-To: <CAM_iQpUxS91BGYU7FOwq65Ln_9bbMO1YRzA2+xJDYh399du7mQ@mail.gmail.com>
On Mon, Aug 21, 2017 at 01:10:34PM -0700, Cong Wang wrote:
> On Fri, Aug 18, 2017 at 11:44 AM, Vallish Vaidyeshwara
> <vallish@amazon.com> wrote:
> > - *timeo_p = schedule_timeout(*timeo_p);
> > + /* Wait using highres timer */
> > + expires = ktime_add_ns(ktime_get(), jiffies_to_nsecs(*timeo_p));
> > + pre_sched_time = jiffies;
> > + if (schedule_hrtimeout(&expires, HRTIMER_MODE_ABS))
>
Hello Cong,
> Does this work with MAX_SCHEDULE_TIMEOUT too??
>
Thanks for pointing out MAX_SCHEDULE_TIMEOUT. I have made minor change to
accommodate MAX_SCHEDULE_TIMEOUT and will send out next version of the patch
for review.
Thanks.
-Vallish
next prev parent reply other threads:[~2017-08-22 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 18:44 [PATCH RESEND 0/2] enable hires timer to timeout datagram socket Vallish Vaidyeshwara
2017-08-18 18:44 ` [PATCH RESEND 1/2] net: enable high resolution timer mode to timeout datagram sockets Vallish Vaidyeshwara
2017-08-21 20:10 ` Cong Wang
2017-08-22 11:14 ` Vallish Vaidyeshwara [this message]
2017-08-18 18:44 ` [PATCH RESEND 2/2] selftests/net: add test to verify datagram socket timeout Vallish Vaidyeshwara
2017-08-18 20:18 ` [PATCH RESEND 0/2] enable hires timer to timeout datagram socket Richard Cochran
2017-08-18 22:27 ` Vallish Vaidyeshwara
2017-08-19 6:21 ` Richard Cochran
2017-08-20 1:47 ` Vallish Vaidyeshwara
2017-08-21 18:22 ` Vallish Vaidyeshwara
2017-08-22 6:23 ` Richard Cochran
2017-08-22 11:17 ` Vallish Vaidyeshwara
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=20170822111433.GA102755@amazon.com \
--to=vallish@amazon.com \
--cc=anchalag@amazon.com \
--cc=davem@davemloft.net \
--cc=eduval@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.