# Re: htb parallelism on multi-core platforms 3 messages from 2009-04-23 to 2009-04-23. Participants: Jesper Dangaard Brouer, Jarek Poplawski, Jeff King. Thread: https://gitlist.dev/t/19027 ## Jesper Dangaard Brouer, 2009-04-23 19:47 Subject: Re: htb parallelism on multi-core platforms Message-ID: URL: https://gitlist.dev/e/Pine.LNX.4.64.0904232136040.13796%40ask.diku.dk In-Reply-To: <20090423191455.GC2756@ami.dom.local> ``` On Thu, 23 Apr 2009, Jarek Poplawski wrote: > On Thu, Apr 23, 2009 at 09:06:59PM +0200, Jesper Dangaard Brouer wrote: >> On Thu, 23 Apr 2009, Jarek Poplawski wrote: >> >>> Radu Rendec wrote, On 04/23/2009 02:31 PM: >>> >>>> On Wed, 2009-04-22 at 23:29 +0200, Jesper Dangaard Brouer wrote: >>> ... >>>>> The HTB classify hash has a scalability issue in kernels below 2.6.26. >>>>> Patrick McHardy fixes that up in 2.6.26. What kernel version are you >>>>> using? >>>> >>>> I'm using 2.6.26, so I guess the fix is already there :( >>> >>> If Jesper meant the change of hash I can see it in 2.6.27 yet. >> >> I'm referring to: >> >> commit f4c1f3e0c59be0e6566d9c00b1d8b204ffb861a2 >> Author: Patrick McHardy >> Date: Sat Jul 5 23:22:35 2008 -0700 >> >> net-sched: sch_htb: use dynamic class hash helpers >> >> Is there any easy git way to figure out which release this commit got >> into? > > I guess git-describe, but I prefer clicking at the "raw" (X-Git-Tag): > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=f4c1f3e0c59be0e6566d9c00b1d8b204ffb861a2 I think I prefer the command line edition "git-describe". But it seems that the two approaches gives a different results. (Cc'ing the git mailing list as they might know the reason) git-describe f4c1f3e0c59be0e6566d9c00b1d8b204ffb861a2 returns "v2.6.26-rc8-1107-gf4c1f3e" While you URL returns: "X-Git-Tag: v2.6.27-rc1~964^2~219" I also did a: "git log v2.6.26..v2.6.27 | grep f4c1f3e0c59be0e6566d9c00b1d8b204ffb861a2" commit f4c1f3e0c59be0e6566d9c00b1d8b204ffb861a2 To Radu: The change I talked about is in 2.6.27, so you should try that kernel on you system. Hilsen Jesper Brouer -- ------------------------------------------------------------------- MSc. Master of Computer Science Dept. of Computer Science, University of Copenhagen Author of http://www.adsl-optimizer.dk ------------------------------------------------------------------- ``` ## Jarek Poplawski, 2009-04-23 20:00 Subject: Re: htb parallelism on multi-core platforms Message-ID: <20090423200042.GD2756@ami.dom.local> URL: https://gitlist.dev/e/20090423200042.GD2756%40ami.dom.local In-Reply-To: ``` On Thu, Apr 23, 2009 at 09:47:05PM +0200, Jesper Dangaard Brouer wrote: > On Thu, 23 Apr 2009, Jarek Poplawski wrote: ... >> I guess git-describe, but I prefer clicking at the "raw" (X-Git-Tag): >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=f4c1f3e0c59be0e6566d9c00b1d8b204ffb861a2 > > I think I prefer the command line edition "git-describe". But it seems > that the two approaches gives a different results. Probably there is something more needed around this git-describe. I prefer the command line too when I can remember this command line... Jarek P. ``` ## Jeff King, 2009-04-23 20:09 Subject: Re: htb parallelism on multi-core platforms Message-ID: <20090423200932.GB3056@coredump.intra.peff.net> URL: https://gitlist.dev/e/20090423200932.GB3056%40coredump.intra.peff.net In-Reply-To: ``` On Thu, Apr 23, 2009 at 09:47:05PM +0200, Jesper Dangaard Brouer wrote: >>> Is there any easy git way to figure out which release this commit got >>> into? >> >> I guess git-describe, but I prefer clicking at the "raw" (X-Git-Tag): >> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=f4c1f3e0c59be0e6566d9c00b1d8b204ffb861a2 > > I think I prefer the command line edition "git-describe". But it seems > that the two approaches gives a different results. > (Cc'ing the git mailing list as they might know the reason) You want "git describe --contains". The default mode for describe is "you are at tag $X, plus $N commits, and by the way, the sha1 is $H" (shown as "$X-$N-g$H"). The default mode is useful for generating a unique semi-human-readable version number (e.g., to be included in your builds). -Peff ```