linux-kernel - Re: [PATCH v3] staging: writeboost: Add dm-writeboost

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150220155036.GB4740@debian>
Date:	Fri, 20 Feb 2015 15:50:36 +0000
From:	Joe Thornber <thornber@...hat.com>
To:	Akira Hayakawa <ruby.wktk@...il.com>
Cc:	ejt@...hat.com, Greg KH <gregkh@...uxfoundation.org>,
	snitzer@...hat.com, dm-devel@...hat.com,
	driverdev-devel@...uxdriverproject.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] staging: writeboost: Add dm-writeboost

On Sat, Feb 21, 2015 at 12:25:53AM +0900, Akira Hayakawa wrote:
> Yes.

How big are your log chunks?  Presumably they're relatively small (eg,
256k).  In which case you can optimise for the common case where you
have enough bios to hand to build your log chunk by just referencing
the bio payloads, rather than copying.  It's only the last bit of io
in a burst that should be using this copying slow path.

- Joe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/