From: Jakub Kicinski <kuba@kernel.org>
To: Coco Li <lixiaoyan@google.com>
Cc: 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>,
netdev@vger.kernel.org, Chao Wu <wwchao@google.com>,
Wei Wang <weiwan@google.com>,
Pradeep Nemavat <pnemavat@google.com>
Subject: Re: [PATCH v7 net-next 1/5] Documentations: Analyze heavily used Networking related structs
Date: Tue, 14 Nov 2023 23:30:56 -0500 [thread overview]
Message-ID: <20231114233056.5f798249@kernel.org> (raw)
In-Reply-To: <20231113233301.1020992-2-lixiaoyan@google.com>
On Mon, 13 Nov 2023 23:32:57 +0000 Coco Li wrote:
> create mode 100644 Documentation/networking/net_cachelines/index.rst
> create mode 100644 Documentation/networking/net_cachelines/inet_connection_sock.rst
> create mode 100644 Documentation/networking/net_cachelines/inet_sock.rst
> create mode 100644 Documentation/networking/net_cachelines/net_device.rst
> create mode 100644 Documentation/networking/net_cachelines/netns_ipv4_sysctl.rst
> create mode 100644 Documentation/networking/net_cachelines/snmp.rst
> create mode 100644 Documentation/networking/net_cachelines/tcp_sock.rst
Can we add a small MAINTAINERS file entry for these files?
To clearly state who's taking on keeping them in sync?
Maybe Eric?
next prev parent reply other threads:[~2023-11-15 4:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 23:32 [PATCH v7 net-next 0/5] Analyze and Reorganize core Networking Structs to optimize cacheline consumption Coco Li
2023-11-13 23:32 ` [PATCH v7 net-next 1/5] Documentations: Analyze heavily used Networking related structs Coco Li
2023-11-15 4:30 ` Jakub Kicinski [this message]
2023-11-15 7:07 ` Eric Dumazet
2023-11-15 17:59 ` Coco Li
2023-11-20 17:19 ` Simon Horman
2023-11-13 23:32 ` [PATCH v7 net-next 2/5] cache: enforce cache groups Coco Li
2023-11-15 4:32 ` Jakub Kicinski
2023-11-13 23:32 ` [PATCH v7 net-next 3/5] netns-ipv4: reorganize netns_ipv4 fast path variables Coco Li
2023-11-13 23:33 ` [PATCH v7 net-next 4/5] net-device: reorganize net_device " Coco Li
2023-11-16 12:39 ` kernel test robot
2023-11-17 19:44 ` Coco Li
2023-11-20 19:41 ` Nathan Chancellor
2023-11-13 23:33 ` [PATCH v7 net-next 5/5] tcp: reorganize tcp_sock " Coco Li
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=20231114233056.5f798249@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=lixiaoyan@google.com \
--cc=mubashirq@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--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.