All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: krkumar2@in.ibm.com
Cc: yinghai@kernel.org, e1000-devel@lists.sourceforge.net,
	netdev@vger.kernel.org, netdev-owner@vger.kernel.org,
	avorontsov@ru.mvista.com, Sandeep.Kumar@freescale.com,
	galak@kernel.crashing.org
Subject: gianfar select_queue bogosity (was Re: ixgbe warning)
Date: Wed, 23 Dec 2009 21:11:57 -0800 (PST)	[thread overview]
Message-ID: <20091223.211157.68124463.davem@davemloft.net> (raw)
In-Reply-To: <OF748A4720.94B5A869-ON65257695.00267BA3-65257695.0027EDC4@in.ibm.com>

From: Krishna Kumar2 <krkumar2@in.ibm.com>
Date: Wed, 23 Dec 2009 12:57:26 +0530

> Also, I was looking at other providers of select_queue and found:
> 
> u16 gfar_select_queue(struct net_device *dev, struct sk_buff *skb)
> {
>         return skb_get_queue_mapping(skb);
> }
> 
> How can this be correct (driver supports upto 8 txq's). Unless txq=0 for
> xmits of all locally
> generated packets is fine.

This must be fixed.  As you note the queue mapping is only set
for forwarding/bridging cases.

There is zero reason for this driver to have it's own select_queue
function, so the fix seems to simply remove this thing altogether.

Some gianfar developer please prepare such a patch, thanks.

  parent reply	other threads:[~2009-12-24  5:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-23  5:00 ixgbe warning Yinghai Lu
2009-12-23  7:27 ` Krishna Kumar2
2009-12-23  8:15   ` Yinghai Lu
2009-12-23  8:58     ` Krishna Kumar2
2009-12-23  9:08       ` Krishna Kumar2
2009-12-24  5:11   ` David Miller [this message]
2009-12-24  6:04     ` gianfar select_queue bogosity (was Re: ixgbe warning) Kumar Gopalpet-B05799
2009-12-24  6:29       ` gianfar select_queue bogosity David Miller
2009-12-24  6:36         ` Kumar Gopalpet-B05799
2009-12-24  6:59           ` Krishna Kumar2
2009-12-24  6:51             ` Kumar Gopalpet-B05799
2009-12-24  6:34       ` gianfar select_queue bogosity (was Re: ixgbe warning) Krishna Kumar2

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=20091223.211157.68124463.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Sandeep.Kumar@freescale.com \
    --cc=avorontsov@ru.mvista.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=galak@kernel.crashing.org \
    --cc=krkumar2@in.ibm.com \
    --cc=netdev-owner@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yinghai@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.