From: kernel test robot <lkp@intel.com>
To: Coco Li <lixiaoyan@google.com>, Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Neal Cardwell <ncardwell@google.com>,
Mubashir Adnan Qureshi <mubashirq@google.com>,
Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
Jonathan Corbet <corbet@lwn.net>,
David Ahern <dsahern@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: oe-kbuild-all@lists.linux.dev, netdev@vger.kernel.org,
Chao Wu <wwchao@google.com>, Wei Wang <weiwan@google.com>,
Pradeep Nemavat <pnemavat@google.com>,
Coco Li <lixiaoyan@google.com>
Subject: Re: [PATCH v6 net-next 3/5] netns-ipv4: reorganize netns_ipv4 fast path variables
Date: Sat, 4 Nov 2023 04:00:10 +0800 [thread overview]
Message-ID: <202311040337.CPhnv1CW-lkp@intel.com> (raw)
In-Reply-To: <20231030052550.3157719-4-lixiaoyan@google.com>
Hi Coco,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Coco-Li/Documentations-Analyze-heavily-used-Networking-related-structs/20231030-133431
base: net-next/main
patch link: https://lore.kernel.org/r/20231030052550.3157719-4-lixiaoyan%40google.com
patch subject: [PATCH v6 net-next 3/5] netns-ipv4: reorganize netns_ipv4 fast path variables
config: i386-randconfig-013-20231101 (https://download.01.org/0day-ci/archive/20231104/202311040337.CPhnv1CW-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231104/202311040337.CPhnv1CW-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202311040337.CPhnv1CW-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/core/net_namespace.c:1102:20: warning: 'netns_ipv4_struct_check' defined but not used [-Wunused-function]
1102 | static void __init netns_ipv4_struct_check(void)
| ^~~~~~~~~~~~~~~~~~~~~~~
vim +/netns_ipv4_struct_check +1102 net/core/net_namespace.c
1101
> 1102 static void __init netns_ipv4_struct_check(void)
1103 {
1104 /* TX readonly hotpath cache lines */
1105 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_tx,
1106 sysctl_tcp_early_retrans);
1107 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_tx,
1108 sysctl_tcp_tso_win_divisor);
1109 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_tx,
1110 sysctl_tcp_tso_rtt_log);
1111 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_tx,
1112 sysctl_tcp_autocorking);
1113 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_tx,
1114 sysctl_tcp_min_snd_mss);
1115 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_tx,
1116 sysctl_tcp_notsent_lowat);
1117 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_tx,
1118 sysctl_tcp_limit_output_bytes);
1119 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_tx,
1120 sysctl_tcp_min_rtt_wlen);
1121 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_tx,
1122 sysctl_tcp_wmem);
1123 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_tx,
1124 sysctl_ip_fwd_use_pmtu);
1125 CACHELINE_ASSERT_GROUP_SIZE(struct netns_ipv4, netns_ipv4_read_tx, 33);
1126
1127 /* TXRX readonly hotpath cache lines */
1128 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_txrx,
1129 sysctl_tcp_moderate_rcvbuf);
1130 CACHELINE_ASSERT_GROUP_SIZE(struct netns_ipv4, netns_ipv4_read_txrx, 1);
1131
1132 /* RX readonly hotpath cache line */
1133 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_rx,
1134 sysctl_ip_early_demux);
1135 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_rx,
1136 sysctl_tcp_early_demux);
1137 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_rx,
1138 sysctl_tcp_reordering);
1139 CACHELINE_ASSERT_GROUP_MEMBER(struct netns_ipv4, netns_ipv4_read_rx,
1140 sysctl_tcp_rmem);
1141 CACHELINE_ASSERT_GROUP_SIZE(struct netns_ipv4, netns_ipv4_read_rx, 18);
1142 }
1143
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-03 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 5:25 [PATCH v6 net-next 0/5] Analyze and Reorganize core Networking Structs to optimize cacheline consumption Coco Li
2023-10-30 5:25 ` [PATCH v6 net-next 1/5] Documentations: Analyze heavily used Networking related structs Coco Li
2023-10-30 5:25 ` [PATCH v6 net-next 2/5] cache: enforce cache groups Coco Li
2023-10-30 5:25 ` [PATCH v6 net-next 3/5] netns-ipv4: reorganize netns_ipv4 fast path variables Coco Li
2023-11-03 20:00 ` kernel test robot [this message]
2023-10-30 5:25 ` [PATCH v6 net-next 4/5] net-device: reorganize net_device " Coco Li
2023-10-30 5:25 ` [PATCH v6 net-next 5/5] tcp: reorganize tcp_sock " Coco Li
2023-10-30 6:35 ` [PATCH v6 net-next 0/5] Analyze and Reorganize core Networking Structs to optimize cacheline consumption Jakub Kicinski
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=202311040337.CPhnv1CW-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lixiaoyan@google.com \
--cc=mubashirq@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=pnemavat@google.com \
--cc=weiwan@google.com \
--cc=wwchao@google.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.