From: Wen Congyang <wency@cn.fujitsu.com>
To: Patrick McHardy <kaber@trash.net>, Li Zhijian <lizhijian@cn.fujitsu.com>
Cc: <netfilter-devel@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <pablo@netfilter.org>,
<kadlec@blackhole.kfki.hu>, <davem@davemloft.net>,
<coreteam@netfilter.org>, Yang Hongyang <yanghy@cn.fujitsu.com>,
zhanghailiang <zhang.zhanghailiang@huawei.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
"peter.huangpeng" <peter.huangpeng@huawei.com>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>
Subject: Re: [RFC] COLO Proxy Module
Date: Wed, 1 Jul 2015 18:57:11 +0800 [thread overview]
Message-ID: <5593C787.3070005@cn.fujitsu.com> (raw)
In-Reply-To: <20150630091905.GF17501@acer.localdomain>
On 06/30/2015 05:19 PM, Patrick McHardy wrote:
> On 30.06, Li Zhijian wrote:
>> |ping...
>>
>> and i have another question:
>> can i add a new |||nf_ct_ext_id simply without touching the exiting kernel
>> code?|
>
> No, the kernel needs to know the highest extension ID in order to
> allocate space for the offsets.
So if we want to add a new extension, we should post the module too. Is
it right?
Thanks
Wen Congyang
>
>> in order to support COLO-Proxy, i need a extra nf_ct_ext_id called
>> "NF_CT_EXT_COLO"
>> to store some message of COLO related. This message can help COLO-Proxy to
>> buffer packet and compare packet for each connection.
>>
>> Thanks
>> Li Zhijian
>
> Cheers,
> Patrick
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> .
>
prev parent reply other threads:[~2015-07-01 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 6:37 [RFC] COLO Proxy Module Li Zhijian
[not found] ` <55924787.3060203@cn.fujitsu.com>
2015-06-30 9:19 ` Patrick McHardy
2015-07-01 10:57 ` Wen Congyang [this message]
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=5593C787.3070005@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=arei.gonglei@huawei.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhijian@cn.fujitsu.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=peter.huangpeng@huawei.com \
--cc=yanghy@cn.fujitsu.com \
--cc=zhang.zhanghailiang@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.