On Wed, Aug 01, 2012 at 08:40:52PM +0200, Hartmut Knaack wrote:
Hi,
my impression is, that a kernel version makes it into trunk if it is either a
long term kernel, or it brings essential new functions. For 3.3 this was most
certainly the introduction of BQL code. Keeping in mind that our
Hi,
due to several devs being on vacation atm I will keep this short. We
will drop a more complete statement start of next week.
3.3 was mainly chosen to get access to the bufferbloat related fixes.
The intent was to use this for the upcoming AA release.
We hope to push AA rather soon.
Hello,
I understand that a lot of effort has been pushed in making
Linux 3.3 the trunk kernel, and I understand that I probably
missed long (IRC?) discussions on this very subject, but since
3.3.8 is going to be the last supported kernel in the 3.3.x
branch it might be a good idea to move on
On 01/08/12 04:57 AM, Emmanuel Deloget wrote:
Hello,
I understand that a lot of effort has been pushed in making
Linux 3.3 the trunk kernel, and I understand that I probably
missed long (IRC?) discussions on this very subject, but since
3.3.8 is going to be the last supported kernel in
Hi,
my impression is, that a kernel version makes it into trunk if it is either a
long term kernel, or it brings essential new functions. For 3.3 this was most
certainly the introduction of BQL code. Keeping in mind that our main targets
are network routers, the bufferbloat issue probably
