From: John Ousterhout <ouster@cs.stanford.edu>
To: netdev@vger.kernel.org
Cc: pabeni@redhat.com, edumazet@google.com, horms@kernel.org,
kuba@kernel.org, John Ousterhout <ouster@cs.stanford.edu>
Subject: [PATCH net-next v12 13/15] net: homa: create homa_timer.c
Date: Thu, 24 Jul 2025 11:40:46 -0700 [thread overview]
Message-ID: <20250724184050.3130-14-ouster@cs.stanford.edu> (raw)
In-Reply-To: <20250724184050.3130-1-ouster@cs.stanford.edu>
This file contains code that wakes up periodically to check for
missing data, initiate retransmissions, and declare peer nodes
"dead".
Signed-off-by: John Ousterhout <ouster@cs.stanford.edu>
---
Changes for v11:
* Cleanup sparse annotations.
Changes for v10:
* Refactor resend mechanism
Changes for v9:
* Reflect changes in socket and peer management
* Minor name changes for clarity
Changes for v7:
* Interface changes to homa_sock_start_scan etc.
* Remove locker argument from locking functions
* Use u64 and __u64 properly
---
net/homa/homa_impl.h | 3 +
net/homa/homa_timer.c | 135 ++++++++++++++++++++++++++++++++++++++++++
2 files changed, 138 insertions(+)
create mode 100644 net/homa/homa_timer.c
diff --git a/net/homa/homa_impl.h b/net/homa/homa_impl.h
index a63cd9613d2f..1dcc39588a16 100644
--- a/net/homa/homa_impl.h
+++ b/net/homa/homa_impl.h
@@ -437,6 +437,9 @@ void homa_resend_pkt(struct sk_buff *skb, struct homa_rpc *rpc,
struct homa_sock *hsk);
void homa_rpc_handoff(struct homa_rpc *rpc);
void homa_spin(int ns);
+void homa_timer(struct homa *homa);
+void homa_timer_check_rpc(struct homa_rpc *rpc);
+int homa_timer_main(void *transport);
struct sk_buff *homa_tx_data_pkt_alloc(struct homa_rpc *rpc,
struct iov_iter *iter, int offset,
int length, int max_seg_data);
diff --git a/net/homa/homa_timer.c b/net/homa/homa_timer.c
new file mode 100644
index 000000000000..0de4de709460
--- /dev/null
+++ b/net/homa/homa_timer.c
@@ -0,0 +1,135 @@
+// SPDX-License-Identifier: BSD-2-Clause
+
+/* This file handles timing-related functions for Homa, such as retries
+ * and timeouts.
+ */
+
+#include "homa_impl.h"
+#include "homa_peer.h"
+#include "homa_rpc.h"
+#include "homa_stub.h"
+
+/**
+ * homa_timer_check_rpc() - Invoked for each RPC during each timer pass; does
+ * most of the work of checking for time-related actions such as sending
+ * resends, aborting RPCs for which there is no response, and sending
+ * requests for acks. It is separate from homa_timer because homa_timer
+ * got too long and deeply indented.
+ * @rpc: RPC to check; must be locked by the caller.
+ */
+void homa_timer_check_rpc(struct homa_rpc *rpc)
+ __must_hold(rpc->bucket->lock)
+{
+ struct homa *homa = rpc->hsk->homa;
+
+ /* See if we need to request an ack for this RPC. */
+ if (!homa_is_client(rpc->id) && rpc->state == RPC_OUTGOING &&
+ rpc->msgout.next_xmit_offset >= rpc->msgout.length) {
+ if (rpc->done_timer_ticks == 0) {
+ rpc->done_timer_ticks = homa->timer_ticks;
+ } else {
+ /* >= comparison that handles tick wrap-around. */
+ if ((rpc->done_timer_ticks + homa->request_ack_ticks
+ - 1 - homa->timer_ticks) & 1 << 31) {
+ struct homa_need_ack_hdr h;
+
+ homa_xmit_control(NEED_ACK, &h, sizeof(h), rpc);
+ }
+ }
+ }
+
+ if (rpc->state == RPC_INCOMING) {
+ if (rpc->msgin.num_bpages == 0) {
+ /* Waiting for buffer space, so no problem. */
+ rpc->silent_ticks = 0;
+ return;
+ }
+ } else if (!homa_is_client(rpc->id)) {
+ /* We're the server and we've received the input message;
+ * no need to worry about retries.
+ */
+ rpc->silent_ticks = 0;
+ return;
+ }
+
+ if (rpc->state == RPC_OUTGOING) {
+ if (rpc->msgout.next_xmit_offset < rpc->msgout.length) {
+ /* There are granted bytes that we haven't transmitted,
+ * so no need to be concerned; the ball is in our court.
+ */
+ rpc->silent_ticks = 0;
+ return;
+ }
+ }
+
+ if (rpc->silent_ticks < homa->resend_ticks)
+ return;
+ if (rpc->silent_ticks >= homa->timeout_ticks) {
+ homa_rpc_abort(rpc, -ETIMEDOUT);
+ return;
+ }
+ if (((rpc->silent_ticks - homa->resend_ticks) % homa->resend_interval)
+ == 0)
+ homa_request_retrans(rpc);
+}
+
+/**
+ * homa_timer() - This function is invoked at regular intervals ("ticks")
+ * to implement retries and aborts for Homa.
+ * @homa: Overall data about the Homa protocol implementation.
+ */
+void homa_timer(struct homa *homa)
+{
+ struct homa_socktab_scan scan;
+ struct homa_sock *hsk;
+ struct homa_rpc *rpc;
+ int rpc_count = 0;
+
+ homa->timer_ticks++;
+
+ /* Scan all existing RPCs in all sockets. */
+ for (hsk = homa_socktab_start_scan(homa->socktab, &scan);
+ hsk; hsk = homa_socktab_next(&scan)) {
+ while (hsk->dead_skbs >= homa->dead_buffs_limit)
+ /* If we get here, it means that Homa isn't keeping
+ * up with RPC reaping, so we'll help out. See
+ * "RPC Reaping Strategy" in homa_rpc_reap code for
+ * details.
+ */
+ if (homa_rpc_reap(hsk, false) == 0)
+ break;
+
+ if (list_empty(&hsk->active_rpcs) || hsk->shutdown)
+ continue;
+
+ if (!homa_protect_rpcs(hsk))
+ continue;
+ rcu_read_lock();
+ list_for_each_entry_rcu(rpc, &hsk->active_rpcs, active_links) {
+ homa_rpc_lock(rpc);
+ if (rpc->state == RPC_IN_SERVICE) {
+ rpc->silent_ticks = 0;
+ homa_rpc_unlock(rpc);
+ continue;
+ }
+ rpc->silent_ticks++;
+ homa_timer_check_rpc(rpc);
+ homa_rpc_unlock(rpc);
+ rpc_count++;
+ if (rpc_count >= 10) {
+ /* Give other kernel threads a chance to run
+ * on this core.
+ */
+ rcu_read_unlock();
+ schedule();
+ rcu_read_lock();
+ rpc_count = 0;
+ }
+ }
+ rcu_read_unlock();
+ homa_unprotect_rpcs(hsk);
+ }
+ homa_socktab_end_scan(&scan);
+ homa_skb_release_pages(homa);
+ homa_peer_gc(homa->peertab);
+}
--
2.43.0
next prev parent reply other threads:[~2025-07-24 18:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 18:40 [PATCH net-next v12 00/15] Begin upstreaming Homa transport protocol John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 01/15] net: homa: define user-visible API for Homa John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 02/15] net: homa: create homa_wire.h John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 03/15] net: homa: create shared Homa header files John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 04/15] net: homa: create homa_pool.h and homa_pool.c John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 05/15] net: homa: create homa_peer.h and homa_peer.c John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 06/15] net: homa: create homa_sock.h and homa_sock.c John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 07/15] net: homa: create homa_interest.h and homa_interest.c John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 08/15] net: homa: create homa_pacer.h and homa_pacer.c John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 09/15] net: homa: create homa_rpc.h and homa_rpc.c John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 10/15] net: homa: create homa_outgoing.c John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 11/15] net: homa: create homa_utils.c John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 12/15] net: homa: create homa_incoming.c John Ousterhout
2025-07-24 18:40 ` John Ousterhout [this message]
2025-07-24 18:40 ` [PATCH net-next v12 14/15] net: homa: create homa_plumbing.c John Ousterhout
2025-07-24 19:38 ` Kuniyuki Iwashima
2025-07-25 16:11 ` John Ousterhout
2025-07-24 18:40 ` [PATCH net-next v12 15/15] net: homa: create Makefile and Kconfig John Ousterhout
2025-07-26 22:41 ` kernel test robot
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=20250724184050.3130-14-ouster@cs.stanford.edu \
--to=ouster@cs.stanford.edu \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).