All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: reiserfs-list@namesys.com
Subject: call for testers. reiserfs_file_write() implementation.
Date: Wed, 14 Aug 2002 18:49:38 +0400	[thread overview]
Message-ID: <20020814184938.A12116@namesys.com> (raw)

Hello!

    After some time of development and internal testing, I am releasing
    this in public (obviously before pushing it to Marcelo).
    There are two patches at
    ftp://ftp.namesys.com/pub/reiserfs-for-2.4/2.4.19.pending/testing
    These implement reiserfs_file_write() support (patches are against
    2.4.20-pre2) that should speedup writes for those applications
    that actually care about st_blksize content of stat(2) output.
    (including cp and dd of course)
    Before submittig these to Marcelo we'd like to get more wide testing,
    of course. So if you can try these and report any problems, that
    would be very much appreciated.
    Also first patch considerably speedups hole creation (I remember report
    about creating 128G empty file was taking ages, this should fix this).
    
    Please note that these patches are not compatible with Chris Mason's
    datalogging patches, though we will do a merge later of course.

Bye,
    Oleg

             reply	other threads:[~2002-08-14 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-14 14:49 Oleg Drokin [this message]
2002-08-15  2:46 ` compatibility of 2.4.20-pre2/.19.pending & data-logging ? Manuel Krause
2002-08-15  4:56   ` Oleg Drokin
2002-08-15 15:33     ` Chris Mason
2002-08-15 15:53     ` reiserfs vs NTFS for large amount of small file transactions darren

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=20020814184938.A12116@namesys.com \
    --to=green@namesys.com \
    --cc=reiserfs-list@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.