All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: davem@davemloft.net
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
	Alexander Duyck <alexander.h.duyck@intel.com>,
	netdev@vger.kernel.org, herbert@gondor.apana.org.au,
	kaber@trash.net
Subject: Re: [take 2] Re: [RFC PATCH] sched: only dequeue if packet can be queued to hardware queue.
Date: Fri, 19 Sep 2008 19:46:03 +0200	[thread overview]
Message-ID: <48D3E55B.4030206@gmail.com> (raw)
In-Reply-To: <20080919103225.GB9135@ff.dom.local>

Jarek Poplawski wrote, On 09/19/2008 12:32 PM:

> Take 2:
> I missed __netif_schedule() in my patch, so the update below.


David,

After rethinking and reading Alexender's opinion I see this
change isn't needed so I withdraw this take 2.

Please, reconsider the first version of this patch (with your
2 patches), yet.

Thanks,
Jarek P.

  parent reply	other threads:[~2008-09-19 17:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18  6:43 [RFC PATCH] sched: only dequeue if packet can be queued to hardware queue Alexander Duyck
2008-09-18  6:56 ` Alexander Duyck
2008-09-18  9:46 ` David Miller
2008-09-18 14:51   ` Alexander Duyck
2008-09-18 19:44 ` Jarek Poplawski
2008-09-19  1:11   ` Alexander Duyck
2008-09-19  9:17     ` Jarek Poplawski
2008-09-19 10:32     ` [take 2] " Jarek Poplawski
2008-09-19 13:07       ` [PATCH] pkt_sched: Fix TX state checking in qdisc_run() Jarek Poplawski
2008-09-19 14:44       ` [PATCH take2] " Jarek Poplawski
2008-09-19 17:49         ` Jarek Poplawski
2008-09-21  5:18         ` David Miller
2008-09-19 17:46       ` Jarek Poplawski [this message]
2008-09-19 15:16   ` [RFC PATCH] sched: only dequeue if packet can be queued to hardware queue Jarek Poplawski
2008-09-19 16:26     ` Duyck, Alexander H
2008-09-19 17:35       ` Jarek Poplawski
2008-09-19 18:01         ` Duyck, Alexander H
2008-09-19 18:51           ` Jarek Poplawski
2008-09-19 21:43             ` Duyck, Alexander H
2008-09-19 16:37     ` Jarek Poplawski

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=48D3E55B.4030206@gmail.com \
    --to=jarkao2@gmail.com \
    --cc=alexander.duyck@gmail.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kaber@trash.net \
    --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 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.