linux-toradex.git/drivers/net/virtio_net.c, branch v3.0.22

virtio_net: delay TX callbacks

2011-05-30T01:44:16+00:00

Ask for delayed callbacks on TX ring full, to give the
other side more of a chance to make progress.

Signed-off-by: Michael S. Tsirkin 
Acked-by: David S. Miller 
Signed-off-by: Rusty Russell

virtio_net: convert to hw_features

2011-04-02T03:53:35+00:00

Signed-off-by: Michał Mirosław 
Signed-off-by: David S. Miller

virtio_net: Add schedule check to napi_enable call

2011-02-10T19:03:31+00:00

Under harsh testing conditions, including low memory, the guest would
stop receiving packets. With this patch applied we no longer see any
problems in the driver while performing these tests for extended periods
of time.

Make sure napi is scheduled subsequent to each napi_enable.

Signed-off-by: Bruce Rogers 
Signed-off-by: Olaf Kirch 
Cc: stable@kernel.org
Signed-off-by: Rusty Russell 
Signed-off-by: David S. Miller

net: Use skb_checksum_start_offset()

2010-12-16T22:43:14+00:00

Replace skb->csum_start - skb_headroom(skb) with skb_checksum_start_offset().

Note for usb/smsc95xx: skb->data - skb->head == skb_headroom(skb).

Signed-off-by: Michał Mirosław 
Signed-off-by: David S. Miller

virtio-net: init link state correctly

2010-11-12T20:21:18+00:00

For device that supports VIRTIO_NET_F_STATUS, there's no need to
assume the link is up and we need to call nerif_carrier_off() before
querying device status, otherwise we may get wrong operstate after
diver was loaded because the link watch event was not fired as
expected.

For device that does not support VIRITO_NET_F_STATUS, we could not get
its status through virtnet_update_status() and what we can only do is
always assuming the link is up.

Acked-by: Michael S. Tsirkin 
Signed-off-by: Jason Wang 
Signed-off-by: Rusty Russell 
Signed-off-by: David S. Miller

ethtool: Provide a default implementation of ethtool_ops::get_drvinfo

2010-08-17T09:31:15+00:00

The driver name and bus address for a net_device can normally be found
through the driver model now.  Instead of requiring drivers to provide
this information redundantly through the ethtool_ops::get_drvinfo
operation, use the driver model to do so if the driver does not define
the operation.  Since ETHTOOL_GDRVINFO no longer requires the driver
to implement any operations, do not require net_device::ethtool_ops to
be set either.

Remove implementations of get_drvinfo and ethtool_ops that provide
only this information.

Signed-off-by: Ben Hutchings 
Signed-off-by: David S. Miller

virtio_net: implements ethtool_ops.get_drvinfo

2010-08-05T04:53:17+00:00

I often use "ethtool -i" command to check what driver controls the
ehternet device.  But because current virtio_net driver doesn't
support "ethtool -i", it becomes the following:

        # ethtool -i eth3
        Cannot get driver information: Operation not supported

This patch simply adds the "ethtool -i" support. The following is the
result when using the virtio_net driver with my patch applied to.

        # ethtool -i eth3
        driver: virtio_net
        version: N/A
        firmware-version: N/A
        bus-info: virtio0

Personally, "-i" is one of the most frequently-used option, and most
network drivers support "ethtool -i", so I think virtio_net also
should do.

Signed-off-by: Taku Izumi 
Signed-off-by: Rusty Russell  (use ARRAY_SIZE)
Signed-off-by: David S. Miller

virtio_net: fix oom handling on tx

2010-07-03T05:27:26+00:00

virtio net will never try to overflow the TX ring, so the only reason
add_buf may fail is out of memory. Thus, we can not stop the
device until some request completes - there's no guarantee anything
at all is outstanding.

Make the error message clearer as well: error here does not
indicate queue full.

Signed-off-by: Michael S. Tsirkin 
Signed-off-by: Rusty Russell  (...and avoid TX_BUSY)
Cc: stable@kernel.org  # .34.x (s/virtqueue_/vi->svq->vq_ops->/)
Signed-off-by: David S. Miller

virtio_net: do not reschedule rx refill forever

2010-07-03T05:27:25+00:00

We currently fill all of RX ring, then add_buf
returns ENOSPC, which gets mis-detected as an out of
memory condition and causes us to reschedule the work,
and so on forever. Fix this by oom = err == -ENOMEM;

Signed-off-by: Michael S. Tsirkin 
Signed-off-by: Rusty Russell 
Cc: stable@kernel.org # .34.x
Signed-off-by: David S. Miller

virtio-net: pass gfp to add_buf

2010-06-01T07:21:20+00:00

virtio-net bounces buffer allocations off to
a thread if it can't allocate buffers from the atomic
pool. However, if posting buffers still requires atomic
buffers, this is unlikely to succeed.
Fix by passing in the proper gfp_t parameter.

Signed-off-by: Michael S. Tsirkin 
Signed-off-by: Rusty Russell 
Signed-off-by: David S. Miller