Two more questions below:
Am 9/21/2024 um 6:42 PM schrieb Mathieu Desnoyers:
+#define NR_PERCPU_SLOTS_BITS 3
Have you measured any advantage of this multi-slot version vs a version
with just one normal slot and one emergency slot?
With just one normal slot, the normal slot version would always be zero,
and there'd be no need to increment etc., which might make the common
case (no conflict) faster.
Either way I recommend stress testing with just one normal slot to
increase the chance of conflict (and hence triggering corner cases)
during stress testing.
+retry:
+ node = uatomic_load(node_p, CMM_RELAXED);
+ if (!node)
+ return false;
+ /* Use rseq to try setting current slot hp. Store B. */
+ if (rseq_load_cbne_store__ptr(RSEQ_MO_RELAXED, RSEQ_PERCPU_CPU_ID,
+ (intptr_t *) &slot->node, (intptr_t) NULL,
+ (intptr_t) node, cpu)) {
+ slot = &cpu_slots->slots[HPREF_EMERGENCY_SLOT];
+ use_refcount = true;
+ /*
+ * This may busy-wait for another reader using the
+ * emergency slot to transition to refcount.
+ */
+ caa_cpu_relax();
+ goto retry;
+ }
I'm not familiar with Linux' preemption model. Can this deadlock if a
low-interrupt-level thread is occupying the EMERGENCY slot and a
higher-interrupt-level thread is also trying to take it?
Best wishes,
jonas
