On 2013年09月16日 17:01, Thomas Gleixner wrote:
On Mon, 16 Sep 2013, Fan Du wrote:
On 2013年09月13日 22:32, Thomas Gleixner wrote:
On Fri, 13 Sep 2013, Fan Du wrote:
(2) What I have been bugging you around here for this long time is really
the
second
problem, I'm sorry I didn't make it
On 2013年09月16日 17:01, Thomas Gleixner wrote:
On Mon, 16 Sep 2013, Fan Du wrote:
On 2013年09月13日 22:32, Thomas Gleixner wrote:
On Fri, 13 Sep 2013, Fan Du wrote:
(2) What I have been bugging you around here for this long time is really
the
second
problem, I'm sorry I didn't make it
On Mon, 16 Sep 2013, Fan Du wrote:
> On 2013年09月13日 22:32, Thomas Gleixner wrote:
> > On Fri, 13 Sep 2013, Fan Du wrote:
> > > (2) What I have been bugging you around here for this long time is really
> > > the
> > > second
> > > problem, I'm sorry I didn't make it clearly to you and others,
On Mon, 16 Sep 2013, Fan Du wrote:
On 2013年09月13日 22:32, Thomas Gleixner wrote:
On Fri, 13 Sep 2013, Fan Du wrote:
(2) What I have been bugging you around here for this long time is really
the
second
problem, I'm sorry I didn't make it clearly to you and others, which
is
Hi, Thomas
On 2013年09月13日 22:32, Thomas Gleixner wrote:
On Fri, 13 Sep 2013, Fan Du wrote:
(2) What I have been bugging you around here for this long time is really the
second
problem, I'm sorry I didn't make it clearly to you and others, which is
below:
Why using wall clock time to
Hi, Thomas
On 2013年09月13日 22:32, Thomas Gleixner wrote:
On Fri, 13 Sep 2013, Fan Du wrote:
(2) What I have been bugging you around here for this long time is really the
second
problem, I'm sorry I didn't make it clearly to you and others, which is
below:
Why using wall clock time to
On Fri, 13 Sep 2013, Fan Du wrote:
> (2) What I have been bugging you around here for this long time is really the
> second
> problem, I'm sorry I didn't make it clearly to you and others, which is
> below:
>
> Why using wall clock time to calculate soft/hard IPsec events when
>
On Fri, 13 Sep 2013, Fan Du wrote:
(2) What I have been bugging you around here for this long time is really the
second
problem, I'm sorry I didn't make it clearly to you and others, which is
below:
Why using wall clock time to calculate soft/hard IPsec events when
xfrm_state timer
Hi Dave/Thomas
On 2013年09月13日 01:32, David Miller wrote:
From: Thomas Gleixner
Date: Thu, 12 Sep 2013 16:43:37 +0200 (CEST)
So what about going back to timer_list timers and simply utilize
register_pm_notifier(), which will tell you that the system resumed?
The thing to understand is that
On Thu, 12 Sep 2013, John Stultz wrote:
> On Thu, Sep 12, 2013 at 6:44 AM, Herbert Xu
> wrote:
> > On Thu, Sep 12, 2013 at 03:21:24PM +0200, Thomas Gleixner wrote:
> >>
> >> > (3): http://www.spinics.net/lists/netdev/msg245169.html
> >>
> >> Thanks for the explanation so far.
> >>
> >> What's
On Thu, Sep 12, 2013 at 6:44 AM, Herbert Xu wrote:
> On Thu, Sep 12, 2013 at 03:21:24PM +0200, Thomas Gleixner wrote:
>>
>> > (3): http://www.spinics.net/lists/netdev/msg245169.html
>>
>> Thanks for the explanation so far.
>>
>> What's still unclear to me is why these timeouts are bound to wall
On Thu, 12 Sep 2013, David Miller wrote:
> From: Thomas Gleixner
> Date: Thu, 12 Sep 2013 16:43:37 +0200 (CEST)
>
> > So what about going back to timer_list timers and simply utilize
> > register_pm_notifier(), which will tell you that the system resumed?
>
> The thing to understand is that
From: Thomas Gleixner
Date: Thu, 12 Sep 2013 16:43:37 +0200 (CEST)
> So what about going back to timer_list timers and simply utilize
> register_pm_notifier(), which will tell you that the system resumed?
The thing to understand is that there are two timeouts for an IPSEC
rule, a soft and a
On Thu, 12 Sep 2013, Herbert Xu wrote:
> On Thu, Sep 12, 2013 at 03:21:24PM +0200, Thomas Gleixner wrote:
> >
> > > (3): http://www.spinics.net/lists/netdev/msg245169.html
> >
> > Thanks for the explanation so far.
> >
> > What's still unclear to me is why these timeouts are bound to wall
> >
On Thu, Sep 12, 2013 at 03:21:24PM +0200, Thomas Gleixner wrote:
>
> > (3): http://www.spinics.net/lists/netdev/msg245169.html
>
> Thanks for the explanation so far.
>
> What's still unclear to me is why these timeouts are bound to wall
> time in the first place.
>
> Is there any real reason
On Tue, 20 Aug 2013, Fan Du wrote:
> Thanks for your patience. Please let me take a few seconds try to
> explain this.
Sorry for the late reply.
> Current xfrm layers has *one* hrtimer to guard Ipsec keys timeout,
> The timeout could be measured in either of below two ways:
>
> (1) The timer
On Tue, 20 Aug 2013, Fan Du wrote:
Thanks for your patience. Please let me take a few seconds try to
explain this.
Sorry for the late reply.
Current xfrm layers has *one* hrtimer to guard Ipsec keys timeout,
The timeout could be measured in either of below two ways:
(1) The timer is
On Thu, Sep 12, 2013 at 03:21:24PM +0200, Thomas Gleixner wrote:
(3): http://www.spinics.net/lists/netdev/msg245169.html
Thanks for the explanation so far.
What's still unclear to me is why these timeouts are bound to wall
time in the first place.
Is there any real reason why the key
On Thu, 12 Sep 2013, Herbert Xu wrote:
On Thu, Sep 12, 2013 at 03:21:24PM +0200, Thomas Gleixner wrote:
(3): http://www.spinics.net/lists/netdev/msg245169.html
Thanks for the explanation so far.
What's still unclear to me is why these timeouts are bound to wall
time in the first
From: Thomas Gleixner t...@linutronix.de
Date: Thu, 12 Sep 2013 16:43:37 +0200 (CEST)
So what about going back to timer_list timers and simply utilize
register_pm_notifier(), which will tell you that the system resumed?
The thing to understand is that there are two timeouts for an IPSEC
rule,
On Thu, 12 Sep 2013, David Miller wrote:
From: Thomas Gleixner t...@linutronix.de
Date: Thu, 12 Sep 2013 16:43:37 +0200 (CEST)
So what about going back to timer_list timers and simply utilize
register_pm_notifier(), which will tell you that the system resumed?
The thing to understand is
On Thu, Sep 12, 2013 at 6:44 AM, Herbert Xu herb...@gondor.apana.org.au wrote:
On Thu, Sep 12, 2013 at 03:21:24PM +0200, Thomas Gleixner wrote:
(3): http://www.spinics.net/lists/netdev/msg245169.html
Thanks for the explanation so far.
What's still unclear to me is why these timeouts are
On Thu, 12 Sep 2013, John Stultz wrote:
On Thu, Sep 12, 2013 at 6:44 AM, Herbert Xu herb...@gondor.apana.org.au
wrote:
On Thu, Sep 12, 2013 at 03:21:24PM +0200, Thomas Gleixner wrote:
(3): http://www.spinics.net/lists/netdev/msg245169.html
Thanks for the explanation so far.
Hi Dave/Thomas
On 2013年09月13日 01:32, David Miller wrote:
From: Thomas Gleixnert...@linutronix.de
Date: Thu, 12 Sep 2013 16:43:37 +0200 (CEST)
So what about going back to timer_list timers and simply utilize
register_pm_notifier(), which will tell you that the system resumed?
The thing to
On 2013年08月18日 17:05, Thomas Gleixner wrote:
On Wed, 14 Aug 2013, Fan Du wrote:
From e3929d4fdfad5b40fd8cad0e217597670d1aef54 Mon Sep 17 00:00:00 2001
From: Fan Du
Date: Wed, 14 Aug 2013 16:39:23 +0800
Subject: [PATCHv3 linux-next] hrtimer: Add notifier when clock_was_set was
called
When
On 2013年08月18日 17:05, Thomas Gleixner wrote:
On Wed, 14 Aug 2013, Fan Du wrote:
From e3929d4fdfad5b40fd8cad0e217597670d1aef54 Mon Sep 17 00:00:00 2001
From: Fan Dufan...@windriver.com
Date: Wed, 14 Aug 2013 16:39:23 +0800
Subject: [PATCHv3 linux-next] hrtimer: Add notifier when
On Wed, 14 Aug 2013, Fan Du wrote:
> From e3929d4fdfad5b40fd8cad0e217597670d1aef54 Mon Sep 17 00:00:00 2001
> From: Fan Du
> Date: Wed, 14 Aug 2013 16:39:23 +0800
> Subject: [PATCHv3 linux-next] hrtimer: Add notifier when clock_was_set was
> called
>
> When clock_was_set is called in case of
On Wed, 14 Aug 2013, Fan Du wrote:
From e3929d4fdfad5b40fd8cad0e217597670d1aef54 Mon Sep 17 00:00:00 2001
From: Fan Du fan...@windriver.com
Date: Wed, 14 Aug 2013 16:39:23 +0800
Subject: [PATCHv3 linux-next] hrtimer: Add notifier when clock_was_set was
called
When clock_was_set is called
Hello.
On 08/14/2013 12:52 PM, Fan Du wrote:
From e3929d4fdfad5b40fd8cad0e217597670d1aef54 Mon Sep 17 00:00:00 2001
From: Fan Du
Date: Wed, 14 Aug 2013 16:39:23 +0800
Subject: [PATCHv3 linux-next] hrtimer: Add notifier when clock_was_set was
called
This header is not needed.
When
Hello.
On 08/14/2013 12:52 PM, Fan Du wrote:
From e3929d4fdfad5b40fd8cad0e217597670d1aef54 Mon Sep 17 00:00:00 2001
From: Fan Du fan...@windriver.com
Date: Wed, 14 Aug 2013 16:39:23 +0800
Subject: [PATCHv3 linux-next] hrtimer: Add notifier when clock_was_set was
called
This header is
30 matches
Mail list logo
