the last user of this option was DPDKStack::DPDKStack(). which used it
to initialize its func vector. but this option is not used anymore.
so let's drop it.
Signed-off-by: Kefu Chai <kchai@redhat.com>
(cherry picked from commit
ee7184639dcd7b8fc0ed5a189bc764151e601437)
:Default: ``3``
-``ms_async_max_op_threads``
-
-:Description: Maximum number of worker threads used by each Async Messenger instance.
- Set to lower values when your machine has limited CPU count, and increase
- when your CPUs are underutilized (i. e. one or more of CPUs are
- constantly on 100% load during I/O operations).
-:Type: 64-bit Unsigned Integer
-:Required: No
-:Default: ``5``
-
-
``ms_async_send_inline``
:Description: Send messages directly from the thread that generated them instead of
:Type: Boolean
:Required: No
:Default: ``false``
-
-
OPTION(ms_dump_on_send, OPT_BOOL) // hexdump msg to log on send
OPTION(ms_dump_corrupt_message_level, OPT_INT) // debug level to hexdump undecodeable messages at
OPTION(ms_async_op_threads, OPT_U64) // number of worker processing threads for async messenger created on init
-OPTION(ms_async_max_op_threads, OPT_U64) // max number of worker processing threads for async messenger
OPTION(ms_async_rdma_device_name, OPT_STR)
OPTION(ms_async_rdma_enable_hugepage, OPT_BOOL)
OPTION(ms_async_rdma_buffer_size, OPT_INT)
.set_min_max(1, 24)
.set_description("Threadpool size for AsyncMessenger (ms_type=async)"),
- Option("ms_async_max_op_threads", Option::TYPE_UINT, Option::LEVEL_ADVANCED)
- .set_default(5)
- .set_description("Maximum threadpool size of AsyncMessenger")
- .add_see_also("ms_async_op_threads"),
-
Option("ms_async_reap_threshold", Option::TYPE_UINT, Option::LEVEL_DEV)
.set_default(5)
.set_min(1)