From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Charles Samuels <charles@cariden.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Queuing of disk writes
Date: Fri, 1 Apr 2011 21:39:17 +0100 [thread overview]
Message-ID: <20110401213917.1bebfa5f@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <201104011334.24182.charles@cariden.com>
> I've seen this on ext3, ext4, and XFS. Reiser3 not so much. I've also
> convinced my users to use write-backed cache. They're Enterprise customers and
> have loads of money to spend on hardware, such as Warp Cores.
ext3 certainly suffers badly from it, that is known.
> > The ultima answer is probably an SSD of course 8)
> Well, that would solve the throughput, but it doesn't solve the blocking!
Best place to go might be linux-fsdevel - especially if you can generate
a simulation of the problem workload (ie one that just does the I/O
patterns)
next prev parent reply other threads:[~2011-04-01 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 19:59 Charles Samuels
2011-04-01 20:10 ` Alan Cox
2011-04-01 20:34 ` Charles Samuels
2011-04-01 20:39 ` Alan Cox [this message]
2011-04-04 2:02 ` Ted Ts'o
2011-04-04 17:50 ` Charles Samuels
2011-04-04 17:54 ` david
2011-04-05 19:37 ` Ted Ts'o
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=20110401213917.1bebfa5f@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=charles@cariden.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®