Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Artem Savkov <asavkov@redhat.com>
To:     tglx@linutronix.de, jpoimboe@redhat.com, netdev@vger.kernel.org
Cc:     davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
        linux-kernel@vger.kernel.org, Artem Savkov <asavkov@redhat.com>
Subject: [PATCH v2 0/2] Upper bound mode for kernel timers
Date:   Thu, 24 Mar 2022 10:14:58 +0100
Message-Id: <20220324091500.2638745-1-asavkov@redhat.com>
In-Reply-To: <20220323184026.wkj55y55jbeumngs@treble>
References: <20220323184026.wkj55y55jbeumngs@treble>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

As previously discussed [1] we had a report of a regression in TCP keepalive
timer where timers were up to 4 minutes late resulting in disconnects.

This patchset tries to fix the problem by introducing upper bound kernel timers
and making tcp keepalive timer use those.

[1] https://lore.kernel.org/all/20210302001054.4qgrvnkltvkgikzr@treble/T/#u

---

Changes in v2:
  - TIMER_UPPER_BOUND flag description added as a comment in timer.h
  - Code style fixes
  - More elaborate commit message in timer commit

Artem Savkov (2):
  timer: introduce upper bound timers
  net: make tcp keepalive timer upper bound

 include/linux/timer.h           |  6 +++++-
 kernel/time/timer.c             | 36 ++++++++++++++++++++-------------
 net/ipv4/inet_connection_sock.c |  2 +-
 3 files changed, 28 insertions(+), 16 deletions(-)

-- 
2.34.1