[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpVQM3rdGk91oaSMUSf48CgPcMFB+bYETQsuOnkx8pEfUw@mail.gmail.com>
Date: Mon, 16 Nov 2020 10:57:58 -0800
From: Cong Wang <xiyou.wangcong@...il.com>
To: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
Cc: wenxu <wenxu@...oud.cn>, Jakub Kicinski <kuba@...nel.org>,
Vlad Buslov <vladbu@...dia.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [PATCH v10 net-next 3/3] net/sched: act_frag: add implict packet
fragment support.
On Sat, Nov 14, 2020 at 2:46 PM Marcelo Ricardo Leitner
<marcelo.leitner@...il.com> wrote:
> Davide had shared similar concerns with regards of the new module too.
> The main idea behind the new module was to keep it as
> isolated/contained as possible, and only so. So thumbs up from my
> side.
>
> To be clear, you're only talking about the module itself, right? It
> would still need to have the Kconfig to enable this feature, or not?
Both. The code itself doesn't look like a module, and it doesn't
look like an optional feature for act_ct either, does it? If not, there is
no need to have a user visible Kconfig, we just select it, or no Kconfig
at all.
Thanks.
Powered by blists - more mailing lists