linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: keld@keldix.com
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: PATCH: RAID10-layout-descriptions
Date: Thu, 3 Jul 2014 11:40:38 +0200	[thread overview]
Message-ID: <20140703094038.GA25459@www5.open-std.org> (raw)
In-Reply-To: <1402852943.4708.8.camel@heisenberg.scientia.net>

Hi all

The updated text is actually techninaclly misleading or plainly wrong, for the description
of the far and offset layouts. Offset cannot compete with far, as also witnessed by many benchmarks,
as described on the wiki. https://raid.wiki.kernel.org/index.php/Performance

The old text is much more precise than the new. So I advise
that we do not apply the patch, or do another one with the small improvements there
is still in the new patches.

Best regards
Keld

On Sun, Jun 15, 2014 at 07:22:23PM +0200, Christoph Anton Mitterer wrote:
> Hi Neil.
> 
> As mentioned on GitHub before I'm trying to clean up some old patches or
> get them merged.
> 
> 
> I lost a bit track on what we've discussed about them before,...
> 
> One thing I remember is that you didn't like unicode and tbl(1) being
> used.
> 
> Well of course we can talk about that again,... but I think this is
> 2014, so literally everyone has unicode and I think the explanations
> benefit from it (actually I see more and more manpages using unicode).
> 
> With respect to tbl(1) and the box drawings... I think you were
> complaining that this doesn't work with groff when rendering e.g. to
> PDF.... well I guess you're right, but the question is probably: is
> anyone in the world doing this?
> I mean for manpages it seems to work quite well and IMHO improves
> readability and understandability of the explanations quite a lot... and
> we can't just cover any side way on how the nroff files might be used,
> and for which rendering doesn't work.
> 
> 
> After all,... I think the patches below contain lots of valuable
> information which is currently missing in the manpages... so having that
> information merged somehow is surely better than not.
> Actually the same is IMHO fully missing for the different RAID 5/6
> layouts.
> 
> I'd be happy if someone could look into spelling issues and that like.
> 
> Cheers,
> Chris.









      parent reply	other threads:[~2014-07-03  9:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-15 17:22 PATCH: RAID10-layout-descriptions Christoph Anton Mitterer
2014-06-15 20:43 ` NeilBrown
2014-06-16 16:34   ` Christoph Anton Mitterer
2014-07-03  6:58     ` NeilBrown
2014-07-03  9:40 ` keld [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=20140703094038.GA25459@www5.open-std.org \
    --to=keld@keldix.com \
    --cc=calestyo@scientia.net \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).