[lc-devel] Read the dates on messages.

[John R M. <jm...@st...>]

Erm, because of my. . . awkward . . . situation, I can't exactly send 
replies.  I hate butchering the list and breaking the threading but I'm 
reading mail with Mozilla Thunderbird and sending it by shelling in to 
the server via ssh and using pine :/  College AIX box won't accept a 
RELAY request, even with authorization ><.

Read the dates on the messages.  It seems a few of you are responding to
my messages in reverse order.

A quick update as to how things are right now:

- There's a patch at sf.net/projects/linuxcompressed in patches.  I 
didn't send it to the mailing list, sorry.  I should have.  I'm a little 
rough to work with since I don't always get proceedure right but . . . 
erm.  At any rate, it's up there in the patches section.  RC can take it 
down if he wants.

- It works fine, just like the unmodified patch at runtime (except for 
the little sanity check I added when I was having trouble tracing the 
decompression bug).  The bug was an infinite loop I introduced.

- LZO IS HOPELESSLY BROKEN.  WKdm is fine.

- Large page sizes (16x for me) will cause a noticable lag in high-stress
situations, particularly in the fact that spin_lock() may occur in 50-200
mS intervals.  I'm trying to buff out the need for spin_lock()'s, which
will make the lag only be application lag.  I haven't confirmed that
anything >double has any effect, but I'm going to test later with octal
and quad.  I'll reflect the results in the Configure.help.  Be aware that
larger page sizes WILL have an effect for algorithms that are made for
larger sets of data; my box can do gzip on 256k faster than it can read
the data from disk, and such higher-intensity algorithms will have a
better trade-off on higher CPU boxes.  The page size should be tailored
for the algorithm you intend to use at compile time, which for the present
is probably going to be WKdm with 2x-8x pages

- I'm currently doing heavy rewrites of some things in here.  A few bad 
hacks are around in the patch to stave off my breakage of things.  
They'll probably persist through the next step, but I can get some of the 
things taken care of.

- other stuff I've forgotten, I'll get to it.

--Bluefox Icy