netdev - Re: [0/7] Distributed storage release.

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4957C2C4.5080007@tmr.com>
Date:	Sun, 28 Dec 2008 13:17:40 -0500
From:	Bill Davidsen <davidsen@....com>
To:	Pavel Machek <pavel@...e.cz>
CC:	Evgeniy Polyakov <zbr@...emap.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, dst@...emap.net,
	netdev@...r.kernel.org
Subject: Re: [0/7] Distributed storage release.

Pavel Machek wrote:
> On Fri 2008-12-26 14:56:09, Evgeniy Polyakov wrote:
>> Hi.
>>
>> This is a maintenance distributed storage release, which includes a
>> rebase against the 2.6.28 kernel tree only.
>>
>> DST is a network block device storage, which can be used to organize
>> exported storages on the remote nodes into the local block device.
>>
>> Its main goal of the project is to allow creation of the block devices
>> on top of different network media and connect physically distributed devices
>> into single storage using existing network infrastructure and not
>> introducing new limitations into the protocol and network usage model.
> 
> So it is basically nbd on steroids?
> 
> ...reminds me, nbd-server should really fsync data before returning success...
> 									Pavel
> 
If you really want reliable operation without killing performance on the server 
you could use aio and just wait until the data is written to the device. Lots of 
discussion of this in various places, "on the device" may not mean on the 
platter, then you talk disabling write cache, barriers, etc. At least aio should 
(a) be more reliable than just issuing the i/o and (b) not impact the 
performance of the server as fsync would.

Comments welcome, pointers to a benchmark even more so, now I'm curious.

-- 
Bill Davidsen <davidsen@....com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html