On Fri, 2015-04-17 at 13:19 -0400, David Miller wrote:
> So the gist of the situation is, that NEED_DMA_MAP_STATE can be 'n' in
> situations where we might actually need it to be 'y' based upon kernel
> comman line boot options given.
>
> Right?
Yes.
>
>
__
On Thu, 2015-04-16 at 09:24 -0300, casca...@linux.vnet.ibm.com wrote:
> Yes, this looks like the driver is not syncing the DMA buffers. Unmap is
> supposed to synchronize as well.
>
For small rx packets (< 256 bytes), we sync the DMA buffer before we
copy the data to another SKB. For larger pac
On Thu, 2015-04-09 at 18:25 +0100, Ian Jackson wrote:
> root@bedbug:~# ethtool -S eth0 | grep -v ': 0$'
> NIC statistics:
> rx_octets: 8196868
> rx_ucast_packets: 633
> rx_mcast_packets: 1
> rx_bcast_packets: 123789
> tx_octets: 42854
> tx_ucast_packets: 9
> tx_mc
On Tue, 2015-04-07 at 19:13 +0100, Ian Jackson wrote:
> root@bedbug:~# ethtool -S xenbr0 | grep -v ': 0$'
> no stats available
> root@bedbug:~#
Please provide ethtool -S on the tg3 device.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://list
On Tue, 2015-04-07 at 16:12 +0100, Ian Jackson wrote:
> The symptom is a very high level of packet loss: around 25-30% (as
> seen in `ping'). There don't seem to be any untoward-looking kernel
> messages. The lost packets get added to the `errors' counter shown in
> ifconfig.
Please provide the
