On Fri, Aug 14, 2015 at 11:41:51AM +0300, Dan Carpenter wrote: > On Fri, Aug 14, 2015 at 11:09:17AM +0530, Sudip Mukherjee wrote: > > On Wed, Aug 12, 2015 at 05:40:28PM +0300, Dan Carpenter wrote: > > > On Wed, Aug 12, 2015 at 01:59:20PM +0530, Sudip Mukherjee wrote: <snip> > > >What kind of a computer are you using? RAM and > > > number of cores? Do you have hyperthreading? > > 64bit, 4 core, 8GB ram, CPU MHz: 3000.000 hyperthreading not there. > > Just one thing, your test_kernel.sh was taking NR_CPU as 4, I hardcoded > > that to 8. Can that be the problem? > > I don't think it is a good idea, but I haven't tested. Things end up > fighting over the CPU so it could be a slow down. Building the database > has been highly optimized by trial and error for my personal system. > > Anyway, reset the NR_CPU and let me know if it's compiling or buiding > the database which is the problem. I am seriously surprised. I deleted everything from smatch folder and did a reset --hard from git and then make. Also deleted the smatch sqlite file and the other two warn files from kernel sourse. $SCRIPT_DIR/test_kernel.sh --call-tree --info --param-mapper --spammy --data=$DATA_DIR took 1hr 20 min 49 sec for i in $SCRIPT_DIR/gen_* ; do $i smatch_warns.txt -p=kernel done took 20 min 52 sec $DATA_DIR/db/create_db.sh -p=kernel smatch_warns.txt took 44 min 29 sec how can there be this much difference? shall i try again with NR_CPU as 8? regards sudip -- To unsubscribe from this list: send the line "unsubscribe smatch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
