netdev - Re: [PATCH V2] net/sched: sch_plug - Queue traffic until an explicit release command

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 Jan 2012 16:25:06 +0100
From:	Hagen Paul Pfeifer <hagen@...u.net>
To:	Shriram Rajagopalan <rshriram@...ubc.ca>
Cc:	Jamal Hadi Salim <jhs@...atatu.com>, " " <netdev@...r.kernel.org>,
	Brendan Cully <brendan@...ubc.ca>
Subject: Re: [PATCH V2] net/sched: sch_plug - Queue traffic until an explicit release command

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html