Re: [PATCH 36/44] [XFRM]: Introduce XFRM_MSG_REPORT.

2006-08-23 Thread David Miller
From: Masahide NAKAMURA <[EMAIL PROTECTED]> Date: Thu, 24 Aug 2006 15:48:10 +0900 > Should I start to design it? Thank you for the analysis. Let's not jump so quickly towards implementation just yet. What I plan to do right now is port my XFRM hashing patches into the current net-2.6.19 tree.

Re: [PATCH 36/44] [XFRM]: Introduce XFRM_MSG_REPORT.

2006-08-23 Thread Masahide NAKAMURA
David Miller wrote: From: YOSHIFUJI Hideaki <[EMAIL PROTECTED]> Date: Thu, 24 Aug 2006 00:02:37 +0900 XFRM_MSG_REPORT is a message as notification of state protocol and selector from kernel to user-space. Mobile IPv6 will use it when inbound reject is occurred at route optimization to make user

Re: [PATCH 36/44] [XFRM]: Introduce XFRM_MSG_REPORT.

2006-08-23 Thread David Miller
From: YOSHIFUJI Hideaki <[EMAIL PROTECTED]> Date: Thu, 24 Aug 2006 00:02:37 +0900 > XFRM_MSG_REPORT is a message as notification of state protocol and selector > from kernel to user-space. > Mobile IPv6 will use it when inbound reject is occurred at route optimization > to make user-space know a b

[PATCH 36/44] [XFRM]: Introduce XFRM_MSG_REPORT.

2006-08-23 Thread YOSHIFUJI Hideaki
From: Masahide NAKAMURA <[EMAIL PROTECTED]> XFRM_MSG_REPORT is a message as notification of state protocol and selector from kernel to user-space. Mobile IPv6 will use it when inbound reject is occurred at route optimization to make user-space know a binding error requirement. Based on MIPL2 kerne