From: Vipin Malik <vipin.malik@daniel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, jffs-dev <jffs-dev@axis.com>,
MTD for Linux <linux-mtd@lists.infradead.org>,
elw_dev_list@embeddedlinuxworks.com
Subject: Re: JFFS2 is broken
Date: Fri, 29 Jun 2001 09:13:52 -0500 [thread overview]
Message-ID: <3B3C8D20.CB1B56DD@daniel.com> (raw)
In-Reply-To: E15Fu8H-0008JI-00@the-village.bc.nu
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!
Vipin
next prev parent reply other threads:[~2001-06-29 14:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 0:14 JFFS2 is broken Vipin Malik
2001-06-29 2:32 ` Nicolas Pitre
2001-06-29 9:00 ` Alan Cox
2001-06-29 14:13 ` Vipin Malik [this message]
2001-07-01 19:10 ` David Woodhouse
2001-06-29 22:11 ` Vipin Malik
2001-08-09 17:00 ` A. Craig West
2001-08-09 22:36 ` Vipin Malik
-- strict thread matches above, loose matches on Subject: below --
2001-08-13 18:34 Frederic Giasson
[not found] <F1BED55F35F4D3118C0F00E0295CFF4D9955F7@webmail.mediatrix.c om>
2001-08-13 22:27 ` Vipin Malik
2001-08-14 0:00 ` David Woodhouse
2001-08-14 2:39 ` Vipin Malik
2001-08-14 16:46 Frederic Giasson
2001-08-14 17:39 Frederic Giasson
2001-08-14 17:57 Frederic Giasson
[not found] <F1BED55F35F4D3118C0F00E0295CFF4DD0DADF@webmail.mediatrix.c om>
2001-08-14 17:57 ` Vipin Malik
[not found] <F1BED55F35F4D3118C0F00E0295CFF4DD0DAE1@webmail.mediatrix.c om>
2001-08-14 21:57 ` Vipin Malik
2001-08-15 15:09 Frederic Giasson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B3C8D20.CB1B56DD@daniel.com \
--to=vipin.malik@daniel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwmw2@infradead.org \
--cc=elw_dev_list@embeddedlinuxworks.com \
--cc=jffs-dev@axis.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.