laforge has submitted this change. ( https://gerrit.osmocom.org/c/osmo-e1d/+/27811 )
Change subject: Make use of libosmcoore cpu_sched_vty ......................................................................
Make use of libosmcoore cpu_sched_vty
osmo-e1d automatically uses SCHED_RR already, but for consistency it actually makes sense to add this, so people can configure the scheduler priority and/or the cpu affinity this way.
The existing call to SCHED_RR is left in place for backwards compatibility. The new VTY commands can just override that, if needed.
Change-Id: I1b8021e6dc864af6e301fced427e24c8bb21ca2f --- M src/osmo-e1d.c 1 file changed, 2 insertions(+), 0 deletions(-)
Approvals: Jenkins Builder: Verified tnt: Looks good to me, but someone else must approve laforge: Looks good to me, approved
diff --git a/src/osmo-e1d.c b/src/osmo-e1d.c index 1e18f88..ee7c0fb 100644 --- a/src/osmo-e1d.c +++ b/src/osmo-e1d.c @@ -41,6 +41,7 @@ #include <osmocom/vty/logging.h> #include <osmocom/vty/stats.h> #include <osmocom/vty/misc.h> +#include <osmocom/vty/cpu_sched_vty.h>
#include <osmocom/e1d/proto_srv.h> #include <osmocom/e1d/proto.h> @@ -186,6 +187,7 @@ osmo_stats_vty_add_cmds(); osmo_talloc_vty_add_cmds(); osmo_fsm_vty_add_cmds(); + osmo_cpu_sched_vty_init(e1d);
handle_options(argc, argv);