[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <670dc5cab30f5_2e1742294bc@willemb.c.googlers.com.notmuch>
Date: Mon, 14 Oct 2024 21:30:50 -0400
From: Willem de Bruijn <willemdebruijn.kernel@...il.com>
To: Jason Xing <kerneljasonxing@...il.com>,
davem@...emloft.net,
edumazet@...gle.com,
kuba@...nel.org,
pabeni@...hat.com,
dsahern@...nel.org,
willemdebruijn.kernel@...il.com,
willemb@...gle.com,
ast@...nel.org,
daniel@...earbox.net,
andrii@...nel.org,
martin.lau@...ux.dev,
eddyz87@...il.com,
song@...nel.org,
yonghong.song@...ux.dev,
john.fastabend@...il.com,
kpsingh@...nel.org,
sdf@...ichev.me,
haoluo@...gle.com,
jolsa@...nel.org
Cc: bpf@...r.kernel.org,
netdev@...r.kernel.org,
Jason Xing <kernelxing@...cent.com>
Subject: Re: [PATCH net-next v2 01/12] net-timestamp: introduce socket tsflag
requestors
Jason Xing wrote:
> From: Jason Xing <kernelxing@...cent.com>
>
> We need a separate tsflag to control bpf extension feature so that
> we will not affect the behaviors of existing applications.
>
> The idea of introducing requestors for better extension (not only
> serving bpf extension) comes from Vadim Fedorenko.
As also said in the cover letter: I prefer sk_tstflags_bpf.
This array approach adds code churn, may have cacheline effects by
moving other fields and anticipates I don't see a third requestor
happening. And if it does, we'll deal with it then.
Powered by blists - more mailing lists