public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Thomas TESTASECCA" <thomas.testasecca@etictelecom.com>
To: "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
	"David Woodhouse" <dwmw2@infradead.org>
Cc: "Mtd" <linux-mtd@lists.infradead.org>,
	"Linux-Arm-Kernel@Lists. Arm. Linux. Org. Uk"
	<linux-arm-kernel@lists.arm.linux.org.uk>,
	"Der Herr Hofrat" <der.herr@mail.hofr.at>
Subject: RE: Scheduler, or task priority problem ... i need help
Date: Fri, 6 Sep 2002 16:19:21 +0200	[thread overview]
Message-ID: <AEEFILJDOOHJLBCFOBJDKEJJDAAA.thomas.testasecca@etictelecom.com> (raw)
In-Reply-To: <8622.1031245320@redhat.com>

Hi,
I have updated the MTD/JFFS2 drivers from current CVS, it works fine :)
Thanks for everything !!
greetings
TOM

-----Message d'origine-----
De : David Woodhouse [mailto:dwmw2@redhat.com]De la part de David
Woodhouse
Envoye : jeudi 5 septembre 2002 19:02
A : Russell King - ARM Linux
Cc : Der Herr Hofrat; Thomas TESTASECCA; Linux-Arm-Kernel@Lists. Arm.
Linux. Org. Uk
Objet : Re: Scheduler, or task priority problem ... i need help



linux@arm.linux.org.uk said:
>  I'd recommend that you talk to the jffs2 people (see other mailing
> lists) about this problem - jffs2 shouldn't suck all the CPU time in
> the world, especially when there are other higher-priority threads
> wanting to run.

The current CVS code did get sprinkled with cond_resched() fairly recently.
I suppose the 2.4 branch could do with the same.


--
dwmw2

       reply	other threads:[~2002-09-06 14:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8622.1031245320@redhat.com>
2002-09-06 14:19 ` Thomas TESTASECCA [this message]
2002-09-05  9:00 Scheduler, or task priority problem ... i need help Thomas TESTASECCA
2002-09-05  9:24 ` David Woodhouse
2002-09-05 13:57   ` Thomas TESTASECCA
2002-09-05 15:30     ` David Woodhouse

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=AEEFILJDOOHJLBCFOBJDKEJJDAAA.thomas.testasecca@etictelecom.com \
    --to=thomas.testasecca@etictelecom.com \
    --cc=der.herr@mail.hofr.at \
    --cc=dwmw2@infradead.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox