diff options
| author | Shrikrishna Khare <skhare@vmware.com> | 2016-06-16 19:51:56 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-06-17 07:37:04 +0200 |
| commit | 50a5ce3e7116a70edb7a1d1d209e3bc537752427 (patch) | |
| tree | cd7fae14e989039d2582da4ad7bf1e4006cf6bef /security | |
| parent | vmxnet3: allow variable length transmit data ring buffer (diff) | |
| download | linux-50a5ce3e7116a70edb7a1d1d209e3bc537752427.tar.xz linux-50a5ce3e7116a70edb7a1d1d209e3bc537752427.zip | |
vmxnet3: add receive data ring support
vmxnet3 driver preallocates buffers for receiving packets and posts the
buffers to the emulation. In order to deliver a received packet to the
guest, the emulation must map buffer(s) and copy the packet into it.
To avoid this memory mapping overhead, this patch introduces the receive
data ring - a set of small sized buffers that are always mapped by
the emulation. If a packet fits into the receive data ring buffer, the
emulation delivers the packet via the receive data ring (which must be
copied by the guest driver), or else the usual receive path is used.
Receive Data Ring buffer length is configurable via ethtool -G ethX rx-mini
Signed-off-by: Shrikrishna Khare <skhare@vmware.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions