From: Krzysztof Halasa <khc@pm.waw.pl>
To: Walt Holman <walt@holmansrus.com>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Strange network timeouts w/ 2.6.30.5
Date: Fri, 21 Aug 2009 11:44:35 +0200 [thread overview]
Message-ID: <m3d46plcvw.fsf@intrepid.localdomain> (raw)
In-Reply-To: <322550336.131250806883202.JavaMail.root@mail.holmansrus.com> (Walt Holman's message of "Thu\, 20 Aug 2009 17\:21\:23 -0500 \(CDT\)")
Walt Holman <walt@holmansrus.com> writes:
> Would something like passing a mem=xx cmdline on x86_64 be sufficient to test this?
I think so, though I admit I don't remember using this personally since
the introduction of e820 RAM mapping support.
Dmesg will show if the memory is limited. For the swiotlb to effectively
disable no RAM > 0x100000000 may be used.
But this test isn't IMHO terribly important at this point - the driver
makes invalid use of the DMA API and it has to change. The test could
only explain _how_ exactly does it fail, we already know _why_ it does.
--
Krzysztof Halasa
next prev parent reply other threads:[~2009-08-21 9:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1359163732.51250769223038.JavaMail.root@mail.holmansrus.com>
2009-08-20 11:54 ` Strange network timeouts w/ 2.6.30.5 Walt Holman
2009-08-20 13:45 ` Krzysztof Halasa
2009-08-20 19:28 ` David Miller
2009-08-20 20:28 ` Krzysztof Halasa
2009-08-20 22:21 ` Walt Holman
2009-08-21 9:44 ` Krzysztof Halasa [this message]
2009-08-23 19:18 ` Aviv Greenberg
2009-08-23 20:02 ` Krzysztof Halasa
[not found] <1489093361.01250869377567.JavaMail.root@mail.holmansrus.com>
2009-08-21 15:45 ` Walt Holman
2009-08-22 20:26 ` Krzysztof Halasa
[not found] <1762204735.01250727555803.JavaMail.root@mail.holmansrus.com>
[not found] ` <2087985663.21250727676944.JavaMail.root@mail.holmansrus.com>
2009-08-20 4:17 ` David Miller
2009-08-20 9:03 ` Krzysztof Halasa
2009-08-20 9:13 ` David Miller
2009-08-20 9:22 ` Krzysztof Halasa
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=m3d46plcvw.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=walt@holmansrus.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;
as well as URLs for NNTP newsgroup(s).