linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: Pavel Machek <pavel@suse.cz>, Evgeniy Polyakov <zbe@ioremap.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, pohmelfs@ioremap.net,
	netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [1/9] pohmelfs: documentation.
Date: Wed, 31 Dec 2008 00:23:33 +0300	[thread overview]
Message-ID: <20081230212333.GC20238@ioremap.net> (raw)
In-Reply-To: <4d8e3fd30812281419y4d40a78fha3eb7bc05e55e8ef@mail.gmail.com>

Hi Paolo.

On Sun, Dec 28, 2008 at 11:19:29PM +0100, Paolo Ciarrocchi (paolo.ciarrocchi@gmail.com) wrote:
> Performance seems to be the most important argument in favour of pohmelfs.
> You should probably add more performance data in the cover letter of
> the patch serie. All the information are already available but not
> easy to be reached.
> In short, try to do a better work in "selling" your product :-)

I will create easily understandible graphs and put a link to them into
the description. Performance is indeed one of the interesting parts
among POHMELFS features.

-- 
	Evgeniy Polyakov

  reply	other threads:[~2008-12-30 21:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-26 14:18 [0/9] pohmelfs: The Great Southern Trendkill release Evgeniy Polyakov
2008-12-26 14:18 ` [1/9] pohmelfs: documentation Evgeniy Polyakov
2008-12-26 14:18   ` [2/9] pohmelfs: configuration interface Evgeniy Polyakov
2008-12-26 14:18     ` [3/9] pohmelfs: crypto processing Evgeniy Polyakov
2008-12-26 14:18       ` [4/9] pohmelfs: directory operations Evgeniy Polyakov
2008-12-26 14:18         ` [5/9] pohmelfs: inode operations Evgeniy Polyakov
2008-12-26 14:18           ` [6/9] pohmelfs: distributed locking and cache coherency protocol Evgeniy Polyakov
2008-12-26 14:18             ` [7/9] pohmelfs: network operations Evgeniy Polyakov
2008-12-26 14:18               ` [8/9] pohmelfs: transaction layer Evgeniy Polyakov
2008-12-26 14:18                 ` [9/9] pohmelfs: kconfig/makefile and vfs changes Evgeniy Polyakov
2008-12-26 19:22   ` [1/9] pohmelfs: documentation Pavel Machek
2008-12-28 13:41     ` Evgeniy Polyakov
2008-12-28 22:19       ` Paolo Ciarrocchi
2008-12-30 21:23         ` Evgeniy Polyakov [this message]
2008-12-26 19:26 ` [0/9] pohmelfs: The Great Southern Trendkill release Pavel Machek
2008-12-28 13:53   ` Evgeniy Polyakov
  -- strict thread matches above, loose matches on Subject: below --
2009-02-09 14:02 [0/9] pohmelfs for drivers/staging Evgeniy Polyakov
2009-02-09 14:02 ` [1/9] pohmelfs: documentation Evgeniy Polyakov

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=20081230212333.GC20238@ioremap.net \
    --to=zbr@ioremap.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paolo.ciarrocchi@gmail.com \
    --cc=pavel@suse.cz \
    --cc=pohmelfs@ioremap.net \
    --cc=zbe@ioremap.net \
    /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;
as well as URLs for NNTP newsgroup(s).