From: Andrew Morton <akpm@linux-foundation.org>
To: linux-mm@kvack.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [Bugme-new] [Bug 16321] New: os unresponsive during buffered I/O
Date: Fri, 2 Jul 2010 16:05:01 -0700 [thread overview]
Message-ID: <20100702160501.45861821.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-16321-10286@https.bugzilla.kernel.org/>
On Thu, 1 Jul 2010 11:57:37 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=16321
>
> Summary: os unresponsive during buffered I/O
> Product: IO/Storage
> Version: 2.5
> Kernel Version: 2.6.34
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Block Layer
> AssignedTo: axboe@kernel.dk
> ReportedBy: rrs@researchut.com
> Regression: No
>
>
> I have been running these tests on my laptop running the 2.6.34 Debian kernel.
> When doing buffered I/O, the OS completely stalls to any interactivity. I
> cannot switch console tabs in my Desktop Environment and the mouse pointer does
> not move.
>
> Eventually, I/O completes and every thing resumes to normal. There is no OOM
> seen during the I/O operation.
> If doing direct I/O, interactivity does not get penalized.
>
1...
2...
3...
FUCK!!!
We've been trying to fix this stuff for ten years. Apparently, without
success. Do we suck, or what?
--
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 parent reply other threads:[~2010-07-02 23:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16321-10286@https.bugzilla.kernel.org/>
2010-07-02 23:05 ` Andrew Morton [this message]
2010-07-03 11:56 ` [Bugme-new] [Bug 16321] New: os unresponsive during buffered I/O Jens Axboe
2010-07-03 15:16 ` Andrew Morton
2010-07-03 19:55 ` Avi Kivity
2010-07-20 4:10 ` Andrew Morton
2010-07-20 15:08 ` Christoph Hellwig
2010-07-20 17:50 ` Andrew Morton
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=20100702160501.45861821.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--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;
as well as URLs for NNTP newsgroup(s).