linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Dale Farnsworth" <dale@farnsworth.org>
To: joachim.bader@diehl-aerospace.de, Linuxppc-embedded@ozlabs.org
Subject: Re: [linux kernel 2.6.19] ethernet driver for Marvell bridge GT-64260
Date: 31 Aug 2007 09:43:43 -0700	[thread overview]
Message-ID: <20070831164343.452.qmail@farnsworth.org> (raw)
In-Reply-To: <OF71BAC825.59CE0529-ONC1257348.0056D44E-C1257348.0057BBA0@diehl-gruppe.de>

> 
> I am porting linux kernel 2.6.19 on a platform based on PPC750FX together 
> with a Marvell GT64260.
> I use a patched 643xx driver which is back ported to 64260 by Steven J. 
> Hill.
> I have ethernet now up and running, but only if I switch debug on, which 
> generates a big bunch of screen messages.
> As soon as I switch debug off, I get the message "Virtual device %s asks 
> to queue packet!" on every transmission request.
> 
> This happens on ping an other system.
> 
> Has anyone experience in such an event? Is there anything how I can speed 
> up performance with the 64260?
> Is there a similar problem known with the 64360?

No, this does not happen on the mv64360.  As I recall, that message occurs
when something attempts to queue a packet to a driver that has called
netif_stop_queue() but hasn't yet called netif_wake_queue().  I would
guess that when you turn debug on, you are changing the driver logic
in addition to the timing.

-Dale

  reply	other threads:[~2007-08-31 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 15:58 [linux kernel 2.6.19] ethernet driver for Marvell bridge GT-64260 joachim.bader
2007-08-31 16:43 ` Dale Farnsworth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-24 13:51 joachim.bader
2007-08-24 16:13 ` Dale Farnsworth

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=20070831164343.452.qmail@farnsworth.org \
    --to=dale@farnsworth.org \
    --cc=Linuxppc-embedded@ozlabs.org \
    --cc=joachim.bader@diehl-aerospace.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).