[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH net] xen-netback: add the scenario which now beyond the range time_after_eq().

On 2013-10-18 0:41, Wei Liu wrote:
On Fri, Oct 18, 2013 at 12:38:12AM +0800, annie li wrote:
On 2013-10-17 17:26, Jan Beulich wrote:
Yes, the issue only can be  reproduced in 32-bit Dom0 (Beyond
MAX_ULONG/2 in 64-bit will need long long time)

I think the gap should be think all environment even now extending 480+.
if now fall in the gap,  one timer will be pending and replenish will be
in time.  Please run the attachment test program.
Not sure what this is supposed to tell me. I recognize that there
are overflow conditions not handled properly, but (a) I have a
hard time thinking of a sensible guest that sits idle for over 240
days (host uptime usually isn't even coming close to that due to
maintenance requirements) and (b) if there is such a sensible
guest, then I can't see why dealing with one being idle for over
480 days should be required too.

If the guest contains multiple NICs, that situation probably happens
when one NIC keeps idle and others work under load. BTW, how do you
get the 240?

I think Jan got this number with HZ=100. It take ~240 days for jiffies
to overflow in 32 bit machine when HZ=100.

If HZ is larger then the days would be less, for example, HZ=250, the days would be ~99. It is possible to hit overflow in environment where multiple NICs coexist and one NIC keeps idle all the time. Moreover, this patch does not extend to the days doubled, the timer is set with value based on next_credit.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.