linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luigi Genoni <kernel@Expansa.sns.it>
To: Yaacov Akiba Slama <slamaya@yahoo.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Announcing Journaled File System (JFS) release 1.0.0 available
Date: Fri, 29 Jun 2001 01:08:41 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0106290056350.27056-100000@Expansa.sns.it> (raw)
In-Reply-To: <3B3B9DD2.1030103@yahoo.com>



On Fri, 29 Jun 2001, Yaacov Akiba Slama wrote:

> Hi,
>  From what I understand from Linus's mail to lkml, there is a difference
> between JFS and XFS:
> JFS doesn't require any modifications to existing code, its only an
> addition.
> XFS on the contrary is far more intrusive.
> So it seems that even if JFS is less complete than XFS (no ACL, quotas
> for instance), and even if it is less robust (I don't know if it is, I
It is not less complete nor less robust, it's a different technology and a
totally different approach.
Remember XFS was designed thinking to a kind of HW totally different from
PC, and so was for jfs. But somehow JFS is a better choice if you
do not have the last fastest CPU, and the last fastest scsi disk.
> only used so far XFS and ext3 -with success), its inclusion in current
> kernel is a lot easier and I don't see any (technical) reason for not
> including it.
I hope it will happen as soon.
ReiserFS is a good FS, probably is the best journaled FS you could find
out here, but how many memories with
the old dear jfs! And I have some pentium classic for non critical use
that would be so happy with it.
> I don't think ext3 will have difficulties to be included in the kernel
> because a) the guys working on it are lk veterans and b) Redhat (VA
> also) is already including it in its kernels (rawhide AND 7.1 update).
agree.
> So I only hope that the smart guys at SGI find a way to prepare the
> patches the way Linus loves because now the file
> "patch-2.4.5-xfs-1.0.1-core" (which contains the modifs to the kernel
> and not the new files) is about 174090 bytes which is a lot.
mmm.
I doubt it will be easy.
I should check better, but i think it requires eavy changes to VFS.

oh, by the way.
On a 8 processor origin 2000, with a not so eavy I/O, I usually see
1 processor
totally used just for journaling. (different HW, different Unix ....)

Luigi



  parent reply	other threads:[~2001-06-28 23:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-28 21:12 Announcing Journaled File System (JFS) release 1.0.0 available Yaacov Akiba Slama
2001-06-28 21:21 ` Alan Cox
2001-06-28 21:43 ` Steve Lord
2001-06-29  4:53   ` Yaacov Akiba Slama
2001-06-28 23:08 ` Luigi Genoni [this message]
2001-06-28 23:23   ` james rich
2001-06-28 23:32     ` Luigi Genoni
  -- strict thread matches above, loose matches on Subject: below --
2001-06-29 13:01 Martin Knoblauch
2001-06-28 14:22 Steve Best
2001-06-28 15:52 ` Daniel Phillips
2001-06-28 22:52   ` Daniel Phillips
2001-06-28 16:02 ` Kervin Pierre
2001-06-29 13:33 ` Aaron Lehmann

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=Pine.LNX.4.33.0106290056350.27056-100000@Expansa.sns.it \
    --to=kernel@expansa.sns.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slamaya@yahoo.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;
as well as URLs for NNTP newsgroup(s).