From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 70121] Increasing efficiency of full data journaling
Date: Wed, 05 Mar 2014 21:48:52 +0000 [thread overview]
Message-ID: <bug-70121-13602-g8xNmS7Ab3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-70121-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=70121
--- Comment #3 from Phillip Susi <psusi@ubuntu.com> ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 2/6/2014 5:38 AM, bugzilla-daemon@bugzilla.kernel.org wrote:
> Full data journaling provides the ability that it is guaranteed
> that a file will never be saved visible for the user in a damaged
> state (except a hardware defect appears afterwards). But this has
> the disadvantage that the writing througput is ~halfed as all files
> are written 2 times.
It does no such thing. To do that, a new kernel api is needed to
allow the application to specify where transactions start/stop. Data
journaling only makes sense for an external journal on an ssd or
similar: then fsync() and friends can return as soon as the data hits
the ssd and rely on it being safely migrated to the hdd in the future.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTF4sKAAoJEI5FoCIzSKrwBpsH/35GAm2iqyNudw0JjJdceYqd
PC+47MwQoJE2kcGLNCPVZLhRdHg+fWF6JKewnGAJXz6jsOIeblWyqyL03x8cCDMB
107ssZzXy8OllhczGp1oMR4q7bM0RiIwDjqD8qPJxYwTOHcoIp7RbyK0ER++LcE6
lISrSCyzyqpgo9o2oRAlAdP8/aioaOyiJbGpIhfH42Je+zG5k3mGwaCIuVvBR+Ef
wm6rOqApxv6JwZy0s12alq6MUFMzE9qb9WTzLiDtPybSFzvUgt5brePi74HdJZHs
JYjtUqk43q8wYCWcDcEjKb8q6/h/HGP296ZhM9CoXjq+HYqqWWXbl9T5F5+Nl6k=
=nADc
-----END PGP SIGNATURE-----
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-03-05 21:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 10:38 [Bug 70121] New: Increasing efficiency of full data journaling bugzilla-daemon
2014-02-07 11:28 ` [Bug 70121] " bugzilla-daemon
2014-02-07 14:49 ` bugzilla-daemon
2014-03-05 20:37 ` [Bug 70121] New: " Phillip Susi
2014-03-05 21:48 ` bugzilla-daemon [this message]
2014-03-06 5:28 ` [Bug 70121] " bugzilla-daemon
2014-03-07 20:41 ` Phillip Susi
2014-03-06 15:34 ` bugzilla-daemon
2014-03-07 7:16 ` bugzilla-daemon
2014-03-07 13:48 ` Theodore Ts'o
2014-03-07 13:48 ` bugzilla-daemon
2014-03-07 15:42 ` bugzilla-daemon
2014-03-07 20:41 ` bugzilla-daemon
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=bug-70121-13602-g8xNmS7Ab3@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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 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.