From: David Miller <davem@davemloft.net>
To: eduval@amazon.com
Cc: dwmw2@infradead.org, vallish@amazon.com, shuah@kernel.org,
richardcochran@gmail.com, xiyou.wangcong@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
anchalag@amazon.com, dwmw@amazon.com
Subject: Re: [PATCH v2 0/2] enable hires timer to timeout datagram socket
Date: Fri, 08 Sep 2017 14:44:58 -0700 (PDT) [thread overview]
Message-ID: <20170908.144458.596885875256619458.davem@davemloft.net> (raw)
In-Reply-To: <20170908185521.GA12340@u40b0340c692b58f6553c.ant.amazon.com>
From: Eduardo Valentin <eduval@amazon.com>
Date: Fri, 8 Sep 2017 11:55:21 -0700
> I agree. I would prefer to understand here what is the technical
> reason not to accept these patches other than "use other system
> calls".
I explained this, let me reiterate:
====================
And most importantly, letting the kernel have flexibility in this area
is absolutely essential for various forms of optimizations and power
savings.
====================
prev parent reply other threads:[~2017-09-08 21:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 0:10 Vallish Vaidyeshwara
2017-08-23 0:10 ` [PATCH v2 1/2] net: enable high resolution timer mode to timeout datagram sockets Vallish Vaidyeshwara
2017-08-23 0:10 ` [PATCH v2 2/2] selftests/net: add test to verify datagram socket timeout Vallish Vaidyeshwara
2017-08-23 4:30 ` [PATCH v2 0/2] enable hires timer to timeout datagram socket David Miller
2017-08-27 20:47 ` Vallish Vaidyeshwara
2017-08-29 11:16 ` David Laight
2017-09-08 17:04 ` Eduardo Valentin
2017-09-08 17:16 ` David Miller
2017-09-08 17:23 ` David Woodhouse
2017-09-08 17:26 ` David Miller
2017-09-08 18:55 ` Eduardo Valentin
2017-09-08 19:11 ` Eric Dumazet
2017-09-16 9:47 ` Thomas Gleixner
2017-09-20 22:48 ` Vallish Vaidyeshwara
2017-09-25 20:42 ` Thomas Gleixner
2017-09-08 21:44 ` David Miller [this message]
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=20170908.144458.596885875256619458.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=anchalag@amazon.com \
--cc=dwmw2@infradead.org \
--cc=dwmw@amazon.com \
--cc=eduval@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=shuah@kernel.org \
--cc=vallish@amazon.com \
--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 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®