Skip to content
Tom Barbette edited this page Oct 3, 2018 · 3 revisions

FromNetmapDevice Element Documentation

NAME

FromNetmapDevice — Click element;

SYNOPSIS

FromNetmapDevice(DEVNAME [, QUEUE, NR_QUEUE, [, keywords PROMISC, BURST])
Receives packets using Netmap

Ports: no inputs, 1 output
Processing: push
Drivers: userlevel

DESCRIPTION

  • DEVNAME — String. Device number

  • QUEUE — Integer. A specific hardware queue to use. Default is 0.

  • N_QUEUES — Integer. Number of hardware queues to use. -1 or default is to use all available queues, as RSS is probably enabled and packet will come to all RX queues. Be noticed that using more than 1 queue per RX thread is useless in 99% of cases and you should use ethtool -L [interface] combined N or equivalent to ensure that.

  • PROMISC — Boolean. FromNetmapDevice puts the device in promiscuous mode if PROMISC is true. The default is false.

  • BURST — Unsigned integer. Maximal number of packets that will be processed before

    rescheduling Click default is 32.

  • MAXTHREADS — Maximal number of threads that this element will take to read packets from

    the input queue. If unset (or negative) all threads not pinned with a ThreadScheduler element will be shared among FromNetmapDevice elements and other input elements supporting multiqueue (extending QueueDevice)

  • THREADOFFSET — Define a number of assignable threads to ignore and do not use. Assignable threads are the one on the same numa node than this device (if NUMA is true)

    and not assigned to other elements using StaticThreadSched. Default is to share the threads available on the device's NUMA node equally.

  • VERBOSE — Amount of verbosity. If 1, display warnings about potential misconfigurations. If 2, display some informations. Default to 1.

Generated by click-elem2man from ../elements/userlevel/fromnetmapdevice.hh:18 on 2018/10/03.

Clone this wiki locally