From: Bradley W. Settlemyer <settlemyerbw@ornl.gov>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] max_dirty_mb and fsync
Date: Thu, 15 Oct 2009 14:52:02 -0400 [thread overview]
Message-ID: <4AD76F52.4040706@ornl.gov> (raw)
Hello
What is the difference between setting the max_dirty_mb setting in
/proc to 4 and making sure that all of my applications fsync every 4MBs
of data that are transmitted?
I would guess that one difference is the 32MB is a filesystem-wide
setting rather than a per file setting -- so the sync occurs regardless
of the number of files receiving data. But are there any other
differences with regards to the interaction with the file system.
More to the point perhaps, does an fsync have additional side effects
beyond those that occur for the max_dirty_mb threshhold being exceeded?
Cheers,
Brad
next reply other threads:[~2009-10-15 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 18:52 Bradley W. Settlemyer [this message]
2009-10-16 15:37 ` [Lustre-devel] max_dirty_mb and fsync Bradley W. Settlemyer
2009-10-17 17:53 ` Andreas Dilger
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=4AD76F52.4040706@ornl.gov \
--to=settlemyerbw@ornl.gov \
--cc=lustre-devel@lists.lustre.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.