netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: Krishna Kumar <krkumar2@in.ibm.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
	netdev@vger.kernel.org, Jarek Poplawski <jarkao2@gmail.com>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [RFC] [PATCH] Don't run __qdisc_run() on a stopped TX queue
Date: Fri, 24 Jul 2009 14:46:06 +0200	[thread overview]
Message-ID: <4A69AD0E.4020701@cosmosbay.com> (raw)
In-Reply-To: <20090720074607.32463.23013.sendpatchset@localhost.localdomain>

Krishna Kumar a écrit :
> From: Krishna Kumar <krkumar2@in.ibm.com>
> diff -ruNp org/net/sched/sch_generic.c new/net/sched/sch_generic.c
> --- org/net/sched/sch_generic.c	2009-05-25 07:48:07.000000000 +0530
> +++ new/net/sched/sch_generic.c	2009-07-20 13:09:18.000000000 +0530
> @@ -56,12 +56,8 @@ static inline struct sk_buff *dequeue_sk
>  	struct sk_buff *skb = q->gso_skb;
>  
>  	if (unlikely(skb)) {
> -		struct net_device *dev = qdisc_dev(q);
> -		struct netdev_queue *txq;
> -
>  		/* check the reason of requeuing without tx lock first */
> -		txq = netdev_get_tx_queue(dev, skb_get_queue_mapping(skb));
> -		if (!netif_tx_queue_stopped(txq) && !netif_tx_queue_frozen(txq))
> +		if (!netif_tx_queue_frozen(q->dev_queue))
>  			q->gso_skb = NULL;

This part might be a separate patch...

Are we sure these are equivalent ?

OLD)
	struct net_device *dev = qdisc_dev(q);
	struct netdev_queue *txq;
	txq = netdev_get_tx_queue(dev, skb_get_queue_mapping(skb));

NEW)
	struct netdev_queue *txq = q->dev_queue;


  parent reply	other threads:[~2009-07-24 12:46 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20  7:46 [RFC] [PATCH] Don't run __qdisc_run() on a stopped TX queue Krishna Kumar
2009-07-24  8:30 ` Jarek Poplawski
2009-07-24  8:37   ` Herbert Xu
2009-07-24 10:31     ` Krishna Kumar2
2009-07-25  3:24       ` Herbert Xu
2009-07-25 11:04         ` Jarek Poplawski
2009-07-25 11:12           ` Herbert Xu
2009-07-25 11:53             ` Jarek Poplawski
2009-07-28  2:28         ` David Miller
2009-07-28  2:48           ` Herbert Xu
2009-07-28  4:21             ` David Miller
2009-07-28  6:43               ` Jarek Poplawski
2009-07-28  8:03                 ` Herbert Xu
2009-07-28  8:37                   ` Jarek Poplawski
2009-07-28  8:44                     ` Herbert Xu
2009-07-28  9:02                       ` Jarek Poplawski
2009-07-28 10:53                         ` Herbert Xu
2009-07-28 11:24                           ` Jarek Poplawski
2009-07-28 11:43                             ` Krishna Kumar2
2009-07-28 11:48                               ` Herbert Xu
2009-07-28 12:24                                 ` Krishna Kumar2
2009-07-28 20:02                       ` David Miller
2009-07-28  7:12               ` Herbert Xu
2009-07-28 19:59                 ` David Miller
2009-07-29  0:44                   ` Herbert Xu
2009-07-29  1:06                     ` David Miller
2009-07-29  1:25                       ` Herbert Xu
2009-07-29  1:34                         ` David Miller
2009-07-29  2:12                           ` Herbert Xu
2009-07-29  2:22                             ` David Miller
2009-07-29  2:38                               ` Herbert Xu
2009-07-29  3:15                                 ` Herbert Xu
2009-08-04  3:15                                   ` David Miller
2009-07-29 11:04                     ` Jarek Poplawski
2009-07-29 11:11                       ` Herbert Xu
2009-07-29 11:26                         ` Jarek Poplawski
2009-07-29 12:30                           ` Herbert Xu
2009-07-29 12:47                             ` Jarek Poplawski
2009-07-29 13:08                               ` Krishna Kumar2
2009-07-29 19:26                                 ` Jarek Poplawski
2009-07-29 13:28                     ` Krishna Kumar2
2009-07-24 12:46 ` Eric Dumazet [this message]
2009-07-24 14:54   ` Herbert Xu

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=4A69AD0E.4020701@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jarkao2@gmail.com \
    --cc=krkumar2@in.ibm.com \
    --cc=netdev@vger.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 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).