mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "Philipp Reisner" <philipp.reisner@linbit.com>,
	"Lars Ellenberg" <lars@linbit.com>,
	drbd-dev@lists.linux.dev, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>,
	"Lars Ellenberg" <lars.ellenberg@linbit.com>
Subject: [PATCH 3/7] drbd: raise the socket buffer size limits to 128 MiB
Date: Wed, 23 Sep 2026 16:06:04 +0200	[thread overview]
Message-ID: <20260923140608.1116713-4-christoph.boehmwalder@linbit.com> (raw)
In-Reply-To: <20260923140608.1116713-1-christoph.boehmwalder@linbit.com>

sndbuf-size and rcvbuf-size are capped at 10 MiB, with a comment that a
larger TCP buffer is not useful. That was written for the networks of
2008. On today's long-haul 25G+ links the bandwidth-delay product of a
single DRBD connection easily exceeds 10 MiB, and the cap then limits
replication throughput regardless of how the rest of the stack is tuned.

Raise both limits to 128 MiB, the value DRBD 9 has used for years. The
defaults are unchanged: 0 keeps the kernel's auto-tuning.

Signed-off-by: Christoph Böhmwalder <christoph.boehmwalder@linbit.com>
---
 include/uapi/linux/drbd_limits.h | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/include/uapi/linux/drbd_limits.h b/include/uapi/linux/drbd_limits.h
index 65d3ebf2437b..4132b619376c 100644
--- a/include/uapi/linux/drbd_limits.h
+++ b/include/uapi/linux/drbd_limits.h
@@ -87,14 +87,13 @@
 #define DRBD_MAX_EPOCH_SIZE_DEF 2048U
 #define DRBD_MAX_EPOCH_SIZE_SCALE '1'
 
-  /* I don't think that a tcp send buffer of more than 10M is useful */
 #define DRBD_SNDBUF_SIZE_MIN  0U
-#define DRBD_SNDBUF_SIZE_MAX  (10U<<20)
+#define DRBD_SNDBUF_SIZE_MAX  (128U << 20)
 #define DRBD_SNDBUF_SIZE_DEF  0U
 #define DRBD_SNDBUF_SIZE_SCALE '1'
 
 #define DRBD_RCVBUF_SIZE_MIN  0U
-#define DRBD_RCVBUF_SIZE_MAX  (10U<<20)
+#define DRBD_RCVBUF_SIZE_MAX  (128U << 20)
 #define DRBD_RCVBUF_SIZE_DEF  0U
 #define DRBD_RCVBUF_SIZE_SCALE '1'
 
-- 
2.55.0


  parent reply	other threads:[~2026-09-23 14:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 14:06 [PATCH 0/7] drbd: preparation for DRBD 9 Christoph Böhmwalder
2026-09-23 14:06 ` [PATCH 1/7] drbd: rename drbd_worker.c to drbd_sender.c Christoph Böhmwalder
2026-09-23 14:06 ` [PATCH 2/7] drbd: modernize the file header comments Christoph Böhmwalder
2026-09-23 14:06 ` Christoph Böhmwalder [this message]
2026-09-23 14:06 ` [PATCH 4/7] drbd: raise the maximum resync rate to 8 GiB/s Christoph Böhmwalder
2026-09-23 14:06 ` [PATCH 5/7] drbd: replace the drbd_interval bitfields with a type and flags Christoph Böhmwalder
2026-09-23 14:06 ` [PATCH 6/7] drbd: move the packet name table to drbd_strings.c Christoph Böhmwalder
2026-09-23 14:06 ` [PATCH 7/7] drbd: rate limit log messages per object Christoph Böhmwalder
2026-11-09 17:22 ` [PATCH 0/7] drbd: preparation for DRBD 9 Christoph Böhmwalder
2026-11-09 17:40   ` Jens Axboe
2026-11-09 17:40 ` Jens Axboe

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=20260923140608.1116713-4-christoph.boehmwalder@linbit.com \
    --to=christoph.boehmwalder@linbit.com \
    --cc=axboe@kernel.dk \
    --cc=drbd-dev@lists.linux.dev \
    --cc=lars.ellenberg@linbit.com \
    --cc=lars@linbit.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipp.reisner@linbit.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

all inboxes | Powered by JetHome®