From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Shriram Rajagopalan <rshriram@cs.ubc.ca>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>, " " <netdev@vger.kernel.org>,
Brendan Cully <brendan@cs.ubc.ca>
Subject: Re: [PATCH V2] net/sched: sch_plug - Queue traffic until an explicit release command
Date: Tue, 31 Jan 2012 16:25:06 +0100 [thread overview]
Message-ID: <6790d1d5d8aa930222bbfc2ef6a9d48e@localhost> (raw)
In-Reply-To: <B99410E5-6E69-425A-913D-272058765A68@cs.ubc.ca>
On Mon, 30 Jan 2012 08:47:45 -0800, Shriram Rajagopalan wrote:
> Could you elaborate a little on the packet-based-unplug ?
>
> I got your earlier comment on "indefinite unplug" until an explicit
> plug is received. Is that what you mean by packet-based-unplug ?
Sure, imagine a multihop MANET network. Sometimes we have high-priority
crosstraffic in the next hop (router). Due to OLSR traffic information we
know in advance that the next hop is not in the ability to forward our low
priority packets. With this knowledge we can stop (unplug) local generated
and forwarded traffic and if the next hop has enough free bandwidth we can
restart (plug) sending already enqueued packets.
So for us a really simple plug/unplug mechanism is superior. Maybe a
head-drop FIFO based policy for forwarded traffic but I can provide a patch
on top of your patch to implement a head-drop policy.
Hagen
next prev parent reply other threads:[~2012-01-31 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 7:53 [PATCH V2] net/sched: sch_plug - Queue traffic until an explicit release command Shriram Rajagopalan
2012-01-29 17:25 ` Hagen Paul Pfeifer
2012-01-30 14:45 ` Jamal Hadi Salim
2012-01-30 14:54 ` Hagen Paul Pfeifer
2012-01-30 16:47 ` Shriram Rajagopalan
2012-01-31 15:25 ` Hagen Paul Pfeifer [this message]
2012-01-31 16:20 ` Shriram Rajagopalan
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=6790d1d5d8aa930222bbfc2ef6a9d48e@localhost \
--to=hagen@jauu.net \
--cc=brendan@cs.ubc.ca \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=rshriram@cs.ubc.ca \
/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).