[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALW65ja5wOf-5PAkQY0yt8FO1_gTvfL392Q+S3TKtJoQ1kXFug@mail.gmail.com>
Date: Thu, 29 Jan 2026 20:06:22 +0800
From: Qingfang Deng <dqfext@...il.com>
To: Florian Westphal <fw@...len.de>
Cc: Pablo Neira Ayuso <pablo@...filter.org>, Phil Sutter <phil@....cc>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Lorenzo Bianconi <lorenzo@...nel.org>
Subject: Re: [PATCH nf-next] netfilter: flowtable: dedicated slab for flow entry
On Thu, Jan 29, 2026 at 6:26 PM Florian Westphal <fw@...len.de> wrote:
> Ok, but please use KMEM_CACHE(), we've had a bunch of patches
> that removed kmem_cache_create() in several places, I would like
> to avoid a followup patch.
But I'm creating a slab with a different name (`nf_flow_offload`) from
the struct name (`flow_offload`). Should I keep the `nf_` prefix?
Regards,
Qingfang
Powered by blists - more mailing lists