All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Andrew Morton <akpm@osdl.org>
Cc: Johannes Stezenbach <js@linuxtv.org>,
	dgc@sgi.com, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: dirty pages (Was: Re: [PATCH] Prevent large file writeback starvation)
Date: Mon, 13 Feb 2006 19:50:02 -0500	[thread overview]
Message-ID: <43F1293A.9050002@rtr.ca> (raw)
In-Reply-To: <43F11BA3.8060904@rtr.ca>

Mark Lord wrote:
> Andrew Morton wrote:
>> Johannes Stezenbach <js@linuxtv.org> wrote:
>>> On Mon, Feb 06, 2006, Andrew Morton wrote:
...
>>> Anyway, I temporarily deinstalled vmware (deleted the kernel
>>> modules and rebooted; kernel is still tainted because of madwifi
>>> if that matters).
>>> The behaviour I see with vmware (long 'sync' time) doesn't seem
>>> to happen without it so far ...
> 
> Mmm.. Okay, all of my machines normally have VMWare-WS installed on them,
> so that might just be the culprit.
...
> Mmm.. so the intent is to affect only VMWare itself, not the rest of the
> system while VMWare is dormant.  I guess it's time to disable loading of
> the VMWare modules and reboot.  Bye bye uptime!   Maybe I'll install
> 2.6.16-rc3 while I'm at it.
> 
> I'll follow-up with results in an hour or two.

Okay, results are non-conclusive, because 2.6.16-rc3-git1 breaks VMWare;
the vmmon module no longer compiles.  Unstable kernel non-API issue again.

So I'm back on 2.6.15 until that gets fixed.

Cheers

  reply	other threads:[~2006-02-14  0:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06  4:00 [PATCH] Prevent large file writeback starvation David Chinner
2006-02-06  4:27 ` Andrew Morton
2006-02-06  5:48   ` David Chinner
2006-02-06  6:22     ` Andrew Morton
2006-02-06  6:36       ` Andrew Morton
2006-02-06 11:57         ` David Chinner
2006-02-06 11:55       ` David Chinner
2006-02-06 23:14         ` Andrew Morton
2006-02-07  0:34           ` David Chinner
2006-02-07  1:04             ` Andrew Morton
2006-02-07  1:31               ` David Chinner
2006-02-07  5:27                 ` Andrew Morton
2006-02-07  7:42                   ` David Chinner
2006-02-07 22:51                     ` Andrew Morton
2006-02-07  7:49           ` David Chinner
2006-02-06 14:36   ` Mark Lord
2006-02-06 14:39     ` Mark Lord
2006-02-06 15:53       ` Several Hangs on diferent Hardwares and diferent kernels Pedro Alves
2006-02-06 20:11       ` [PATCH] Prevent large file writeback starvation Andrew Morton
2006-02-13 13:59         ` dirty pages (Was: Re: [PATCH] Prevent large file writeback starvation) Johannes Stezenbach
2006-02-13 20:08           ` Andrew Morton
2006-02-13 22:48             ` Johannes Stezenbach
2006-02-13 23:04               ` Andrew Morton
2006-02-13 23:31                 ` Johannes Stezenbach
2006-02-13 23:52             ` Mark Lord
2006-02-14  0:50               ` Mark Lord [this message]
2006-02-14 16:32               ` Mark Lord
2006-04-11 12:42           ` Alexander Bergolth
2006-03-20 22:40         ` [PATCH] Prevent large file writeback starvation Alexander Bergolth

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=43F1293A.9050002@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=akpm@osdl.org \
    --cc=dgc@sgi.com \
    --cc=js@linuxtv.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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.