From: WANG Cong <xiyou.wangcong@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: xiyou.wangcong@gmail.com, herbert@gondor.apana.org.au,
linux-kernel@vger.kernel.org, akpm@osdl.org,
netdev@vger.kernel.org
Subject: Re: [Patch] (revised) net/xfrm/xfrm_policy.c: replace timer with delayed_work
Date: Sat, 3 May 2008 22:46:49 +0800 [thread overview]
Message-ID: <20080503144647.GF3986@hack> (raw)
In-Reply-To: <20080502.165455.24687234.davem@davemloft.net>
On Fri, May 02, 2008 at 04:54:55PM -0700, David Miller wrote:
>From: WANG Cong <xiyou.wangcong@gmail.com>
>Date: Fri, 2 May 2008 13:35:55 +0800 (CST)
>
>>
>> As suggested by Herbert Xu, using workqueue is better than timer
>> for net/xfrm/xfrm_policy.c, so replace them with delayed_work.
>> And due to this change, we have to disable BH when trying to
>> lock.
>>
>> Note that, this patch is not fully tested, so should be
>> in -mm first.
>>
>> Signed-off-by: WANG Cong <wangcong@zeuux.org>
>
>Please let me know when these two patches have gotten some
>good testing.
Thanks for your comments, David!
I thought it can go into -mm so that many other people can help
me to test it. Since I didn't have the IPSec environment. ;(
I will try if I can set up one, then test it.
Thanks.
next prev parent reply other threads:[~2008-05-03 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-16 15:55 [Patch]net/xfrm/xfrm_policy.c: replace timer with delayed_work WANG Cong
2008-04-27 1:18 ` Herbert Xu
2008-04-28 14:53 ` WANG Cong
2008-04-28 15:13 ` Herbert Xu
2008-04-30 16:06 ` WANG Cong
2008-05-01 1:11 ` Herbert Xu
2008-05-02 5:21 ` WANG Cong
2008-05-02 5:35 ` [Patch] (revised) net/xfrm/xfrm_policy.c: " WANG Cong
2008-05-02 23:54 ` David Miller
2008-05-03 14:46 ` WANG Cong [this message]
2008-05-03 15:06 ` Herbert Xu
2008-05-03 15:31 ` WANG Cong
2008-05-04 1:38 ` David Miller
2008-05-04 1:37 ` David Miller
2008-05-06 3:08 ` Herbert Xu
2008-05-06 3:57 ` WANG Cong
2008-05-02 5:43 ` [Patch](Revised) net/xfrm/xfrm_state.c: " WANG Cong
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=20080503144647.GF3986@hack \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).