I've also been experiencing these problems. I thought it was just a performance deficiency of Linux as a whole rather than attributing it to love-sources (I just started using linux fulltime in late 2003/early 2004, and love-sources has been my kernel since I've started. I was only using a kernel without nick's scheduler for a short amount of time before). This will be interesting to experiment with (eg the lack of pre-emptable kernels).(for example compiling kernel on background with web surfing/mp3 takes twice the time to complete, heavy disk load gets the machine to its knees...)
Hmm... interesting. I may be experiencing something of an isolated case thened0n wrote:It works here.
Code: Select all
#!/bin/bash
love_url="http://www.public.iastate.edu/~jpcox"
for patchdir in patches ../patches
do
[ -d "$patchdir" ] && cd "$patchdir" && break
done
set -- `wget -q -O - "$love_url/?M=D" \
| grep "HREF" | grep ".bz2" | head -n1`
file=${6/>*/}
file=${file/'HREF='/}
file=${file//\"/}
if [ ! -f "$patchdir/$file" ]
then
wget "$love_url/$file"
echo
echo "$file downloaded."
else
echo "$file already exists."
fi
looks to me like an -mm problem...- Added the DRM development tree to -mm kernel. Please Cc
dri-devel@lists.sourceforge.net on any bug reports.
Andrea Arcangeli wrote:"...keep preempt turned off always, it's useless..."
"...preempt just wastes cpu with tons of branches in fast paths that should take one cycle instead..."
"...Takashi Iwai did lots of research on the preempt vs lowlatency and he found that preempt buys nothing..."
"...infact 2.4-aa has a lower max latency than 2.6 stock with preempt enabled..."
"...Sure, I agree it improves average latency, the problem is that there are nearly no application that cares about average, what matters is the worst case latency only..."
"...PREEMPT=y doesn't and cannot improve the worst case latency. This is true today like it was true 4 years ago..."
Adrew Morton wrote:Preempt is overrated. The infrastructure which it has introduced has been useful for detecting locking bugs.
It has been demonstrated that preempt improves the average latency. But not worst-case, because those paths tend to be under spinlock.
Quotes taken from this kerneltrap-story.Robert Love wrote:Yes, the absolute worst case latency probably remains because it tends to occur under lock.
For those of you that cannot compile drivers (ati-drivers, vmware... etc), this solution works.Zviratko wrote:I got vmware and ndiswrapper to compile!!
Replaced scripts/Makefile.modpost and /usr/src/linux/Makefile with respective files from -love3 and everything works....
I recommend switching them back if you want to recompile your kernel though

If everything works for you, then that's great. However, you didn't catch all the related changes.Zviratko wrote:I got vmware and ndiswrapper to compile!!
Replaced scripts/Makefile.modpost and /usr/src/linux/Makefile with respective files from -love3 and everything works....
I recommend switching them back if you want to recompile your kernel though

AFAICT it is performing well. I'm primarily interested in the new C++ parser, but there are a lot of other improvements too. Visit http://gcc.gnu.org/gcc-3.4/changes.html for further details.ktech wrote:OFF-Topic, but... how is gcc 3.4 performing in gentoo?Markus_T wrote:Working fine here with:
CONFIG_CFLAGS_STRING="-O3 -funroll-loops -fpeel-loops -funswitch-loops"
and gcc 3.4.0
