From: David Vrabel <david.vrabel@citrix.com>
To: jianhai luan <jianhai.luan@oracle.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Jan Beulich <JBeulich@suse.com>,
<ian.campbell@citrix.com>, <xen-devel@lists.xenproject.org>,
<annie.li@oracle.com>, <netdev@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH net] xen-netback: add the scenario which now beyond the range time_after_eq().
Date: Thu, 17 Oct 2013 16:25:16 +0100 [thread overview]
Message-ID: <5260015C.2030100@citrix.com> (raw)
In-Reply-To: <526000F5.1090102@oracle.com>
On 17/10/13 16:23, jianhai luan wrote:
>
> On 2013-10-17 22:06, Wei Liu wrote:
>> On Thu, Oct 17, 2013 at 09:59:30PM +0800, jianhai luan wrote:
>> [...]
>>>>>>> If use time_after_eq64(), expire ,next_credit and other member
>>>>>>> will must
>>>>>>> be u64.
>>>>>> Yes, you'll need to store next_credit as a u64 in vif instead of
>>>>>> calculating it in tx_credit_exceeded from expires (which is only an
>>>>>> unsigned long).
>>>>> I know that. Even we use u64, time_after_eq() will also do wrong
>>>>> judge
>>>>> in theory (not in reality because need long long time).
>>>> If jiffies_64 has millisecond resolution that would be more than
>>>> 500,000,000 years.
>>> Yes, I agree the fact.
>>>>> I think the two better fixed way is below:
>>>>> - By time_before() to judge if now beyond MAX_ULONG/2
>>>> This is broken, so no.
>>> Where is broken? would you like to help me point it out.
>> I think David means you didn't actually fix the problem. Your solution is
>> merely a workaround.
>
> I have think about using u64, but more code need to be modified and
> that is not all. Key point is how to change the element of struct
> time_list (expires) and don't affect other thing?
I already suggested a way that didn't require changing the timer
structure -- calculate and store next_credit in advanced.
David
next prev parent reply other threads:[~2013-10-17 15:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 17:22 [PATCH net] xen-netback: add the scenario which now beyond the range time_after_eq() Jason Luan
2013-10-17 8:26 ` [Xen-devel] " Jan Beulich
2013-10-17 9:02 ` jianhai luan
2013-10-17 9:04 ` jianhai luan
2013-10-17 9:15 ` David Vrabel
2013-10-17 10:19 ` jianhai luan
2013-10-17 10:31 ` David Vrabel
2013-10-17 13:59 ` jianhai luan
2013-10-17 14:06 ` Wei Liu
2013-10-17 15:23 ` jianhai luan
2013-10-17 15:25 ` David Vrabel [this message]
2013-10-17 15:41 ` jianhai luan
2013-10-18 6:48 ` annie li
2013-10-17 9:26 ` Jan Beulich
2013-10-17 9:59 ` jianhai luan
2013-10-17 16:38 ` annie li
2013-10-17 16:41 ` Wei Liu
2013-10-18 1:59 ` annie li
2013-10-18 7:43 ` Jan Beulich
2013-10-18 8:14 ` annie li
2013-10-18 8:26 ` Jan Beulich
2013-10-18 8:40 ` David Laight
2013-10-18 11:24 ` Wei Liu
2013-10-23 8:02 ` jianhai luan
2013-10-23 16:07 ` Jan Beulich
2013-10-24 10:04 ` David Laight
2013-10-24 11:34 ` jianhai luan
2013-10-18 8:55 ` annie li
2013-10-17 16:21 ` annie li
2013-10-18 7:41 ` Jan Beulich
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=5260015C.2030100@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=annie.li@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=jianhai.luan@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).