From: Ed Cashin <ed.cashin@acm.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: y2038@lists.linaro.org,
Tina Ruchandani <ruchandani.tina@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Y2038] [PATCH] aoe: Use 64-bit timestamp in frame
Date: Wed, 13 May 2015 20:47:01 -0400 [thread overview]
Message-ID: <5553F085.8090004@acm.org> (raw)
In-Reply-To: <8535976.TAdvFKB2bQ@wuerfel>
On 05/13/2015 04:04 AM, Arnd Bergmann wrote:
...
> Shall we do the ktime_get_us() approach then? It still requires a
> 32-bit division like do_gettimeofday(), so it will not be as efficient
> as the shifted nanoseconds.
It's no worse, though, right? So I think it's a good transition. Further
optimization could be attempted in an experimental branch at some
point for easy testing.
> As for the aoe_deadsecs computation, converting the aoe_deadsec module
> parameter into scaled nanoseconds can be done at module load time, and
> that way you also save the integer division you currently do for each
> frame in rexmit_timer() to turn the microseconds into seconds. Arnd
That's true, but the "secs" in the identifier stands for "seconds". It would
be misleading to have something called seconds be scaled nanoseconds.
And we could just use another variable if it weren't for the fact that this
module parameter is exposed through sysfs and can be changed through
that mechanism at any time.
--
Ed
next prev parent reply other threads:[~2015-05-14 0:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 2:35 [PATCH] aoe: Use 64-bit timestamp in frame Tina Ruchandani
2015-05-11 15:38 ` Arnd Bergmann
2015-05-11 15:59 ` Ed Cashin
2015-05-12 1:00 ` Ed Cashin
2015-05-12 9:44 ` Arnd Bergmann
2015-05-12 11:14 ` [Y2038] " Arnd Bergmann
2015-05-13 1:23 ` Ed Cashin
2015-05-13 8:04 ` Arnd Bergmann
2015-05-14 0:47 ` Ed Cashin [this message]
2015-05-12 11:21 ` Ed Cashin
2015-05-13 1:26 ` Ed Cashin
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=5553F085.8090004@acm.org \
--to=ed.cashin@acm.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ruchandani.tina@gmail.com \
--cc=y2038@lists.linaro.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