linux-toradex.git/drivers/net/vmxnet3/vmxnet3_defs.h, branch v4.10

vmxnet3: introduce command to register memory region

2016-06-17T05:37:05+00:00

In vmxnet3 version 3, the emulation added support for the vmxnet3 driver
to communicate information about the memory regions the driver will use
for rx/tx buffers. The driver can also indicate which rx/tx queue the
memory region is applicable for. If this information is communicated
to the emulation, the emulation will always keep these memory regions
mapped, thereby avoiding the mapping/unmapping overhead for every packet.

Currently, Linux vmxnet3 driver does not leverage this capability. The
feasibility of using this approach for the Linux vmxnet3 driver will be
investigated independently and if possible, will be part of a different
patch. This patch only exposes the emulation capability to the driver
(vmxnet3_defs.h is identical between the driver and the emulation).

Signed-off-by: Guolin Yang 
Signed-off-by: Shrikrishna Khare 
Signed-off-by: David S. Miller

vmxnet3: add support for get_coalesce, set_coalesce ethtool operations

2016-06-17T05:37:04+00:00

The emulation supports a variety of coalescing modes viz. disabled
(no coalescing), adaptive, static (number of packets to batch before
raising an interrupt), rate based (number of interrupts per second).

This patch implements get_coalesce and set_coalesce methods to allow
querying and configuring different coalescing modes.

Signed-off-by: Keyong Sun 
Signed-off-by: Manoj Tammali 
Signed-off-by: Shrikrishna Khare 
Signed-off-by: David S. Miller

vmxnet3: add receive data ring support

2016-06-17T05:37:04+00:00

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 
Signed-off-by: David S. Miller

vmxnet3: allow variable length transmit data ring buffer

2016-06-17T05:37:04+00:00

vmxnet3 driver supports transmit data ring viz. a set of fixed size
buffers used by the driver to copy packet headers. Small packets that
fit these buffers are copied into these buffers entirely.

Currently this buffer size of fixed at 128 bytes. This patch extends
transmit data ring implementation to allow variable length transmit
data ring buffers. The length of the buffer is read from the emulation
during initialization.

Signed-off-by: Sriram Rangarajan 
Signed-off-by: Shrikrishna Khare 
Signed-off-by: David S. Miller

vmxnet3: introduce generalized command interface to configure the device

2016-06-17T05:37:04+00:00

Shared memory is used to exchange information between the vmxnet3 driver
and the emulation. In order to request emulation to perform a task, the
driver first populates specific fields in this shared memory and then
issues corresponding command by writing to the command register(CMD). The
layout of the shared memory was defined by vmxnet3 version 1 and cannot
be extended for every new command without breaking backward compatibility.

To address this problem, in vmxnet3 version 3, the emulation repurposed
a reserved field in the shared memory to represent command information
instead. For new commands, the driver first populates the command
information field in the shared memory and then issues the command. The
emulation interprets the data written to the command information depending
on the type of the command. This patch exposes this capability to the driver.

Signed-off-by: Guolin Yang 
Signed-off-by: Shrikrishna Khare 
Signed-off-by: David S. Miller

vmxnet3: prepare for version 3 changes

2016-06-17T05:37:04+00:00

vmxnet3 is currently at version 2, but some command definitions from
previous vmxnet3 versions are missing. Add those definitions before
moving to version 3.

Also, introduce utility macros for vmxnet3 version comparison and update
Copyright information and Maintained by.

Signed-off-by: Shrikrishna Khare 
Signed-off-by: David S. Miller

Driver: Vmxnet3: Update Rx ring 2 max size

2016-02-22T03:04:15+00:00

Device emulation supports max size of 4096.

Signed-off-by: Shrikrishna Khare 
Signed-off-by: Bhavesh Davda 
Signed-off-by: David S. Miller

vmxnet3: Changes for vmxnet3 adapter version 2 (fwd)

2015-06-23T13:26:01+00:00

Make the driver understand adapter version 2.

Cc: Rachel Lunnon 
Signed-off-by: Guolin Yang 
Signed-off-by: Shreyas N Bhatewara 
Signed-off-by: David S. Miller

Driver: Vmxnet3: Change the hex constant to its decimal equivalent

2015-02-09T00:55:01+00:00

The hex constant chosen for VMXNET3_REV1_MAGIC is offensive,
replace it with its decimal equivalent.

Signed-off-by: Shrikrishna Khare 
Reviewed-by: Shreyas Bhatewara 
Signed-off-by: David S. Miller

Driver: Vmxnet3: Make Rx ring 2 size configurable

2015-01-06T19:15:16+00:00

Rx ring 2 size can be configured by adjusting rx-jumbo parameter
of ethtool -G.

Signed-off-by: Ramya Bolla 
Signed-off-by: Shreyas Bhatewara 
Signed-off-by: Shrikrishna Khare 
Signed-off-by: David S. Miller