Lines Matching refs:gro_flush_timeout

221 The ``gro_flush_timeout`` sysfs configuration of the netdevice
323 if ``gro_flush_timeout`` passes without any busy poll call. For epoll-based
336 It is important to note that choosing a large value for ``gro_flush_timeout``
339 ``gro_flush_timeout`` can cause interference of the user application which is
374   2. The sysfs parameter or per-NAPI config parameters ``gro_flush_timeout``
389 automatically disabled and the ``gro_flush_timeout`` and
393 than ``gro_flush_timeout`` as ``irq-suspend-timeout`` should suspend IRQs for
397 ``gro_flush_timeout`` to use IRQ suspension, their use is strongly
402 overrides ``gro_flush_timeout`` and keeps the system busy polling, but when
403 epoll finds no events, the setting of ``gro_flush_timeout`` and
413 Loop 2 can take control from Loop 1, if ``gro_flush_timeout`` and
416 If ``gro_flush_timeout`` and ``napi_defer_hard_irqs`` are set, Loops 2
422 If ``gro_flush_timeout`` and ``napi_defer_hard_irqs`` are not set, Loop 3
425 Therefore, setting ``gro_flush_timeout`` and ``napi_defer_hard_irqs`` is