From: Jiri Pirko <jiri@resnulli.us>
To: Aurelien Aptel <aaptel@nvidia.com>
Cc: linux-nvme@lists.infradead.org, netdev@vger.kernel.org,
sagi@grimberg.me, hch@lst.de, kbusch@kernel.org, axboe@fb.com,
chaitanyak@nvidia.com, davem@davemloft.net, kuba@kernel.org,
aurelien.aptel@gmail.com, smalin@nvidia.com, malin1024@gmail.com,
ogerlitz@nvidia.com, yorayz@nvidia.com, borisp@nvidia.com,
galshalom@nvidia.com, mgurtovoy@nvidia.com, edumazet@google.com,
pabeni@redhat.com
Subject: Re: [PATCH v22 02/20] netlink: add new family to manage ULP_DDP enablement and stats
Date: Tue, 2 Jan 2024 11:08:19 +0100 [thread overview]
Message-ID: <ZZPgk3mrEkciwI_7@nanopsycho> (raw)
In-Reply-To: <20231221213358.105704-3-aaptel@nvidia.com>
Thu, Dec 21, 2023 at 10:33:40PM CET, aaptel@nvidia.com wrote:
>Add a new netlink family to get/set ULP DDP capabilities on a network
>device and to retrieve statistics.
>
>The messages use the genetlink infrastructure and are specified in a
>YAML file which was used to generate some of the files in this commit:
>
>./tools/net/ynl/ynl-gen-c.py --mode kernel \
> --spec ./Documentation/netlink/specs/ulp_ddp.yaml --header \
> -o net/core/ulp_ddp_gen_nl.h
>./tools/net/ynl/ynl-gen-c.py --mode kernel \
> --spec ./Documentation/netlink/specs/ulp_ddp.yaml --source \
> -o net/core/ulp_ddp_gen_nl.c
>./tools/net/ynl/ynl-gen-c.py --mode uapi \
> --spec ./Documentation/netlink/specs/ulp_ddp.yaml --header \
> > include/uapi/linux/ulp_ddp.h
>
>Signed-off-by: Shai Malin <smalin@nvidia.com>
>Signed-off-by: Aurelien Aptel <aaptel@nvidia.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
next prev parent reply other threads:[~2024-01-02 10:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 21:33 [PATCH v22 00/20] nvme-tcp receive offloads Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 01/20] net: Introduce direct data placement tcp offload Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 02/20] netlink: add new family to manage ULP_DDP enablement and stats Aurelien Aptel
2024-01-02 10:08 ` Jiri Pirko [this message]
2023-12-21 21:33 ` [PATCH v22 03/20] iov_iter: skip copy if src == dst for direct data placement Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 04/20] net/tls,core: export get_netdev_for_sock Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 05/20] nvme-tcp: Add DDP offload control path Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 06/20] nvme-tcp: Add DDP data-path Aurelien Aptel
2024-01-09 9:34 ` Aurelien Aptel
2024-01-10 16:05 ` Sagi Grimberg
2024-01-17 10:03 ` Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 07/20] nvme-tcp: RX DDGST offload Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 08/20] nvme-tcp: Deal with netdevice DOWN events Aurelien Aptel
2024-01-10 16:01 ` Sagi Grimberg
2024-01-17 10:05 ` Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 09/20] Documentation: add ULP DDP offload documentation Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 10/20] net/mlx5e: Rename from tls to transport static params Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 11/20] net/mlx5e: Refactor ico sq polling to get budget Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 12/20] net/mlx5: Add NVMEoTCP caps, HW bits, 128B CQE and enumerations Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 13/20] net/mlx5e: NVMEoTCP, offload initialization Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 14/20] net/mlx5e: TCP flow steering for nvme-tcp acceleration Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 15/20] net/mlx5e: NVMEoTCP, use KLM UMRs for buffer registration Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 16/20] net/mlx5e: NVMEoTCP, queue init/teardown Aurelien Aptel
2023-12-23 17:48 ` Simon Horman
2023-12-26 12:58 ` Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 17/20] net/mlx5e: NVMEoTCP, ddp setup and resync Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 18/20] net/mlx5e: NVMEoTCP, async ddp invalidation Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 19/20] net/mlx5e: NVMEoTCP, data-path for DDP+DDGST offload Aurelien Aptel
2023-12-21 21:33 ` [PATCH v22 20/20] net/mlx5e: NVMEoTCP, statistics Aurelien Aptel
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=ZZPgk3mrEkciwI_7@nanopsycho \
--to=jiri@resnulli.us \
--cc=aaptel@nvidia.com \
--cc=aurelien.aptel@gmail.com \
--cc=axboe@fb.com \
--cc=borisp@nvidia.com \
--cc=chaitanyak@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=galshalom@nvidia.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=malin1024@gmail.com \
--cc=mgurtovoy@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@nvidia.com \
--cc=pabeni@redhat.com \
--cc=sagi@grimberg.me \
--cc=smalin@nvidia.com \
--cc=yorayz@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox