From: Mike Galbraith <efault@gmx.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
bfennema@falcon.csc.calpoly.edu
Subject: Re: [vm] writing to UDF DVD+RW (/dev/sr0) while under memory pressure: box ==> doorstop
Date: Thu, 10 Jan 2008 05:21:25 +0100 [thread overview]
Message-ID: <1199938885.4324.80.camel@homer.simson.net> (raw)
In-Reply-To: <20080109150139.311f68d3.akpm@linux-foundation.org>
On Wed, 2008-01-09 at 15:01 -0800, Andrew Morton wrote:
> So are you saying that the fs throughput is unaltered by this change,
> but that the side-effects which your workload has on the overall
> machine are lessened?
Yes. UDF IO is still a slow trickle, but the box is now fine under VM
stress, vs all allocating tasks eventually getting nailed (essentially
forever) by iprune_mutex previously.
-Mike
P.S. I would submit one-liner for VFS part, but it's useless without
UDF part, and nobody is hitting what I ran into while testing alleged
scsi_done regression thingy anyway. cc added.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-01-10 4:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1199447212.4529.13.camel@homer.simson.net>
[not found] ` <1199612533.4384.54.camel@homer.simson.net>
[not found] ` <1199642470.3927.12.camel@homer.simson.net>
[not found] ` <20080106122954.d8f04c98.akpm@linux-foundation.org>
[not found] ` <1199790316.4094.57.camel@homer.simson.net>
[not found] ` <20080108033801.40d0043a.akpm@linux-foundation.org>
[not found] ` <1199805713.3571.12.camel@homer.simson.net>
[not found] ` <1199806071.4174.2.camel@homer.simson.net>
2008-01-09 11:11 ` Mike Galbraith
2008-01-09 23:01 ` Andrew Morton
2008-01-10 4:21 ` Mike Galbraith [this message]
2008-01-10 14:41 ` Jan Kara
2008-01-10 15:29 ` Mike Galbraith
2008-01-10 17:16 ` Jan Kara
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=1199938885.4324.80.camel@homer.simson.net \
--to=efault@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=bfennema@falcon.csc.calpoly.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox