netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Varun Chandramohan <varunc@linux.vnet.ibm.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kaber@trash.net,
	socketcan@hartkopp.net, krkumar2@in.ibm.com, varuncha@in.ibm.com
Subject: Re: [PATCH 2/4 - rev2] Add new timeval_to_sec function
Date: Tue, 21 Aug 2007 09:09:33 +0530	[thread overview]
Message-ID: <46CA5E75.9050904@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070820075325.43bd8f60@freepuppy.rosehill.hemminger.net>

Stephen Hemminger wrote:
> On Mon, 20 Aug 2007 13:45:36 +0530
> Varun Chandramohan <varunc@linux.vnet.ibm.com> wrote:
>
>   
>> A new function for converting timeval to time_t is added in time.h. Its a common function used in different
>> places.
>>
>> Signed-off-by: Varun Chandramohan <varunc@linux.vnet.ibm.com>
>> ---
>>  include/linux/time.h |   12 ++++++++++++
>>  1 files changed, 12 insertions(+), 0 deletions(-)
>>
>> diff --git a/include/linux/time.h b/include/linux/time.h
>> index 6a5f503..1faf65c 100644
>> --- a/include/linux/time.h
>> +++ b/include/linux/time.h
>> @@ -149,6 +149,18 @@ static inline s64 timeval_to_ns(const st
>>  }
>>  
>>  /**
>> + * timeval_to_sec - Convert timeval to seconds
>> + * @tv:         pointer to the timeval variable to be converted
>> + *
>> + * Returns the seconds representation of timeval parameter.
>> + * Note : Here we round up the value. We dont need accuracy.
>> + */
>> +static inline time_t timeval_to_sec(const struct timeval *tv)
>> +{
>> +	return (tv->tv_sec + (tv->tv_usec ? 1 : 0));
>> +}
>> +
>>     
>
> Why roundup? Unless there is a requirement in the standard, please just
> use the timeval seconds. In which case the inline is unneeded.
>
>
>   
Thanks for the reply stephen. As you might be aware that this discussion
took place sometime ago when i posted my first patch set.
Initially it was like this:

return (tv->tv_sec + (tv->tv_usec + 500000)/1000000);
Then i got some comments from patrick and oliver. They wanted me to
round it up.

So what about rounding up with

return (tv->tv_sec + (tv->tv_usec + 999999)/1000000);


Then on second revision the above was changed to

return tv->tv_sec + (tv->tv_usec ? 1 : 0);

as it would be much faster. Since the timeval is meant for stats purpose
we decided not really bother about accuracy. My initial patch actually
took only sec value into account, but i was adviced to round up usec to
give a better o/p. Is that ok??? Or you still think we should consider
only secs?

Regards,
Varun

  reply	other threads:[~2007-08-21  3:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20  8:15 [PATCH 2/4 - rev2] Add new timeval_to_sec function Varun Chandramohan
2007-08-20 14:53 ` Stephen Hemminger
2007-08-21  3:39   ` Varun Chandramohan [this message]
2007-08-21  9:58     ` Bob Beers
2007-08-21 11:09       ` Varun Chandramohan

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=46CA5E75.9050904@linux.vnet.ibm.com \
    --to=varunc@linux.vnet.ibm.com \
    --cc=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=krkumar2@in.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.org \
    --cc=socketcan@hartkopp.net \
    --cc=varuncha@in.ibm.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;
as well as URLs for NNTP newsgroup(s).