public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yury Umanets <yury@clusterfs.com>
To: Chris Mason <mason@suse.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] reiserfs v3 fixes and features
Date: Wed, 07 Apr 2004 16:06:18 +0300	[thread overview]
Message-ID: <1081343178.3042.2.camel@firefly> (raw)
In-Reply-To: <1081274618.30828.30.camel@watt.suse.com>

On Tue, 2004-04-06 at 21:03, Chris Mason wrote:
> Hello everyone,
> 
> You can download the set of experimental reiserfs v3 patches from:
> 
> ftp://ftp.suse.com/pub/people/mason/patches/reiserfs/2.6.5
> 
> Since some of these are in -mm and some are not, there are two series
> files.  series.linus gives you the patches needed for mainline 2.6.5,
> and series.mm gives you the patches needed for 2.6.5-mm1
> 
> Most of these are from Jeff Mahoney and I, they include:
> 
> bug fixes
> logging optimizations
> data=ordered support
> xattrs
> acls
> quotas
> error messages with device names (based on Oleg's 2.4 patch)
> block allocator improvements
> 
> Jeff Mahoney's acls and xattrs for reiserfs v3 have been in use in the
> suse 2.4 kernels and now 2.6 kernels for a while.  I've posted for
> review to namesys many times, but Hans refuses to consider or read the
> code.   I renewed my efforts over the last month to talk with him about
> the code, but he has ignored it entirely.
> 
> His past objections seem to be that he doesn't want new features in v3. 
> The implementation does not change the disk format in any way (xattrs
> are stored as regular files in a hidden directory) and is stable.  I
> believe reiserfs needs these features in order to stay current in the
> kernel, so I'm posting for inclusion in -mm.  I'm sending Andrew the
> following patches from series.mm:
> 
> reiserfs-end-trans-bkl 
> reiserfs-acl-mknod.diff 
> reiserfs-xattrs-04 
> reiserfs-acl-02 
> reiserfs-trusted-02 
> reiserfs-selinux-02 
> reiserfs-xattr-locking-02 
> reiserfs-quota 
> permission-reiserfs 
> reiserfs-warning 
> 
> (which is everything except the new block allocator code)
> 
> The block allocator improvements is our attempt to reduce
> fragmentation.  The patch defaults to the regular 2.6.5 block allocator,
> but has options documented at the top of the patch that allow grouping
> of blocks by packing locality or object id.  It also has an option to
> inherit lightly used packing localities across multiple subdirs, which
> keeps things closer together in the tree if you have a bunch of subdirs
> without much in them.
> 
> If anyone is interested in experimenting with the block allocator stuff,
> please let me know.
> 
> -chris
> 
Hello Chris,

That would be nice to have also improved locking in this
features-improvements-fixes patch set. Ask Oleg, he had intention to
work on and probably has something done already.

Thanks.

-- 
umka


  parent reply	other threads:[~2004-04-07 13:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06 18:03 [PATCH] reiserfs v3 fixes and features Chris Mason
2004-04-06 20:14 ` Marc-Christian Petersen
2004-04-06 21:06   ` Chris Mason
2004-04-07  2:00 ` Chris Wright
2004-04-07 13:19   ` Chris Mason
2004-04-07 14:37     ` Hans Reiser
2004-04-07 13:06 ` Yury Umanets [this message]
2004-04-07 13:25   ` Chris Mason
2004-04-08  7:22     ` Yury Umanets
2004-04-09 22:02       ` Oleg Drokin
2004-04-15  0:30 ` Chris Mason
2004-04-15  2:53   ` Hubert Chan
2004-04-15 11:37     ` Chris Mason
2004-04-15 12:12     ` Nikita Danilov
2004-04-16 18:54   ` Chris Mason
2004-04-16 19:47     ` Marc-Christian Petersen
2004-04-16 19:59       ` Chris Mason
2004-04-16 20:06       ` Marc-Christian Petersen
2004-04-16 20:26         ` Chris Mason
2004-04-16 20:39           ` Chris Mason
2004-04-16 20:44             ` Marc-Christian Petersen
2004-04-16 20:41           ` Marc-Christian Petersen

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=1081343178.3042.2.camel@firefly \
    --to=yury@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox