From 2a490d559704d246e89bd0c05d4b85d28f7993f1 Mon Sep 17 00:00:00 2001 From: Erik Boasson Date: Mon, 29 Jan 2024 13:49:32 +0100 Subject: [PATCH] Allow multipathing between PSMX and DDSI Once upon a time sending a sample to a single destination via PSMX and DDSI at the same time would lead to stuttering because of insufficient precise filtering in the delivery paths, but that problem has been fixed a long time ago (I think in commit ef91c275e5b6649279fff7d29462d491a0d08b28). For a long time, no-one realised that the bit that prevented this from happening was left in. Signed-off-by: Erik Boasson --- src/core/ddsi/src/ddsi_wraddrset.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/core/ddsi/src/ddsi_wraddrset.c b/src/core/ddsi/src/ddsi_wraddrset.c index 90fa3dd570..3805e76d43 100644 --- a/src/core/ddsi/src/ddsi_wraddrset.c +++ b/src/core/ddsi/src/ddsi_wraddrset.c @@ -324,9 +324,7 @@ static const int32_t cost_discarded = 1; // Cost associated with delivering another time to a reader that has // already been covered by a (selected) PSMX locator. -// Currently, it is quite painful when this happens because it can -// lead to user observable stuttering. -static const int32_t cost_redundant_psmx = 1000000; +static const int32_t cost_redundant_psmx = 0; // Cost associated with delivering data for the first time (slightly // negative cost makes it possible to give a slightly higher initial