Guys- If you want to drive AQM requirements into router/switch specification, count me in. We need to be careful to specify behaviors, as opposed to implementations. If we start to specify implementation details, the process will get bogged down in intractable differences. There is a lot of variability in what the existing hardware/software queueing components do, and we need to allow some leeway to "do the right thing" on the various platforms.
Given a good set of requirements, the community can both 1) work on next generation chipset/software/firmware/memory/board/architecture that do AQM in an optimum manner and 2) make (hopefully simple and well-bounded) changes to the existing software/firmware. Bvs -----Original Message----- From: bloat-boun...@lists.bufferbloat.net [mailto:bloat-boun...@lists.bufferbloat.net] On Behalf Of Mikael Abrahamsson Sent: Thursday, February 26, 2015 1:59 PM To: Dave Taht Cc: bloat@lists.bufferbloat.net Subject: Re: [Bloat] RED against bufferbloat On Thu, 26 Feb 2015, Dave Taht wrote: > First, everyone saying that fq_codel can't be done in hardware is > *wrong* See my last point far below, I know I write over-long emails... What do you define as "hardware"? > YES, at the lowest level of the hardware, where packets turn into > light or fuzzy electrons, or need to be tied up in a an aggregate (as > in > cable) and shipped onto the wire, you can't do it. BUT, as BQL has I am talking about doing this in the NPUs that are available on the market today and in the future. We're talking about these kinds of devices: http://www.tilera.com/News/PressRelease/?ezchip=97 I'm afraid that your experience with CPU driven devices isn't a great match here, and we're talking past each other. I would love to be able to use my employers purchasing power to drive demand on AQM, but I need to know what the requirements are, and that they're feasable to do, preferrably with an engineering effort for the vendor in the range of few man years. I can't produce this document myself, I have already tried pointing them in the direction of presentations etc, but I need "hard" documents, outlining exactly what they need to do. Do we have this currently? In that case, whereto should I point them? -- Mikael Abrahamsson email: swm...@swm.pp.se _______________________________________________ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat _______________________________________________ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat
