public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Vallish Vaidyeshwara <vallish@amazon.com>
Cc: davem@davemloft.net, shuah@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, eduval@amazon.com,
	anchalag@amazon.com, tglx@linutronix.de
Subject: Re: [PATCH RESEND 0/2] enable hires timer to timeout datagram socket
Date: Fri, 18 Aug 2017 22:18:54 +0200	[thread overview]
Message-ID: <20170818201854.xes246oviptinwvq@localhost> (raw)
In-Reply-To: <1503081850-10671-1-git-send-email-vallish@amazon.com>

On Fri, Aug 18, 2017 at 06:44:08PM +0000, Vallish Vaidyeshwara wrote:
> There has been a behavior change in 4.9 kernel with refactoring of Kernel
> timer wheel in 4.8. We have a use case wherein our datagram socket
> application is sensitive to socket timeout including long timeouts.
> 
> One of the test runs with a timeout value of 180 seconds timed out at
> 190 seconds.

So the whole premise of the new timer wheel is that long timeouts need
not be very accurate.

> Patch 1: Has core code change of enabling hires timer to timeout datagram
> 	 socket on AF_UNIX and AF_INET domain

Using hrtimers will hurt performance for most applications.  Can you
please explain your use case and why is it so important?

Thanks,
Richard

  parent reply	other threads:[~2017-08-18 20:19 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
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 ` Richard Cochran [this message]
2017-08-18 22:27   ` [PATCH RESEND 0/2] enable hires timer to timeout datagram socket 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=20170818201854.xes246oviptinwvq@localhost \
    --to=richardcochran@gmail.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=tglx@linutronix.de \
    --cc=vallish@amazon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox