Skip to content

Commit

Permalink
reactor_config: make it internal
Browse files Browse the repository at this point in the history
Said struct is now only used internally to configure individual reactor
instances in `smp::configure()`. So it should not be in the
documentation.
  • Loading branch information
denesb committed Nov 15, 2021
1 parent 869a9bb commit 6a9e3be
Showing 1 changed file with 3 additions and 18 deletions.
21 changes: 3 additions & 18 deletions include/seastar/core/reactor_config.hh
Original file line number Diff line number Diff line change
Expand Up @@ -27,27 +27,12 @@

namespace seastar {

/// Configuration structure for reactor
///
/// This structure provides configuration items for the reactor. It is typically
/// provided by \ref app_template, not the user.
/// \cond internal
struct reactor_config {
/// \brief Handle SIGINT/SIGTERM by calling reactor::stop()
///
/// When true, Seastar will set up signal handlers for SIGINT/SIGTERM that call
/// reactor::stop(). The reactor will then execute callbacks installed by
/// reactor::at_exit().
///
/// When false, Seastar will not set up signal handlers for SIGINT/SIGTERM
/// automatically. The default behavior (terminate the program) will be kept.
/// You can adjust the behavior of SIGINT/SIGTERM by installing signal handlers
/// via reactor::handle_signal().
bool auto_handle_sigint_sigterm = true; ///< automatically terminate on SIGINT/SIGTERM

/// Specifies the default value for linux-aio I/O control blocks. This translates
/// to the maximum number of sockets the shard can handle.
bool auto_handle_sigint_sigterm = true;
unsigned max_networking_aio_io_control_blocks = 10000;
};
/// \endcond

class reactor_backend_selector;
class network_stack_factory;
Expand Down

0 comments on commit 6a9e3be

Please sign in to comment.