From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: cap on writeback?
Date: Mon, 25 Mar 2013 20:06:36 -0400 [thread overview]
Message-ID: <64601.1364256396@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 25 Mar 2013 16:33:48 -0700." <CAGDaZ_rpsUM1ke6Q9b2W+7HwZtSEU21owrgwAkyq6dw0kZPi8g@mail.gmail.com>
On Mon, 25 Mar 2013 16:33:48 -0700, Raymond Jennings said:
> Just curious, is there a cap on how much data can be in "writeback" at
> the same time?
>
> I'm asking because I have over a gigabyte of data in "dirty", but
> during flush, only about 60k or so is in writeback at any one time.
Only a gigabyte? :) (I've got a box across the hall that has 2.6T of RAM,
and yes, it's pretty sad when it decides it's time for writeback across
an NFS or GPFS mount, even though it's a 10GE connection.)
For the record, writeback is one of those things that's really hard to
get right, because there's always corner cases. Probably why we seem to
end up screwing around with it every 2-3 releases. :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 865 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130325/3a11f438/attachment.bin
next prev parent reply other threads:[~2013-03-26 0:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 23:33 cap on writeback? Raymond Jennings
2013-03-26 0:06 ` Valdis.Kletnieks at vt.edu [this message]
2013-03-26 0:23 ` Raymond Jennings
2013-03-26 3:17 ` Valdis.Kletnieks at vt.edu
2013-03-26 9:01 ` Raymond Jennings
2013-03-26 16:46 ` SSDs vs elevators (was Re: cap on writeback?) Arlie Stephens
2013-03-27 10:43 ` Raymond Jennings
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=64601.1364256396@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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).