From: Jeff Mock <jeff@mock.com>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: PPC440GX ethernet oddities
Date: Mon, 27 Nov 2006 09:39:07 -0800 [thread overview]
Message-ID: <456B22BB.7060301@mock.com> (raw)
In-Reply-To: <20061127071454.93C73353A44@atlas.denx.de>
Wolfgang Denk wrote:
> In message <456A641D.7070904@mock.com> you wrote:
>> Here's the weird part. On one of the four prototype boxes, if I plug
>> the second ethernet port into gigabit switch and get a link light (2nd
>> interface is not enabled under linux), the DMA behavior will change and
>> I can see the ring buffer get as large as 25MB (up from 512kB!)
>>
>> Only one of my four boxes shows this strange behavior, and only when the
>> second ethernet port is connected to an ethernet switch. Everything
>
> Are you using exactly the same switch, and the same port on the
> switch, and the same network cable with all of your boxen?
>
Yeah, I'm using the same switch, cables, and server machines for these
tests. I've done quite a lot of fiddling with servers, cables, and
switches looking for some differential behavior, but the only thing I
find is that with second ethernet port unconnected, my ring buffer will
consistently only fill to 512kB, but with the second ethernet port
connect to get a link light (disabled under linux), the ring buffer will
get as full as 25MB over time.
jeff
prev parent reply other threads:[~2006-11-27 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 4:05 PPC440GX ethernet oddities Jeff Mock
2006-11-27 4:25 ` Eugene Surovegin
2006-11-27 17:34 ` Jeff Mock
2006-11-27 20:18 ` Eugene Surovegin
2006-11-27 22:19 ` Jeff Mock
2006-11-27 22:44 ` Eugene Surovegin
2006-11-27 7:14 ` Wolfgang Denk
2006-11-27 17:39 ` Jeff Mock [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=456B22BB.7060301@mock.com \
--to=jeff@mock.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@denx.de \
/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).