> when these messages appear, removing r8169 would appear to be key. Indeed, if
> there is no significant libata activity, the problem still occurs on the NIC
> within approximately the same amount of transfer.
You seem to have a leak, which actually isn't suprising
rtl8169_xmit_frags allocates a set of maps for a fragmented packet
rtl8169_start_xmit allocates a buffer
When we finish the transit we free the main buffer (always using skb->len
when sometimes its skb->headlne. We don't seem to free the fragment
buffers at all.
Looks like the unmap path for fragmented packets is broken with any kind
of iommu
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Prev by Date:
Re: 2.6.24-rc3, 4GB RAM, swiotlb, r8169, out of space
- Next by Date:
NFSv3 bug: F_SETLEASE/F_WRLCK active on file causes it to appear modified over NVSv3 mount
- Previous by thread:
Re: 2.6.24-rc3, 4GB RAM, swiotlb, r8169, out of space
- Next by thread:
Re: 2.6.24-rc3, 4GB RAM, swiotlb, r8169, out of space
- Index(es):
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
