https://osmocom.org/https://osmocom.org/favicon.ico?16647414092020-10-27T17:59:11ZOpen Source Mobile Communicationslibosmocore - Bug #4836: ns2: load sharing function for UDP datahttps://osmocom.org/issues/4836?journal_id=201532020-10-27T17:59:11Zdaniel
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/20153/diff?detail_id=33447">diff</a>)</li></ul> libosmocore - Bug #4836: ns2: load sharing function for UDP datahttps://osmocom.org/issues/4836?journal_id=203172020-11-14T08:42:28Zlaforge
<ul><li><strong>Category</strong> set to <i>libosmogb</i></li></ul> libosmocore - Bug #4836: ns2: load sharing function for UDP datahttps://osmocom.org/issues/4836?journal_id=203232020-11-14T08:53:43Zlaforge
<ul><li><strong>Assignee</strong> set to <i>lynxis</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul><p>Related: load sharing function for FR.</p>
<p>In the FR case, we should assume all weights are equal, and all NS-VC are equally suitable for signaling and user plane traffic.</p>
<p>In the TTCN3 code I chose to simply do a modulo operation of the identifier (LSP) into the array of currently unblocked NS-VCs. That of course means that every time links go up and down there will be a re-assignment of LSP to NS-VC. Some of hat would be avoidable in your list-based approach, but I would argue we can get away with the modulo-based approach. After all, when NS-VCs go down, we inevitably will have a re-distribution of traffic among the remaining NS-VCs. Your approach reduces the number of users/flows that gets redistributed. Not sure if it's worth the effort. The biggest danger in changing NS-VC for an established connection is re-ordering of a few messages.</p> libosmocore - Bug #4836: ns2: load sharing function for UDP datahttps://osmocom.org/issues/4836?journal_id=213092021-02-15T01:06:43Zlynxis
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>80</i></li></ul> libosmocore - Bug #4836: ns2: load sharing function for UDP datahttps://osmocom.org/issues/4836?journal_id=213442021-02-19T12:12:42Zlynxis
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="gprs_ns2: implement a simple load sharing for UDP Implement the load sharing based on modulo of ..." href="https://osmocom.org/projects/libosmocore/repository/libosmocore/revisions/d8a8d980535468d1f8642cdcf796b2d675c7b8df">libosmocore|d8a8d980535468d1f8642cdcf796b2d675c7b8df</a>.</p>