From: Hans Reiser <reiser@namesys.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
Doug McNaught <doug@wireboard.com>,
"Doug O'Neil" <DougO@seven-systems.com>,
lk <linux-kernel@vger.kernel.org>
Subject: Re: LFS Support for Sendfile
Date: Sun, 03 Mar 2002 15:36:19 +0300 [thread overview]
Message-ID: <3C8218C3.6080204@namesys.com> (raw)
In-Reply-To: <036801c1bfee$b5b0f780$1801010a@Mauser> <m34rk2tn7h.fsf@varsoon.denali.to> <20020228100325.O23151@mea-ext.zmailer.org> <20020302222451.GB9590@tapu.f00f.org>
Chris Wedgwood wrote:
>On Thu, Feb 28, 2002 at 10:03:25AM +0200, Matti Aarnio wrote:
>
> The API (kernel syscall) as defined does not support LFS.
>
>I wonder does it really need to? I mean, a loop calling sendfile for
>2GB (or whatever) at a time is almost as good, if not better in some
>ways.
>
> The "extent based" filesystems offer flatter performance, and
> while I can't determine if ReiserFS is exactly of that type, it
> too offers fast and flat performance.
>
>Reiserfs (v3) isn't extent based but does perform pretty well. When I
>was messing large numbers of with (what at the time were) large files
>of 50GB or so, XFS proved to be very effective.
>
>
> --cw
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
extents are in reiserfs v4.0 (September ship date), and should offer
much improved performance for large files.
Hans
next prev parent reply other threads:[~2002-03-03 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 0:27 LFS Support for Sendfile Doug O'Neil
2002-02-28 1:22 ` Doug McNaught
2002-02-28 8:03 ` Matti Aarnio
2002-03-02 22:24 ` Chris Wedgwood
2002-03-03 12:36 ` Hans Reiser [this message]
[not found] <fa.inaf1vv.one4p5@ifi.uio.no>
[not found] ` <fa.esfhmsv.bku814@ifi.uio.no>
2002-03-03 5:08 ` Dan Maas
2002-03-03 5:34 ` Andrew Morton
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=3C8218C3.6080204@namesys.com \
--to=reiser@namesys.com \
--cc=DougO@seven-systems.com \
--cc=cw@f00f.org \
--cc=doug@wireboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.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 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.