netdev - Re: [PATCH 20/31]: pkt_sched: Perform bulk of qdisc destruction in RCU.

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 18 Jul 2008 14:05:39 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	hadi@...erus.ca
Cc:	kaber@...sh.net, netdev@...r.kernel.org, johannes@...solutions.net,
	linux-wireless@...r.kernel.org
Subject: Re: [PATCH 20/31]: pkt_sched: Perform bulk of qdisc destruction in
 RCU.

From: jamal <hadi@...erus.ca>
Date: Fri, 18 Jul 2008 09:27:21 -0400

> On Fri, 2008-18-07 at 09:10 -0400, jamal wrote:
> 
> > wire still even on multiple rings;->
> > If Woz (really) showed up at 9am and the Broussards at 3 am[1] on that
> > single (congestion-buffering) FIFO waiting for the shop/wire to open up,
> > then Woz should jump the queue (if he deserves it) when shop opens at
> > 10am.
> 
> Sorry, the url of Woz allegedly jumping the queue:
> http://news.cnet.com/8301-1023_3-9989823-93.html?hhTest=1%C3%A2%C2%88%
> C2%82=rss&subj=news&tag=2547-1_3-0-20

The fundamental issue is what we believe qdiscs schedule, do they
schedule a device, or do they schedule what their namesake implies,
"queues"?

Logically once we have multiple queues, we schedule queues.

Therefore what probably makes sense is that for mostly stateless
priority queueing such as pfifo_fast, doing prioritization at the
queue level is OK.

But where non-trivial classification occurs, we have to either:

1) Make the queue selection match what the classifiers would do
   exactly.

OR

2) Point all the queues at a single device global qdisc.

What we have now implements #2.  Later on we can try to do something
as sophisticated as #1.

--
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