From: Nathan Grennan <alistair@cygnusx-1.org>
To: Francois Romieu <romieu@fr.zoreil.com>,
Alistair John Strachan <alistair@devzero.co.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-net@vger.kernel.org
Subject: Re: r8169 and out of space
Date: Thu, 10 Jan 2008 20:54:05 -0800 [thread overview]
Message-ID: <4786F66D.1060903@cygnusx-1.org> (raw)
In-Reply-To: <20080110205727.GA8692@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Alistair John Strachan <alistair@devzero.co.uk> :
> [..]
>
>> No, we have not diagnosed the cause of the problem, beyond the swiotlb usage.
>> I'm adding the r8169 maintainer, linux-net and linux-kernel to CC, to pass on
>> your information, I hope you don't mind.
>>
>
> swiotlb fragmentation perhaps ?
>
> Switching the driver to be page based on Rx would help then.
>
> [...]
>
>>> I have a Abit AB9 Pro motherboard with Intel P965 chipset, 4gb of
>>> memory, and two onboard r8169.
>>>
>
> Which r8169 model exactly ?
>
>
I seem to have been wrong about the kernel update fixing my mtu issue.
I am not 100% sure, but I think 7200 works if the forcedeth system is
sending, but not if the r8169 system is sending.
I tried a mtu of 3000, and basically the same errors, but I did
noticed something interesting. Note the three different byte sizes.
DMA: Out of SW-IOMMU space for 2410 bytes at device 0000:03:00.0
DMA: Out of SW-IOMMU space for 3014 bytes at device 0000:03:00.0
DMA: Out of SW-IOMMU space for 3014 bytes at device 0000:03:00.0
DMA: Out of SW-IOMMU space for 3022 bytes at device 0000:03:00.0
On a side note, leaving the mtu at 1500 seems to work without error,
and I get about the same performance.
prev parent reply other threads:[~2008-01-11 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <478655B6.6010406@cygnusx-1.org>
2008-01-10 19:20 ` r8169 and out of space Alistair John Strachan
2008-01-10 20:57 ` Francois Romieu
2008-01-10 21:39 ` Nathan Grennan
2008-01-11 4:54 ` Nathan Grennan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4786F66D.1060903@cygnusx-1.org \
--to=alistair@cygnusx-1.org \
--cc=alistair@devzero.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox