public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [0/7] Distributed storage release.
Date: Sun, 28 Dec 2008 13:17:40 -0500	[thread overview]
Message-ID: <4957C2C4.5080007@tmr.com> (raw)
In-Reply-To: <20081226191701.GA1761@ucw.cz>

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@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot


      parent reply	other threads:[~2008-12-28 18:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-26 11:56 [0/7] Distributed storage release Evgeniy Polyakov
2008-12-26 11:56 ` [1/7] dst: core files Evgeniy Polyakov
2008-12-26 11:56   ` [2/7] dst: network state machine Evgeniy Polyakov
2008-12-26 11:56     ` [3/7] dst: export node Evgeniy Polyakov
2008-12-26 11:56       ` [4/7] dst: thread pool Evgeniy Polyakov
2008-12-26 11:56         ` [5/7] dst: transactions Evgeniy Polyakov
2008-12-26 11:56           ` [6/7] dst: crypto processing Evgeniy Polyakov
2008-12-26 11:56             ` [7/7] dst: kconfig and makefile changes Evgeniy Polyakov
2008-12-30 17:26               ` Randy Dunlap
2008-12-30 21:21                 ` Evgeniy Polyakov
2008-12-26 19:17 ` [0/7] Distributed storage release Pavel Machek
2008-12-28 13:37   ` Evgeniy Polyakov
2008-12-28 18:17   ` Bill Davidsen [this message]

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=4957C2C4.5080007@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox