From: Jarek Poplawski <jarkao2@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, Patrick McHardy <kaber@trash.net>
Subject: Re: [PATCH 0/9]: Killing qdisc->ops->requeue().
Date: Mon, 18 Aug 2008 09:21:38 +0000 [thread overview]
Message-ID: <20080818092138.GD5434@ff.dom.local> (raw)
In-Reply-To: <20080818.013640.254202527.davem@davemloft.net>
On Mon, Aug 18, 2008 at 01:36:40AM -0700, David Miller wrote:
>
> This implements what I tried to describe in previous
> emails.
>
> It gets rid of qdisc->ops->requeue() because logically it
> is completely superfluous. All it does is allow the
> next level to declare to the lower qdisc "send this next
> no matter what" and we can trivially do that with a simple
> list.
>
> Signed-off-by: David S. Miller <davem@davemloft.net>
David, I hope these patches are right, anyway I think I'll be able
to look at them later, after I figure out these new locking changes.
Of course, you don't need to wait for me.
But, I guess, much more important should be Patrick's opinion on
this, so I added him to CC.
Thanks,
Jarek P.
next prev parent reply other threads:[~2008-08-18 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 8:36 [PATCH 0/9]: Killing qdisc->ops->requeue() David Miller
2008-08-18 9:21 ` Jarek Poplawski [this message]
2008-08-18 9:28 ` David Miller
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=20080818092138.GD5434@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=davem@davemloft.net \
--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 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).