From: "Maurizio Lombardi" <mlombard@arkamax.eu>
To: "Ing. Alfonso Kuen Arroyo" <gerencia@idkmanager.com>,
<hch@lst.de>, <sagi@grimberg.me>, <kch@nvidia.com>
Cc: <linux-nvme@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<mlombard@arkamax.eu>
Subject: Re: [PATCH v2] nvmet-tcp: fix stale comment on NVMET_TCP_MAXH2CDATA
Date: Wed, 23 Sep 2026 09:39:59 +0200 [thread overview]
Message-ID: <DLMIXHATYR90.4RUG08AMWH8U@arkamax.eu> (raw)
In-Reply-To: <179013720383.9364.11263428288753603011@idkmanager.com>
On Wed Sep 23, 2026 at 6:20 AM CEST, Ing. Alfonso Kuen Arroyo wrote:
> The constant is 0x400000, 4 MiB, but the comment next to it said 16M.
> Use SZ_4M instead of a value and a comment that can drift out of sync
> with each other, as suggested by Christoph Hellwig.
>
> Noticed by Maurizio Lombardi while reviewing "nvmet-tcp: report a
> bounded MDTS instead of "no limit"".
>
> v2: use SZ_4M instead of the raw hex value + comment (Christoph
> Hellwig). The file did not pull in linux/sizes.h yet and had no
> other SZ_ user, so the include is added.
version differences should be put after the '---' separator, they are
not part of the commit message
>
> Signed-off-by: Alfonso Kuen
The mail is missing, this should be:
Signed-off-by: Alfonso Kuen <gerencia@idkmanager.com>
> ---
> drivers/nvme/target/tcp.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/nvme/target/tcp.c b/drivers/nvme/target/tcp.c
> index e598101..000000 100644
> --- a/drivers/nvme/target/tcp.c
> +++ b/drivers/nvme/target/tcp.c
> @@ -18,12 +18,13 @@
> #include <net/handshake.h>
> #include <linux/inet.h>
> #include <linux/llist.h>
> +#include <linux/sizes.h>
> #include <trace/events/sock.h>
>
> #include "nvmet.h"
>
> #define NVMET_TCP_DEF_INLINE_DATA_SIZE (4 * PAGE_SIZE)
> -#define NVMET_TCP_MAXH2CDATA 0x400000 /* 16M arbitrary limit */
> +#define NVMET_TCP_MAXH2CDATA SZ_4M
> #define NVMET_TCP_BACKLOG 128
>
> static int param_store_val(const char *str, int *val, int min, int max)
> --
> 2.53.0
The change looks ok to me
Reviewed-by: Maurizio Lombardi <mlombard@redhat.com>
next prev parent reply other threads:[~2026-09-23 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 4:20 Ing. Alfonso Kuen Arroyo
2026-09-23 7:39 ` Maurizio Lombardi [this message]
2026-09-25 6:57 ` Christoph Hellwig
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=DLMIXHATYR90.4RUG08AMWH8U@arkamax.eu \
--to=mlombard@arkamax.eu \
--cc=gerencia@idkmanager.com \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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
all inboxes | Powered by JetHome®