[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JFFS2 is broken

Alan Cox wrote:

> One thing you can do here is to wake the gc thread and sleep politely on it
> > The only solution, that I think will work, is to find a way to block the
> > write() to JFFS2 but allow kernel schedduling to go on. I really don't
> > know
> Well there are two things there.
> 1.      You could wake the GC and sleep on it  using sleep/wakeup or
>         semaphores
> 2.      Profile the kernel and find out where it is tight looping. I can't
>         see any reason for tight loops except for the compression itself
>         so it suggests a code bug.
> Finally within the compression loops you can check current->need_resched and
> if it is set call schedule() to allow the compression to switch to other
> tasks at the point it has used its time slice.

If David is already looking at this, maybe I'll wait for a few days before
bumbling through the code myself ;) David? You've been awfully quite!


To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo@xxxxxxx.com