| 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
| ||
|
Message-Id: <1180542897.4109.81.camel@localhost> Date: Wed, 30 May 2007 12:34:57 -0400 From: jamal <hadi@...erus.ca> To: Patrick McHardy <kaber@...sh.net> Cc: netdev@...r.kernel.org Subject: Re: [RFC NET_SCHED 00/02]: Flexible SFQ flow classification On Wed, 2007-30-05 at 18:23 +0200, Patrick McHardy wrote: > I think exposing SFQ's queues as classes is a good thing, it allows > you to do whatever classification you want. In fact I'm probably > going to add patch on top to also dump them to userspace. Yes, that would be useful. > What > remains for SFQ to do is serve the queues evenly. And it does (yes, I looked at the patch;->). > My classifier seperates them entirely. The only thing it keeps > in SFQ is the old classifier for compatibility, besides that its > exactly what you say. It should be easily possible to remove it > entirely and use my classifier in a compatible configuration > automatically. > If you removed it entirely (and had it as a separate classifier) IMO that would be a better approach. Then what you have is a pure FQ qdisc. In which case, you leave alone SFQ and have a new qdisc. The "removed" hashing dynamic classifier would of course be better off it allowed the user to select a hash algorithm such as the other ones specified in ESFQ. cheers, jamal - 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
Powered by blists - more mailing lists