public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frieder Buerzele <stamm@flashmail.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7-np2
Date: Thu, 01 Jul 2004 00:59:08 +0200	[thread overview]
Message-ID: <40E345BC.2070008@flashmail.com> (raw)
In-Reply-To: <40E00EA4.8060205@yahoo.com.au>

must I still renice X to get your patch run without responsive-lose 
during I/O e.g with cdparanoia?
thx

I had to edit fs/hfsplus/inode.c to get it compile properly

--- fs/hfsplus/inode.c.orig     2004-07-01 00:51:52.347198744 +0200
+++ fs/hfsplus/inode.c  2004-07-01 00:42:00.685145048 +0200
@@ -72,7 +72,7 @@
                                res = 0;
                        else for (i = 0; i < tree->pages_per_bnode; i++) {
                                if (PageActiveMapped(node->page[i]) ||
-                                       
PageActiveUnmapped(node->page[i]))) {
+                                       PageActiveUnmapped(node->page[i])) {
                                        res = 0;
                                        break;


Nick Piggin wrote:

> http://www.kerneltrap.org/~npiggin/2.6.7-np2.gz
>
> This is against 2.6.7-mm3. I can do one against -bk if anyone would
> like.
>
> It should fix scheduler problems and compile problems in 2.6.7-np1.
>
> It contains my CPU scheduler and memory management stuff. If anyone
> is having swapping or interactivity problems, please try it out.


  parent reply	other threads:[~2004-06-30 22:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-28 12:27 2.6.7-np2 Nick Piggin
2004-06-28 15:34 ` 2.6.7-np2 Norberto Bensa
2004-06-29  4:29   ` 2.6.7-np2 Nick Piggin
2004-06-28 18:32 ` 2.6.7-np2 Markus Hästbacka
2004-06-29  4:28   ` 2.6.7-np2 Nick Piggin
2004-06-30 22:59 ` Frieder Buerzele [this message]
2004-07-01  5:53   ` 2.6.7-np2 Nick Piggin

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=40E345BC.2070008@flashmail.com \
    --to=stamm@flashmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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