All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Andrew Morton <akpm@osdl.org>, vs <vs@thebsh.namesys.com>
Cc: Nick Orlov <bugfixer@list.ru>,
	linux-kernel@vger.kernel.org, Jeff Mahoney <jeffm@suse.com>,
	reiserfs-dev@namesys.com
Subject: Re: bitmap loading related reiserfs changes in 2.6.17-mm1 are broken
Date: Wed, 21 Jun 2006 23:33:10 -0700	[thread overview]
Message-ID: <449A39A6.7060209@namesys.com> (raw)
In-Reply-To: <20060621204303.47facd01.akpm@osdl.org>

Andrew Morton wrote:

>It would really help if Chris or one of the namesys developers could take
>the time to review and test these patches closely, please.
>  
>
Chris's code also has QA problems.  Because I don't control their
salaries, they both just basically ignore the QA process that the rest
of Namesys uses, and have exactly the results one would expect.  I no
longer encourage non-Namesys companies to pay our developers directly 
--- because of this experience.

That QA process is: everyone must get their patch reviewed and tested by
a second developer before sending it in.  Elena is not qualified to
review the code, but she is able to run a standard suite of tests (one
of which is gcc....) in addition to whatever special test is required
for the patch.   I review the design aspects of the patches, but leave
to others to find most of the coding errors.

Everyone once in a while someone strays from it, and I complain
privately about it.  The percentage of time that it is a mistake to
stray from it is remarkably high.....

Unfortunately, there is both real user demand for the
on-demand-bitmap-loading, and a proper qa of it is non-trivial.  I
propose that vs look at it next week.  vs, please ack.  Chris, if you
are available, please take a look as well.

Jeff has done a lot of good work in optimizing V3 bitmap related code,
and I would like to thank him for that.  It did a lot for our
performance.  Chris's work on the journaling code was also very
important and I am very grateful for it.  A better QA methodology could
have dramatically reduced the number of bugs in that code though.

Hans



  parent reply	other threads:[~2006-06-22  6:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22  3:27 bitmap loading related reiserfs changes in 2.6.17-mm1 are broken Nick Orlov
2006-06-22  3:43 ` Andrew Morton
2006-06-22  3:50   ` Jeffrey Mahoney
2006-06-22  5:09   ` Barry K. Nathan
2006-06-22 10:11     ` Barry K. Nathan
2006-06-22  6:33   ` Hans Reiser [this message]
2006-06-22  7:02   ` Hans Reiser

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=449A39A6.7060209@namesys.com \
    --to=reiser@namesys.com \
    --cc=akpm@osdl.org \
    --cc=bugfixer@list.ru \
    --cc=jeffm@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-dev@namesys.com \
    --cc=vs@thebsh.namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.