lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 28 May 2013 18:14:18 +0200
From:	Jan Kara <jack@...e.cz>
To:	jingguo yao <yaojingguo@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Why does journal mode outperforms all other modes when reading
 and writing data at the same time?

On Tue 28-05-13 22:39:18, jingguo yao wrote:
> Documentation/filesystems/ext4.txt has the following sentence:
> 
>   This mode is the slowest except when data needs to be read from and
>   written to disk at the same time where it outperforms all others
>   modes.
> 
> And the following link talks about it in more details. Can anybody give
> the reason?
> 
> http://www.ibm.com/developerworks/library/l-fs8/index.html#4
  Not sure why exactly data=journal was faster in that workload. But
generally data=journal is known to help if you have shortlived files which
are then written only to the journal and deleted before they are copied to
the final location on disk. Also it may help by penalizing the writer so
that readers have better chance to do their work...

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ