From: jianhai luan <jianhai.luan@oracle.com>
To: Jan Beulich <jbeulich@suse.com>,
David.Laight@ACULAB.COM, wei.liu2@citrix.com
Cc: david.vrabel@citrix.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, 24 Oct 2013 19:34:42 +0800 [thread overview]
Message-ID: <526905D2.4000003@oracle.com> (raw)
In-Reply-To: <5268025002000078000A56B5@nat28.tlf.novell.com>
>>> As I understand it, this is the idea of this patch -- to narrow down the
>>> timing window.
>> Jan, do you agree the idea or have better suggestion to me.
> As said before - I disagree (reducing a timing window is never a solution,
> only eliminating it is), and I pointed at the alternative (using 64-bit
> calculations) before.
Your mean is that add u64 member into struct xenvif or add static
variable to keep expire?
Jason
>
> Jan
>
next prev parent reply other threads:[~2013-10-24 11:35 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
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 [this message]
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=526905D2.4000003@oracle.com \
--to=jianhai.luan@oracle.com \
--cc=David.Laight@ACULAB.COM \
--cc=annie.li@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=jbeulich@suse.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).