| To: | Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: RFC: IPSEC patch 0 for netlink events |
| From: | jamal <hadi@xxxxxxxxxx> |
| Date: | 27 Mar 2005 14:07:29 -0500 |
| Cc: | Patrick McHardy <kaber@xxxxxxxxx>, Masahide NAKAMURA <nakam@xxxxxxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>, netdev <netdev@xxxxxxxxxxx> |
| In-reply-to: | <20050327081848.GA13428@xxxxxxxxxxxxxxxxxxx> |
| Organization: | jamalopolous |
| References: | <1111864971.1092.904.camel@xxxxxxxxxxxxxxxx> <20050326194707.GA9872@xxxxxxxxxxxxxxxxxxx> <1111867875.1089.915.camel@xxxxxxxxxxxxxxxx> <20050327081848.GA13428@xxxxxxxxxxxxxxxxxxx> |
| Reply-to: | hadi@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Sun, 2005-03-27 at 03:18, Herbert Xu wrote: > For non-standard extensions like this I wouldn't worry about PF_KEY. > After all, if you're going to make sense of all the messages from > the kernel you'll have to use netlink anyway. > Just for consistency (since both call the same xfrm_state core code) I made some minor changes to pf_key internal-to-kernel API (not exposed to user space). Sample patch, still under construction, attached. pfkey already does adverts on its own after a response from the generic code. In the future this could be modified to do events about the same time netlink does them i.e invocation from core xfrm_state code. At the moment pfkey listeners are slightly delayed relative to netlink. cheers, jamal
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Resend: Re: PATCH: IPSEC acquire in presence of multiple managers, jamal |
|---|---|
| Next by Date: | cls_u32 compile failure in current 2.6.12-rc1+BK tree, Meelis Roos |
| Previous by Thread: | Re: RFC: IPSEC patch 0 for netlink events, Herbert Xu |
| Next by Thread: | Re: RFC: IPSEC patch 0 for netlink events, Patrick McHardy |
| Indexes: | [Date] [Thread] [Top] [All Lists] |