Thanks for reply. After performing an additional testing with SSD. I have
more questions.
Firstly, about the additional testing with SSD:
I tested it with SSD (in Linux software raid level 10 setup). The result
shown using dm-integrity is faster than using XFS directly. For using
dm-integrity,
On Mon, Dec 16, 2019 at 10:50:26AM -0800, Eric Biggers wrote:
> On Mon, Dec 16, 2019 at 02:02:33AM +, xianrong.zhou(周先荣) wrote:
> > hey Eric:
> >
> > On Wed, Dec 11, 2019 at 11:32:40AM +0800, zhou xianrong wrote:
> > > From: "xianrong.zhou"
> > >
> > > If check_at_most_once enabled, just
On Fri, 3 Jan 2020, Patrick Dung wrote:
> Hello,
>
> A quick question on dm-integrity. Does dm-integrity layer honors fsync?
Yes it does.
However, it writes data into the journal and when the journal is flushed,
it reports the fsync function as finished.
On a mechanical disk, writes to
Hello,
A quick question on dm-integrity. Does dm-integrity layer honors fsync?
I was testing dm-integrity and performance. It had a strange result that
using dm-integrity with journal is faster than a normal file system or
dm-integrity with bitmap (no journal). fio is used for testing the
From: Anatol Pomazau
Add a configurable timeout mechanism to disable queue_if_no_path without
assistance from multipathd. In reality, this reimplements the
no_path_retry mechanism from multipathd in kernel space, which is
interesting for cases where we cannot rely on a daemon being present all
Any feedback on this patch please.
On 06/12/2019 21:03, Maged Mokhtar wrote:
Removes seq_count from super block. Currently the super block gets
written in each commit to update the seq_count which is just used when
the target is restarted/resumed. This extra iop has a performance impact
on
This patch adds experimental support for BitLocker encryption
with CBC mode and additional Elephant diffuser.
The mode was used in older Windows systems and it is provided
mainly for compatibility reasons. The userspace support
to activate these devices is being added to cryptsetup utility.
