Re: [PATCH net-next v12 00/13] Device Memory TCP

[Mina Almasry]

On Thu, Jun 13, 2024 at 6:35 PM Jakub Kicinski <kuba@xxxxxxxxxx> wrote:
>
> On Thu, 13 Jun 2024 01:35:37 +0000 Mina Almasry wrote:
> > v12: https://patchwork.kernel.org/project/netdevbpf/list/?series=859747&state=*
>
> patches 5 and 6 transiently break the build
>
> ../include/trace/events/page_pool.h:65:23: error: use of undeclared identifier 'NET_IOV'
>    65 |                   __entry->netmem & NET_IOV, __entry->pfn, __entry->release)
>       |                                     ^
> ../include/trace/events/page_pool.h:91:23: error: use of undeclared identifier 'NET_IOV'
>    91 |                   __entry->netmem & NET_IOV, __entry->pfn, __entry->hold)
>       |                                     ^
>
> Looking at NIPA status the builders are 12h behind, so please don't
> repost immediately. This series takes a lot of compute cycles to build.
>
> FWIW there is a docker version of NIPA checks in the nipa repo.
>
> https://github.com/linux-netdev/nipa/tree/main/docker
>
> IDK if it still works, but could help avoid mistakes..

My sincere apologies. I have trouble with the patch-by-patch
allmodconfig build being very slow on my setup with the headers I'm
touching, and I've been running into false positives with the C=1 &
W=1 checks. I've been trying to look at the nipa scripts and porting
them over to my setup. I'll take a look at the docker image and if
not, at least make sure the patch-by-patch allmodconfig with C=1 and
W=1 is working.

-- 
Thanks,
Mina