Skip to contentSkip to conversation

XFS for 2.4

DISCUSSION Nathan Scott 34 participants 55 messages Dec 1, 2003 – Dec 15, 2003

lore
Share & tools
lore
#0 lore raw

Hi Marcelo,

Please do a

	bk pull http://xfs.org:8090/linux-2.4+coreXFS

This will merge the core 2.4 kernel changes required for supporting the XFS filesystem, as listed below. If this all looks acceptable, then please also pull the filesystem-specific code (fs/xfs/*)

	bk pull http://xfs.org:8090/linux-2.4+justXFS

cheers.

Signature · 63 lines
Nathan


linux-2.4+coreXFS updates the following files:

 Documentation/Changes              |   16 ++
 Documentation/Configure.help       |   84 +++++++++++++
 Documentation/filesystems/00-INDEX |    2 
 Documentation/filesystems/xfs.txt  |  226 +++++++++++++++++++++++++++++++++++--
 MAINTAINERS                        |    8 +
 drivers/block/ll_rw_blk.c          |    3 
 fs/Config.in                       |    7 +
 fs/Makefile                        |    4 
 fs/buffer.c                        |   59 ++++++++-
 fs/inode.c                         |   46 +++----
 fs/namei.c                         |   13 +-
 fs/open.c                          |   13 ++
 include/linux/dqblk_xfs.h          |    9 -
 include/linux/fs.h                 |   50 +++++++-
 include/linux/posix_acl_xattr.h    |   67 ++++++++++
 include/linux/sched.h              |    1 
 kernel/ksyms.c                     |   12 +
 mm/filemap.c                       |   63 +++++++++-
 18 files changed, 618 insertions(+), 65 deletions(-)

through these ChangeSets:

<[email protected]> (03/11/24 1.1183.1.1)
   VFS support for filesystems which implement POSIX ACLs.
   
   This involves an inode flag which directs the VFS to skip application
   of the umask so that the filesystem ACL code can do this according to
   the POSIX rules, and a new header file defining the contents of the 2
   system ACL extended attributes.  This is a backport from 2.6.

<[email protected]> (03/11/25 1.1194)
   Fix utimes(2) and immutable/append-only files.

<[email protected]> (03/11/25 1.1195)
   Remove some unused macros and related comment from the XFS quota header.

<[email protected]> (03/11/25 1.1196)
   Add a process flag to identify a process performing a transaction.
   Used by XFS and backported from 2.6.

<[email protected]> (03/11/25 1.1197)
   Support for delayed allocation.  Used by XFS and backported from 2.6.

<[email protected]> (03/11/25 1.1198)
   Provide a simple try-lock based dirty page flushing routine.

<[email protected]> (03/11/25 1.1199)
   Provide an iget variant without unlocking the inode and without the
   read_inode call (iget_locked).  Used by XFS and backported from 2.6.

<[email protected]> (03/11/26 1.1200)
   Export several kernel symbols used by the XFS filesystem.

<[email protected]> (03/11/26 1.1201)
   Add XFS documentation and incorporate XFS into the kernel build.

<[email protected]> (03/12/01 1.1202.1.1)
   [XFS] Document the XFS noikeep option, make ikeep the default.
#1 lore raw
Quoted 11 lines · Nathan Scott

Hi Marcelo,

Please do a

	bk pull http://xfs.org:8090/linux-2.4+coreXFS

This will merge the core 2.4 kernel changes required for supporting the XFS filesystem, as listed below. If this all looks acceptable, then please also pull the filesystem-specific code (fs/xfs/*)

	bk pull http://xfs.org:8090/linux-2.4+justXFS

Where can these be found as a unified diff? It's quite bothersome to have to pull a changeset just to review it (cloning a kernel tree first), not to mention space intensive.

Signature · 1 line
Jens Axboe
#2 lore raw
Quoted 12 lines · Jens Axboe
Quoted 10 lines · Nathan Scott

Hi Marcelo,

Please do a

	bk pull http://xfs.org:8090/linux-2.4+coreXFS

This will merge the core 2.4 kernel changes required for supporting the XFS filesystem, as listed below. If this all looks acceptable, then please also pull the filesystem-specific code (fs/xfs/*)

Quoted 7 lines
Quoted 1 line
	bk pull http://xfs.org:8090/linux-2.4+justXFS

Where can these be found as a unified diff? It's quite bothersome to have to pull a changeset just to review it (cloning a kernel tree first), not to mention space intensive.

There was a mail announcing split-patches for 2.4.23 five hours before this mail. The mail was from Keith Owens but here's the link from it:

ftp://oss.sgi.com/projects/xfs/patches/2.4.23 for the 2.4.23 patches.

// Stefan

#3 lore raw
Quoted 22 lines · Stefan Smietanowski
Quoted 12 lines · Jens Axboe
Quoted 10 lines · Nathan Scott

Hi Marcelo,

Please do a

	bk pull http://xfs.org:8090/linux-2.4+coreXFS

This will merge the core 2.4 kernel changes required for supporting the XFS filesystem, as listed below. If this all looks acceptable, then please also pull the filesystem-specific code (fs/xfs/*)

Quoted 7 lines
Quoted 1 line
	bk pull http://xfs.org:8090/linux-2.4+justXFS

Where can these be found as a unified diff? It's quite bothersome to have to pull a changeset just to review it (cloning a kernel tree first), not to mention space intensive.

Quoted 4 lines

There was a mail announcing split-patches for 2.4.23 five hours before this mail. The mail was from Keith Owens but here's the link from it:

ftp://oss.sgi.com/projects/xfs/patches/2.4.23 for the 2.4.23 patches.

Great, thanks.

Signature · 1 line
Jens Axboe
#4 lore raw
In reply to Nathan Scott
Quoted 11 lines · Nathan Scott

Hi Marcelo,

Please do a

	bk pull http://xfs.org:8090/linux-2.4+coreXFS

This will merge the core 2.4 kernel changes required for supporting the XFS filesystem, as listed below. If this all looks acceptable, then please also pull the filesystem-specific code (fs/xfs/*)

	bk pull http://xfs.org:8090/linux-2.4+justXFS

Nathan,

I think XFS should be a 2.6 only feature.

2.6 is already stable enough for people to use it.

#49 lore raw
In reply to Nathan Scott

Marcelo,

We (Fermilab) second this request. We won't be touching 2.6 until it's really stable (read as, Red Hat comes out with an official distro that has it built in), and we already have *a lot* of XFS filesystems here (~>300TB) running on 2.4 kernels. It would be very, very nice to have it in the 2.4 tree without having to pull it from SGI.

Thanks,
Dan

Quoted 14 lines · Nathan Scott

Hi Marcelo,

Please do a

	bk pull http://xfs.org:8090/linux-2.4+coreXFS

This will merge the core 2.4 kernel changes required for supporting the XFS filesystem, as listed below. If this all looks acceptable, then please also pull the filesystem-specific code (fs/xfs/*)

	bk pull http://xfs.org:8090/linux-2.4+justXFS

cheers.

Signature · 4 lines
Dan Yocum
Sloan Digital Sky Survey, Fermilab  630.840.6509
[email protected], http://www.sdss.org
SDSS.  Mapping the Universe.  You are here.
#50 lore raw

I'd like to "third" this request. Have a large amount of data here on XFS with v2.4 kernel.

Would be nice to be able to use pre-release 2.4 for testing without having to manually hack in XFS paches from SGI for the odd reject...

Quoted 25 lines · Dan Yocum

Marcelo,

We (Fermilab) second this request. We won't be touching 2.6 until it's really stable (read as, Red Hat comes out with an official distro that has it built in), and we already have *a lot* of XFS filesystems here (~>300TB) running on 2.4 kernels. It would be very, very nice to have it in the 2.4 tree without having to pull it from SGI.

Thanks,
Dan

Quoted 14 lines · Nathan Scott

Hi Marcelo,

Please do a

    bk pull http://xfs.org:8090/linux-2.4+coreXFS

This will merge the core 2.4 kernel changes required for supporting the XFS filesystem, as listed below. If this all looks acceptable, then please also pull the filesystem-specific code (fs/xfs/*)

    bk pull http://xfs.org:8090/linux-2.4+justXFS

cheers.

Signature · 4 lines
Bryan Whitehead
SysAdmin - JPL - Interferometry and Large Optical Systems
Phone: 818 354 2903
[email protected]
#51 lore raw

I'd like to add my vote also. I've been using XFS for years. The XFS patches work well. But having them in the standard kernel would be very nice.

Signature · 1 line
jeffrey hundstad
Quoted 33 lines · Bryan Whitehead

I'd like to "third" this request. Have a large amount of data here on XFS with v2.4 kernel.

Would be nice to be able to use pre-release 2.4 for testing without having to manually hack in XFS paches from SGI for the odd reject...

Quoted 25 lines · Dan Yocum

Marcelo,

We (Fermilab) second this request. We won't be touching 2.6 until it's really stable (read as, Red Hat comes out with an official distro that has it built in), and we already have *a lot* of XFS filesystems here (~>300TB) running on 2.4 kernels. It would be very, very nice to have it in the 2.4 tree without having to pull it from SGI.

Thanks,
Dan

Quoted 14 lines · Nathan Scott

Hi Marcelo,

Please do a

    bk pull http://xfs.org:8090/linux-2.4+coreXFS

This will merge the core 2.4 kernel changes required for supporting the XFS filesystem, as listed below. If this all looks acceptable, then please also pull the filesystem-specific code (fs/xfs/*)

    bk pull http://xfs.org:8090/linux-2.4+justXFS

cheers.

#5 lore raw
In reply to Marcelo Tosatti
Quoted 12 lines · Marcelo Tosatti
Quoted 10 lines · Nathan Scott

Hi Marcelo,

Please do a

	bk pull http://xfs.org:8090/linux-2.4+coreXFS

This will merge the core 2.4 kernel changes required for supporting the XFS filesystem, as listed below. If this all looks acceptable, then please also pull the filesystem-specific code (fs/xfs/*)

Quoted 8 lines
Quoted 1 line
	bk pull http://xfs.org:8090/linux-2.4+justXFS

Nathan,

I think XFS should be a 2.6 only feature.

2.6 is already stable enough for people to use it.

Hi Marcelo,

Please reconsider -- the "core" kernel changes we need have existed for three+ years outside of the mainline tree, and each is a small and easily understood change that doesn't affect other filesystems. There is also a VFS fix in there from Ethan Benson, as we discussed during 2.4.23-pre, when you asked us to resend XFS for 2.4.24-pre!) Everything there is a backport from 2.6 in some form, there should be no surprises.

Not having XFS in 2.4 is extremely disadvantageous for us XFS folks (especially since every other journaled filesystem has been merged now). To our users it means some rescue disks simply don't support XFS, meaning you can't mount filesystems when you _really_ need to, etc, etc. Its also always extra work for distributors to merge XFS themselves, and hence a few just don't (and occasionally tell us that they are waiting for you to merge it) - which means some users don't even get the option of using XFS, despite our best efforts.

Quoted 1 line

From discussions with distributors, a stable 2.6 distribution will

be many months after 2.6.0 is officially released, so these issues are not going to go away anytime soon.

So, please merge XFS this time round - its actively developed, has a large installed user base, and has been maintained outside of 2.4 for a long time. We have waited patiently as each release goes by for you to give us the nod, and have been knocked back on a number of occasions while various other merges are being done.

cheers.

Signature · 1 line
Nathan
#52 lore raw
In reply to Bryan Whitehead
Quoted 6 lines · Bryan Whitehead

I'd like to "third" this request. Have a large amount of data here on XFS with v2.4 kernel.

Would be nice to be able to use pre-release 2.4 for testing without having to manually hack in XFS paches from SGI for the odd reject...

Yes, exactly.

Ok the XFS changes some vfs code, but works OK, and is in the -ac and -ck trees.

And another point is make the possiblility to add some patchs such as security without hunks failed, and another funny hacks.

And the majority of distros include it.

Another vote.

chau,
djgera

Quoted 37 lines
Quoted 29 lines · Dan Yocum

Marcelo,

We (Fermilab) second this request. We won't be touching 2.6 until it's really stable (read as, Red Hat comes out with an official distro that has it built in), and we already have *a lot* of XFS filesystems here (~>300TB) running on 2.4 kernels. It would be very, very nice to have it in the 2.4 tree without having to pull it from SGI.

Thanks,
Dan

Quoted 14 lines · Nathan Scott

Hi Marcelo,

Please do a

    bk pull http://xfs.org:8090/linux-2.4+coreXFS

This will merge the core 2.4 kernel changes required for supporting the XFS filesystem, as listed below. If this all looks acceptable, then please also pull the filesystem-specific code (fs/xfs/*)

    bk pull http://xfs.org:8090/linux-2.4+justXFS

cheers.

Signature · 4 lines
Bryan Whitehead
SysAdmin - JPL - Interferometry and Large Optical Systems
Phone: 818 354 2903
[email protected]
Signature · 4 lines
Gerardo Exequiel Pozzi ( djgera )
http://www.vmlinuz.com.ar http://www.djgera.com.ar
KeyID: 0x1B8C330D
Key fingerprint = 0CAA D5D4 CD85 4434 A219  76ED 39AB 221B 1B8C 330D
#6 lore raw
In reply to Nathan Scott
Quoted 10 lines · Nathan Scott
Quoted 6 lines

Nathan,

I think XFS should be a 2.6 only feature.

2.6 is already stable enough for people to use it.

Hi Marcelo,

Please reconsider

I have no idea if XFS should or should not go in, I'm not commenting on that.

However, having a bunch of XFS users say "put it in" when the maintainer said no, DaveM said no, and no other file system people seem to be stepping up to the bat with a review and a nod seems wrong.

Have you spoken with the people who maintain the generic parts of the VFS layer that you want to change? If those people were in the list of people saying "XFS should go in" then I think you'd get a lot farther.

It's great that there are XFS users but the users should not make the add it or not add it decision, the people who maintain those interfaces which are generic should make that decision. Don't you agree?

Signature · 2 lines
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm
#7 lore raw

Hello Larry,

Quoted 6 lines · Larry McVoy

I have no idea if XFS should or should not go in, I'm not commenting on that.

However, having a bunch of XFS users say "put it in" when the maintainer said no, DaveM said no, and no other file system people seem to be stepping up to the bat with a review and a nod seems wrong.

I must have missed that mail from Dave - or perhaps its still in flight to me. If you're refering to his "super-maintainence mode" comment, I don't believe there was any specific comments relating to XFS there (and XFS on 2.4 is in maintenance mode, has been for a long time).

I also have mail from Marcelo saying he would look at merging XFS in 2.4.24-pre (back when we last sent it, in 2.4.23-pre) ... so, obviously I'm a little confused by this turn of events.

Quoted 3 lines

Have you spoken with the people who maintain the generic parts of the VFS layer that you want to change? If those people were in the list of people saying "XFS should go in" then I think you'd get a lot farther.

That level of discussion with other kernel coders, and extensive review _has_ happened, in many cases _years_ ago now - this stuff has all been merged in 2.5 for ages. I wouldn't expect discussion from other filesystem people at this stage - it is all old news to them.

Quoted 2 lines

... the people who maintain those interfaces which are generic should make that decision. Don't you agree?

Of course, and they have agreed that these are the way the changes should be made - if you look at 2.6 you will see these changes all merged there, a long time ago. As I said, there is nothing new or surprising here, and the changes are small and such that the other filesystems are unaffected.

cheers.

Signature · 1 line
Nathan
#34 lore raw
In reply to Marcelo Tosatti

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcelo Tosatti wrote:

| Nathan,
|
| I think XFS should be a 2.6 only feature.
|
| 2.6 is already stable enough for people to use it.

It is not. It is still in development, and even if a 2.6.0 is released I just think back to 2.4.0, just because it is called stable doesn't make it stable.
I am sure it will need at least half a year for the major distros (RedHat, Novell/SuSe, Mandrake) to pick it up. Perhaps some others more earlier (Gentoo who knows), some never (Debian), but still, in the mean time it is always a bit tricky with kernel updats here. Either I patch it with the SGI and might have troubles with other patches, or I take the -ac (which didn't work last time because of some driver problems with the HP/Compaq Raid) or I take the -ck which is a Desktop patchset and not a server patchset ...
Well in just my opinion XFS should go into 2.4 (and not only because ALL other FS are in there already). 2.4 will be the main kernel for quite some more time and always come up with the argument "but 2.6 is so ready" doesn't help ...

- --
Clemens Schwaighofer - IT Engineer & System Administration
==========================================================
Tequila Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
http://www.tequila.jp
==========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/y+IKjBz/yQjBxz8RAlmAAJ44ixaLQ0UWX+y3pfM3AGJplJ/VdwCfSHP8 ghIZWUtwQhg+ZHU/iN4obzI=
=KfM2
-----END PGP SIGNATURE-----

#35 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 2 Dec 2003, Clemens Schwaighofer wrote:

[...]

Quoted 5 lines

time it is always a bit tricky with kernel updats here. Either I patch it with the SGI and might have troubles with other patches, or I take the -ac (which didn't work last time because of some driver problems with the HP/Compaq Raid) or I take the -ck which is a Desktop patchset and not a server patchset ...

[...]

As a replacement to the -ac patches, you can allways use the -pac patches (currently 2.4.23-pac1).

Greetings,
Mind Booster Noori

- --
==================================================
Marcos Daniel Marado Torres AKA Mind Booster Noori
/"\ http://student.dei.uc.pt/~marado
\ / [email protected]
X ASCII Ribbon Campaign
/ \ against HTML e-mail and Micro$oft attachments
==================================================

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQE/y+pbmNlq8m+oD34RAg2hAJ48v2ZqMNxsHIcepJPttZo1Qk+kJgCfWh6c jccDjXLdPDBUncc014Ce104=
=0+lU
-----END PGP SIGNATURE-----

#53 lore raw
In reply to Bryan Whitehead
Quoted 17 lines · Bryan Whitehead

I'd like to "third" this request. Have a large amount of data here on XFS with v2.4 kernel.

Would be nice to be able to use pre-release 2.4 for testing without having to manually hack in XFS paches from SGI for the odd reject...

Quoted 10 lines · Dan Yocum

Marcelo,

We (Fermilab) second this request. We won't be touching 2.6 until it's really stable (read as, Red Hat comes out with an official distro that has it built in), and we already have *a lot* of XFS filesystems here (~>300TB) running on 2.4 kernels. It would be very, very nice to have it in the 2.4 tree without having to pull it from SGI.

Thanks,
Dan

I would like to 'me too' - like some brain dead aoler.

I have 40+ machines which use XFS, and I have used it since the 1.0 was released. There are various servers, running a variety of services, etc. I think that the SGI team has done a fantastic job of supporting 2.4, and I have been using with no problems since 2.4.12.

I don't want to dis anyone either, but XFS is the filesystem that I use because it is stable, and reliable, and IMHO mature. I appreciate ext3, Reiser, and especially JFS! However, XFS was ready first, and it was a great disappointment not to see it in 2.4. 2.4 was truly a kernel of pain in the beginning, and I repect the decision not to include it up till now. Not that it matters, but I will respect the decision of the 2.4 maintainers on this. I do ask for 2.4, as a person who uses XFS on all my personal, friends, mom's, and clients' systems. Some of my clients will not use it because it is not in the vanilla tree. Please reconsider on behalf of a wide body of users.

thanks,
Joshua Schmidlkofer

#54 lore raw
In reply to Dan Yocum
Quoted 1 line

We (Fermilab) second this request. We won't be touching 2.6 until it's

I, an ordinary user, also second it. I have been using XFS, but some day I just
got tired of patching the kernel and backed up the data and switched to other filesystem.

I really liked XFS.

Regards,
Maciej

#23 lore raw
In reply to Nathan Scott
Quoted 24 lines · Nathan Scott
Quoted 12 lines · Marcelo Tosatti
Quoted 10 lines · Nathan Scott

Hi Marcelo,

Please do a

	bk pull http://xfs.org:8090/linux-2.4+coreXFS

This will merge the core 2.4 kernel changes required for supporting the XFS filesystem, as listed below. If this all looks acceptable, then please also pull the filesystem-specific code (fs/xfs/*)

Quoted 8 lines
Quoted 1 line
	bk pull http://xfs.org:8090/linux-2.4+justXFS

Nathan,

I think XFS should be a 2.6 only feature.

2.6 is already stable enough for people to use it.

Hi Marcelo,

Quoted 7 lines

Please reconsider -- the "core" kernel changes we need have existed for three+ years outside of the mainline tree, and each is a small and easily understood change that doesn't affect other filesystems. There is also a VFS fix in there from Ethan Benson, as we discussed during 2.4.23-pre, when you asked us to resend XFS for 2.4.24-pre!) Everything there is a backport from 2.6 in some form, there should be no surprises.

Nathan,

I remember I have said to you "resend me XFS for 2.4.24-pre". A changed my mind since then...

Quoted 3 lines

Not having XFS in 2.4 is extremely disadvantageous for us XFS folks (especially since every other journaled filesystem has been merged now).

JFS did not touch generic code as I remember.

Quoted 6 lines

To our users it means some rescue disks simply don't support XFS, meaning you can't mount filesystems when you _really_ need to, etc, etc. Its also always extra work for distributors to merge XFS themselves, and hence a few just don't (and occasionally tell us that they are waiting for you to merge it) - which means some users don't even get the option of using XFS, despite our best efforts.

Come one, it is not so hard to maintain a patch in a distros kernel.

Distros maintain hundreds of patches (even I did maintain hundreds of patches while maintaining Conectiva's RPM). One more patch is not that hard.

Quoted 3 lines

From discussions with distributors, a stable 2.6 distribution will be many months after 2.6.0 is officially released, so these issues are not going to go away anytime soon.

Fine, so people who want XFS go compile 2.6.0 by hand. I'm using test11 on several boxes and its working very well.

And 2.6 is much nicer than 2.4 anyway.

Quoted 5 lines

So, please merge XFS this time round - its actively developed, has a large installed user base, and has been maintained outside of 2.4 for a long time. We have waited patiently as each release goes by for you to give us the nod, and have been knocked back on a number of occasions while various other merges are being done.

Also I'm not completly sure if the generic changes are fine and I dont like the XFS code in general.

#8 lore raw
In reply to Nathan Scott
Quoted 16 lines · Nathan Scott

Hello Larry,

Quoted 6 lines · Larry McVoy

I have no idea if XFS should or should not go in, I'm not commenting on that.

However, having a bunch of XFS users say "put it in" when the maintainer said no, DaveM said no, and no other file system people seem to be stepping up to the bat with a review and a nod seems wrong.

I must have missed that mail from Dave - or perhaps its still in flight to me. If you're refering to his "super-maintainence mode" comment, I don't believe there was any specific comments relating to XFS there (and XFS on 2.4 is in maintenance mode, has been for a long time).

Quoted 3 lines

I also have mail from Marcelo saying he would look at merging XFS in 2.4.24-pre (back when we last sent it, in 2.4.23-pre) ... so, obviously I'm a little confused by this turn of events.

Nathan,

Yes, I indeed told you "resent me for 2.4.24-pre". I have changed my mind.

Sorry for the trouble that caused you.

Quoted 6 lines

That level of discussion with other kernel coders, and extensive review _has_ happened, in many cases _years_ ago now - this stuff has all been merged in 2.5 for ages. I wouldn't expect discussion from other filesystem people at this stage - it is all old news to them.

Quoted 8 lines
Quoted 2 lines

... the people who maintain those interfaces which are generic should make that decision. Don't you agree?

Of course, and they have agreed that these are the way the changes should be made - if you look at 2.6 you will see these changes all merged there, a long time ago. As I said, there is nothing new or surprising here, and the changes are small and such that the other filesystems are unaffected.

A development tree is much different from a stable tree. You cant just simply backport generic VFS changes just because everybody agreed with them on the development tree.

My whole point is "2.6 is almost out of the door and its so much better". Its much faster, much cleaner.

#24 lore raw
In reply to Marcelo Tosatti
Quoted 47 lines · Marcelo Tosatti
Quoted 24 lines · Nathan Scott
Quoted 12 lines · Marcelo Tosatti
Quoted 10 lines · Nathan Scott

Hi Marcelo,

Please do a

	bk pull http://xfs.org:8090/linux-2.4+coreXFS

This will merge the core 2.4 kernel changes required for supporting the XFS filesystem, as listed below. If this all looks acceptable, then please also pull the filesystem-specific code (fs/xfs/*)

Quoted 8 lines
Quoted 1 line
	bk pull http://xfs.org:8090/linux-2.4+justXFS

Nathan,

I think XFS should be a 2.6 only feature.

2.6 is already stable enough for people to use it.

Hi Marcelo,

Quoted 7 lines

Please reconsider -- the "core" kernel changes we need have existed for three+ years outside of the mainline tree, and each is a small and easily understood change that doesn't affect other filesystems. There is also a VFS fix in there from Ethan Benson, as we discussed during 2.4.23-pre, when you asked us to resend XFS for 2.4.24-pre!) Everything there is a backport from 2.6 in some form, there should be no surprises.

Nathan,

I remember I have said to you "resend me XFS for 2.4.24-pre". A changed my mind since then...

Quoted 3 lines

Not having XFS in 2.4 is extremely disadvantageous for us XFS folks (especially since every other journaled filesystem has been merged now).

JFS did not touch generic code as I remember.

Quoted 8 lines
Quoted 6 lines

To our users it means some rescue disks simply don't support XFS, meaning you can't mount filesystems when you _really_ need to, etc, etc. Its also always extra work for distributors to merge XFS themselves, and hence a few just don't (and occasionally tell us that they are waiting for you to merge it) - which means some users don't even get the option of using XFS, despite our best efforts.

Come one, it is not so hard to maintain a patch in a distros kernel.

s/one/on/

Ugh

#25 lore raw
In reply to Marcelo Tosatti

On Tue, 2003-12-02 at 05:18, Marcelo Tosatti wrote:
[snip]

Quoted 2 lines

Also I'm not completly sure if the generic changes are fine and I dont like the XFS code in general.

Ahh so the real truth comes out.

Is there a reason for your sudden dislike of the XFS code? or is this just an arbitrary general dislike for unknown or unstated reasons?

Signature · 1 line
Russell Cattelan <[email protected]>
#26 lore raw
Quoted 8 lines · Russell Cattelan

On Tue, 2003-12-02 at 05:18, Marcelo Tosatti wrote:
[snip]

Quoted 2 lines

Also I'm not completly sure if the generic changes are fine and I dont like the XFS code in general.

Ahh so the real truth comes out.

Is there a reason for your sudden dislike of the XFS code?

I always disliked the XFS code.

Quoted 2 lines

or is this just an arbitrary general dislike for unknown or unstated reasons?

I dont like the style of the code. Thats a personal issue, though, and shouldnt matter.

The bigger point is that XFS touches generic code and I'm not sure if that can break something.

Why it matters so much for you to have XFS in 2.4 ?

#27 lore raw

As a user it would be very beneficial for me to have XFS support in the official 2.4 kernel tree. XFS been stable and "2.4 integration-ready" for a long time, and 2.4 is going to be used in certain environments for a long time, if only because it's easier to upgrade a 2.4 kernel to a newer 2.4 kernel than to upgrade to a 2.6 kernel. It seems like an easy case to make.

I use other filesystems and some funky drivers as well.. and I'm always very happy to see useful backports show up in the 2.4 tree. Thank you!

Quoted 24 lines · Marcelo Tosatti
Quoted 8 lines · Russell Cattelan

On Tue, 2003-12-02 at 05:18, Marcelo Tosatti wrote:
[snip]

Quoted 2 lines

Also I'm not completly sure if the generic changes are fine and I dont like the XFS code in general.

Ahh so the real truth comes out.

Is there a reason for your sudden dislike of the XFS code?

I always disliked the XFS code.

Quoted 2 lines

or is this just an arbitrary general dislike for unknown or unstated reasons?

I dont like the style of the code. Thats a personal issue, though, and shouldnt matter.

The bigger point is that XFS touches generic code and I'm not sure if that can break something.

Why it matters so much for you to have XFS in 2.4 ?

Signature · 1 line
Darrell Michaud <[email protected]>
#33 lore raw
In reply to Russell Cattelan

I think the dislike is justified. XFS is kind of like an alien parasite attached to Linux. IRIX's IO system is different, it's taken a lot of changes. I still think it is the best filesystem with a lot of unused potential though. I hope it will eventually be well integrated - 2.6/2.8. It's only the generic code changes we need to worry about though, right?

Regards,

Jeremy Jackson

Quoted 14 lines · Russell Cattelan

On Tue, 2003-12-02 at 05:18, Marcelo Tosatti wrote:
[snip]

Quoted 2 lines

Also I'm not completly sure if the generic changes are fine and I dont like the XFS code in general.

Ahh so the real truth comes out.

Is there a reason for your sudden dislike of the XFS code? or is this just an arbitrary general dislike for unknown or unstated reasons?

#28 lore raw
In reply to Darrell Michaud

I second this as well. I'm sure there are others. XFS is a good option to have for official FS inclusion and I'm *very* happy it's in 2.6. If it were in 2.4, that *may* make adoption of 2.6 for some, slow in coming along. While that may be true, I see that most will eventually want to take advantage of all 2.6 has to offer, but if XFS were in the official tree, then that may be one less piece of guess work needed when upgrading from 2.4 to 2.6 with regards to FS maintenance. (i.e. same version of XFS in both trees == possible same reliability, etc)

Quoted 47 lines · Darrell Michaud

As a user it would be very beneficial for me to have XFS support in the
official 2.4 kernel tree. XFS been stable and "2.4 integration-ready" for a long time, and 2.4 is going to be used in certain environments for
a long time, if only because it's easier to upgrade a 2.4 kernel to a newer 2.4 kernel than to upgrade to a 2.6 kernel. It seems like an easy
case to make.

I use other filesystems and some funky drivers as well.. and I'm always
very happy to see useful backports show up in the 2.4 tree. Thank you!

Quoted 5 lines · Marcelo Tosatti
Quoted 3 lines · Russell Cattelan

On Tue, 2003-12-02 at 05:18, Marcelo Tosatti wrote:
[snip]

Quoted 1 line

Also I'm not completly sure if the generic changes are fine and

I dont

Quoted 9 lines
Quoted 5 lines
Quoted 1 line

like the XFS code in general.

Ahh so the real truth comes out.

Is there a reason for your sudden dislike of the XFS code?

I always disliked the XFS code.

Quoted 1 line

or is this just an arbitrary general dislike for unknown or

unstated

Quoted 3 lines
Quoted 1 line

reasons?

I dont like the style of the code. Thats a personal issue, though,

and

Quoted 3 lines

shouldnt matter.

The bigger point is that XFS touches generic code and I'm not sure

if that

Quoted 4 lines

can break something.

Why it matters so much for you to have XFS in 2.4 ?

Signature · 1 line
Darrell Michaud <[email protected]>
Signature · 2 lines
Austin Gonyou <[email protected]>
Coremetrics, Inc.
#29 lore raw
In reply to Darrell Michaud
Quoted 9 lines · Darrell Michaud

As a user it would be very beneficial for me to have XFS support in the official 2.4 kernel tree. XFS been stable and "2.4 integration-ready" for a long time, and 2.4 is going to be used in certain environments for a long time, if only because it's easier to upgrade a 2.4 kernel to a newer 2.4 kernel than to upgrade to a 2.6 kernel. It seems like an easy case to make.

I use other filesystems and some funky drivers as well.. and I'm always very happy to see useful backports show up in the 2.4 tree. Thank you!

This can also be done in patch form, as it is done now :)

There are several pieces of backported software that are integration-ready, but that doesn't imply they should go into an increasingly-frozen 2.4.x tree...

Jeff

#30 lore raw
Quoted 3 lines · Jeff Garzik

This can also be done in patch form, as it is done now :)

of course.
2.4 systems that are already using XFS as a patch probably would have a benefit to see it integrated into 2.4 kernel, but they would is it anyway as a patch.

I do not think the merge would be usefull thinking to a from2.4/to2.6 upgrade. In fact, if a system is not using XFS already, it is difficoult that a filesystem is changed if it is an upgrade and not a reinstallation.

So, at the end, to have XFS just as a patch for 2.4 is not so bad.

Luigi

#31 lore raw
In reply to Jeff Garzik
Quoted 13 lines · Jeff Garzik
Quoted 9 lines · Darrell Michaud

As a user it would be very beneficial for me to have XFS support in the official 2.4 kernel tree. XFS been stable and "2.4 integration-ready" for a long time, and 2.4 is going to be used in certain environments for a long time, if only because it's easier to upgrade a 2.4 kernel to a newer 2.4 kernel than to upgrade to a 2.6 kernel. It seems like an easy case to make.

I use other filesystems and some funky drivers as well.. and I'm always very happy to see useful backports show up in the 2.4 tree. Thank you!

Quoted 5 lines

This can also be done in patch form, as it is done now :)

There are several pieces of backported software that are integration-ready, but that doesn't imply they should go into an increasingly-frozen 2.4.x tree...

Good point, however the XFS code has been ready for way longer than some other things that were integrated have existed at all.

There was a question to merge XFS before 2.4 but the answer was no then. That was eons ago and reiserfs and JFS has made it in since then but not XFS. That strikes me as odd. Everybody have been patient and changing the code according to how it might get accepted and it still hasn't been merged. Many people have run XFS for a long time and while they can use the same way they do now (xfs-patches or precompiled RPM) I don't see a motivation not to include it, especially seeing that other filesystems got in. True XFS touches some generic code but if that really is an issue, why don't people sit down and look at the changes (again) and see what can be changed. If that's the reason.

// Stefan

#32 lore raw
In reply to Marcelo Tosatti
Quoted 11 lines · Marcelo Tosatti
Quoted 8 lines · Russell Cattelan

On Tue, 2003-12-02 at 05:18, Marcelo Tosatti wrote:
[snip]

Quoted 2 lines

Also I'm not completly sure if the generic changes are fine and I dont like the XFS code in general.

Ahh so the real truth comes out.

Is there a reason for your sudden dislike of the XFS code?

Quoted 7 lines

I always disliked the XFS code.

Quoted 2 lines

or is this just an arbitrary general dislike for unknown or unstated reasons?

I dont like the style of the code. Thats a personal issue, though, and shouldnt matter.

True... so are you basing your decision to not include it on some thing technical or just your personal feeling? which in your words "shouldn't matter"

Quoted 3 lines

The bigger point is that XFS touches generic code and I'm not sure if that can break something.

We have taken great pain to make sure the generic code changes do not logically change any code paths.
Everything is either new code paths only used by XFS or very careful conditionals on flags only set by XFS.
Some of the changes that were made to generic code was done because it was the right way to it. It would certainly would be possible pull many of the needed changes back into fs/xfs but then there would be duplicated code that could potentially be wrong if somebody changes the generic routines. (core locking differences in different kernels have bitten us in the past, RedHat kernel are good at this)

If you really have issues with any of the core changes please make some suggestions it's possible things could be done differently.

Quoted 2 lines

Why it matters so much for you to have XFS in 2.4 ?

Well if you follow that logic then why did any of the other filesystems go in? in fact why would any new subsystems go in?
Everybody maintaining a large pile of patches should be sufficient to call something linux?

Take anybody list of reasons for inclusion into core. Acceptance
Larger audience, possible exposure in other projects that won't look at XFS due the extra work of merging their patches with ours Ease the support work needed to integrate with all the different distro More feed back for interfaces

#9 lore raw
In reply to Marcelo Tosatti
Quoted 4 lines · Marcelo Tosatti

[...]
My whole point is "2.6 is almost out of the door and its so much better".
Its much faster, much cleaner.

I agree with this, even in spite of my earlier arguments. I do like 2.6, but I think there are some valid points listed recently for 2.4 inclusion. I might just be an end-user, but I do appreciate XFS for what it is, and have been using it for a while now. It just seems like natural inclusion at this point almost "just makes sense."

Signature · 2 lines
Austin Gonyou <[email protected]>
Coremetrics, Inc.
#10 lore raw
In reply to Marcelo Tosatti
Quoted 7 lines · On Tue, 2 Dec 2003 09:22:48 -0200 (BRST) Marcelo Tosatti…

[...]
A development tree is much different from a stable tree. You cant just simply backport generic VFS changes just because everybody agreed with them on the development tree.

My whole point is "2.6 is almost out of the door and its so much better". Its much faster, much cleaner.

Even if I am a bit off-topic here, please reconsider your last sentence. Don't make people think that 2.6 is in a widely useable state right now. Just take a look at the history of 2.4. Don't forget 2.4 can be used in boxes beyond 4 GB only right _now_ (2.4.23), all previous versions fall completely apart on i386 platform. 2.4 is right now nice, useable and pretty stable - and 2.6 has not even begun to see the real-and-ugly world yet. There will for sure be a lot of interesting test cases during the next months for 2.6, but there are quite an amount of people that need a real stable environment - and that's why they will have to use 2.4 for at least one year from now on.

This is no vote for or against XFS-inclusion, I don't know the thing at all. I only want to state: developer environment is pretty different from the real world, so don't dump 2.4 too early please.

Regards,
Stephan

#11 lore raw

<snip>

Quoted 10 lines

Even if I am a bit off-topic here, please reconsider your last sentence. Don't make people think that 2.6 is in a widely useable state right now. Just take a look at the history of 2.4. Don't forget 2.4 can be used in boxes beyond 4 GB only right _now_ (2.4.23), all previous versions fall completely apart on i386 platform. 2.4 is right now nice, useable and pretty stable - and 2.6 has not even begun to see the real-and-ugly world yet. There will for sure be a lot of interesting test cases during the next months for 2.6, but there are quite an amount of people that need a real stable environment - and that's why they will have to use 2.4 for at least one year from now on.

Ye gods I'm going to regret butting into this conversation but...

I have moved a couple servers successfully to 2.6.0-pre9, felt (over) confident that 2.6.x would work on my busiest server. It was a mistake, lightly loaded it worked great. As user logged in that morning the server became unstable, processes started waiting forever and hanging, imap mostly, later exim and openldap. I never reported it for lack of good debugging info, I plan to take another wack at it in a month or so.

2.4.x is my only option, I would imagine I'm not in the minority here. I do use XFS, not on this particular server but I do use it and would like to see it included into 2.4.x for no other reason than 2.6.x is not stable in all situations.

Signature · 6 lines
*--* Mail: [email protected]
*--* Voice: 425.739.4247
*--* Fax: 425.827.9577
*--* HTTP://the-penguin.otak.com/~lawrence
--------------------------------------
- - - - - - O t a k  i n c . - - - - - 
#12 lore raw
In reply to Stephan von Krawczynski
Quoted 21 lines · Stephan von Krawczynski
Quoted 7 lines · On Tue, 2 Dec 2003 09:22:48 -0200 (BRST) Marcelo Tosatti…

[...]
A development tree is much different from a stable tree. You cant just simply backport generic VFS changes just because everybody agreed with them on the development tree.

My whole point is "2.6 is almost out of the door and its so much better". Its much faster, much cleaner.

Even if I am a bit off-topic here, please reconsider your last sentence. Don't make people think that 2.6 is in a widely useable state right now. Just take a look at the history of 2.4. Don't forget 2.4 can be used in boxes beyond 4 GB only right _now_ (2.4.23), all previous versions fall completely apart on i386 platform. 2.4 is right now nice, useable and pretty stable - and 2.6 has not even begun to see the real-and-ugly world yet. There will for sure be a lot of interesting test cases during the next months for 2.6, but there are quite an amount of people that need a real stable environment - and that's why they will have to use 2.4 for at least one year from now on.

Quoted 3 lines

This is no vote for or against XFS-inclusion, I don't know the thing at all. I only want to state: developer environment is pretty different from the real world, so don't dump 2.4 too early please.

I'm not dumping 2.4. It will enter "maintenance-only" mode in 2.4.25. It will be update as long as there are problems in it, but no more features will creep in.

As for XFS, Christoph will review the patches and tell me what he thinks.

Also other people mailed me saying they reviewed the code.

That makes me more comfortable with merging the XFS modifications.

#13 lore raw
In reply to Marcelo Tosatti

In article <[email protected]>, Marcelo Tosatti <[email protected]> wrote:

| A development tree is much different from a stable tree. You cant just
| simply backport generic VFS changes just because everybody agreed with
| them on the development tree.
| 
| My whole point is "2.6 is almost out of the door and its so much better".  
| Its much faster, much cleaner. 

Yes, a development tree is much different than a stable tree, and even though the number has gone to 2.6, it's very much a development tree, in that it's still being used by the same people, and probably not getting a lot of new testing. Stability is unlikely to be production quality until fixes go in for problems in mass testing, which won't happen until it shows up in a vendor release, which won't happen until the vendors test and clean up what they find... In other words, I don't expect it to be "really stable" for six months at least, maybe a year.

As for "much faster," let's say that I don't see that on any apples to apples benchmark. If you measure new threading against 2.4 threading there is a significant gain, but for anything else the gains just don't seem to warrant a "much" and there are some regressions shown in other people's data.

I think 2.6 has new features, it is more scalable, but other than threads I don't see any huge performance gains.

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#14 lore raw
Quoted 8 lines · bill davidsen

Yes, a development tree is much different than a stable tree, and even though the number has gone to 2.6, it's very much a development tree, in that it's still being used by the same people, and probably not getting a lot of new testing. Stability is unlikely to be production quality until fixes go in for problems in mass testing, which won't happen until it shows up in a vendor release, which won't happen until the vendors test and clean up what they find... In other words, I don't expect it to be "really stable" for six months at least, maybe a year.

There even are people using 2.2 on production and/or desktop computers. I know some of them. Many people jumped from 2.2 to 2.4 because of USB, but since it was backported into 2.2.18, many people prefered to stick to 2.2.

Quoted 5 lines

As for "much faster," let's say that I don't see that on any apples to apples benchmark. If you measure new threading against 2.4 threading there is a significant gain, but for anything else the gains just don't seem to warrant a "much" and there are some regressions shown in other people's data.

I second this. I've already tested several 2.5 and 2.6-test, and I'm really deceived by the scheduler. It looks a lot more as a hack to satisfy xmms users than something usable. I'm doing 'ls -ltr' all the day in directories filled with 2000 files, and it takes ages to complete. I'm even at the point to which I add a "|tail" to make things go faster.

For instance, time typically reports 0.03u, 0.03s, 2.8 real. It seems as each line sent to xterm consumes one full clock tick doing nothing. I never reported it yet because I don't have time to investigate, and it seems more important that people don't hear skips in xmms while compiling their kernel with "make -j 256" on a 16 MB machine. Second test : launch 10 times : xterm -e "find /" & and look how some windows freeze for up to 10 seconds... I don't think this is a problem right now. We've seen lots of work in the scheduler area, many people proposing theirs, and this will stabilize once 2.6 is out and people start to describe what they really do with it and what they feel.

Don't take me wrong, I don't want to whine nor offend anyone here. I think that Ingo and other people like Con have done a very great job at optimizing this scheduler. I just wish we could choose one depending on what we want to do with it.

Just my 2 cents,
Willy

#15 lore raw

In article <[email protected]> you write:

| On Wed, Dec 03, 2003 at 07:01:39PM +0000, bill davidsen wrote:
|  
| > Yes, a development tree is much different than a stable tree, and even
| > though the number has gone to 2.6, it's very much a development tree, in
| > that it's still being used by the same people, and probably not getting
| > a lot of new testing. Stability is unlikely to be production quality
| > until fixes go in for problems in mass testing, which won't happen until
| > it shows up in a vendor release, which won't happen until the vendors
| > test and clean up what they find... In other words, I don't expect it to
| > be "really stable" for six months at least, maybe a year.
| 
| There even are people using 2.2 on production and/or desktop computers. I
| know some of them. Many people jumped from 2.2 to 2.4 because of USB, but
| since it was backported into 2.2.18, many people prefered to stick to 2.2.

I still have a 2.0.30 machine, not network connected, does what I want.

| 
| > As for "much faster," let's say that I don't see that on any apples to
| > apples benchmark. If you measure new threading against 2.4 threading
| > there is a significant gain, but for anything else the gains just don't
| > seem to warrant a "much" and there are some regressions shown in other
| > people's data.
| 
| I second this. I've already tested several 2.5 and 2.6-test, and I'm
| really deceived by the scheduler. It looks a lot more as a hack to
| satisfy xmms users than something usable. I'm doing 'ls -ltr' all the
| day in directories filled with 2000 files, and it takes ages to complete.
| I'm even at the point to which I add a "|tail" to make things go faster.

Just tried that, test11 seems better behaved. I've been running Nick's patches, for general use they work better for me, I can stand a skip a few times a day.

| 
| For instance, time typically reports 0.03u, 0.03s, 2.8 real. It seems as
| each line sent to xterm consumes one full clock tick doing nothing. I
| never reported it yet because I don't have time to investigate, and it
| seems more important that people don't hear skips in xmms while compiling
| their kernel with "make -j 256" on a 16 MB machine. Second test : launch
| 10 times : xterm -e "find /" & and look how some windows freeze for up
| to 10 seconds... I don't think this is a problem right now. We've seen
| lots of work in the scheduler area, many people proposing theirs, and
| this will stabilize once 2.6 is out and people start to describe what
| they really do with it and what they feel.
| 
| Don't take me wrong, I don't want to whine nor offend anyone here. I
| think that Ingo and other people like Con have done a very great job
| at optimizing this scheduler. I just wish we could choose one depending
| on what we want to do with it.

It has been proposed, but people more influentional than I, that scheduling be a module with some base doorknob scheduler as default if not better scheduler is chosen.

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#16 lore raw
Quoted 10 lines · bill davidsen

In article <[email protected]> you write:

| I second this. I've already tested several 2.5 and 2.6-test, and I'm
| really deceived by the scheduler. It looks a lot more as a hack to
| satisfy xmms users than something usable. I'm doing 'ls -ltr' all the
| day in directories filled with 2000 files, and it takes ages to complete.
| I'm even at the point to which I add a "|tail" to make things go faster.

Just tried that, test11 seems better behaved. I've been running Nick's patches, for general use they work better for me, I can stand a skip a few times a day.

Just another datapoint. On my 300MHz PII laptop, ls and tab
completion often hang, taking up 100% CPU on -test11. 2.4.19-pre3-ac2, my 2.4 kernel, doesn't even blip the CPU.
That said, -test11 performs much better than 2.4.2[01], which
used to pause the system entirely for 30 seconds or more.
If there are any knobs I can turn to tweak this, I'm interested.

Joel

Signature · 9 lines
Life's Little Instruction Book #347

	"Never waste the oppourtunity to tell someone you love them."

Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: [email protected]
Phone: (650) 506-8127
#18 lore raw
In reply to bill davidsen
Quoted 29 lines · bill davidsen

In article <[email protected]> you write:

| On Wed, Dec 03, 2003 at 07:01:39PM +0000, bill davidsen wrote:
|  | > Yes, a development tree is much different than a stable tree, and even
| > though the number has gone to 2.6, it's very much a development tree, in
| > that it's still being used by the same people, and probably not getting
| > a lot of new testing. Stability is unlikely to be production quality
| > until fixes go in for problems in mass testing, which won't happen until
| > it shows up in a vendor release, which won't happen until the vendors
| > test and clean up what they find... In other words, I don't expect it to
| > be "really stable" for six months at least, maybe a year.
| | There even are people using 2.2 on production and/or desktop computers. I
| know some of them. Many people jumped from 2.2 to 2.4 because of USB, but
| since it was backported into 2.2.18, many people prefered to stick to 2.2.

I still have a 2.0.30 machine, not network connected, does what I want.

| | > As for "much faster," let's say that I don't see that on any apples to
| > apples benchmark. If you measure new threading against 2.4 threading
| > there is a significant gain, but for anything else the gains just don't
| > seem to warrant a "much" and there are some regressions shown in other
| > people's data.
| | I second this. I've already tested several 2.5 and 2.6-test, and I'm
| really deceived by the scheduler. It looks a lot more as a hack to
| satisfy xmms users than something usable. I'm doing 'ls -ltr' all the
| day in directories filled with 2000 files, and it takes ages to complete.
| I'm even at the point to which I add a "|tail" to make things go faster.

Just tried that, test11 seems better behaved. I've been running Nick's patches, for general use they work better for me, I can stand a skip a few times a day.

Quoted 10 lines
| | For instance, time typically reports 0.03u, 0.03s, 2.8 real. It seems as
| each line sent to xterm consumes one full clock tick doing nothing. I
| never reported it yet because I don't have time to investigate, and it
| seems more important that people don't hear skips in xmms while compiling
| their kernel with "make -j 256" on a 16 MB machine. Second test : launch
| 10 times : xterm -e "find /" & and look how some windows freeze for up
| to 10 seconds... I don't think this is a problem right now. We've seen
| lots of work in the scheduler area, many people proposing theirs, and
| this will stabilize once 2.6 is out and people start to describe what
| they really do with it and what they feel.

The windows can freeze for many reasons. You could be running X in a lower priority, painting X terms is heavy on X using that command and it can steal cpu from the terminal who's process is working in retrieving data from the fs. No dma on the hdds, Etc. I ran this command using test11 with akpm's test10-mm1 patch applied and 10 were going just fine.
All going at the same time along with mplayer playing a divx movie. No
skips in video or audio and all the terminals were updating as rapidly as they could with no pauses of noticable length.
The schedular is nothing short of incredibly better than 2.4.x and prior. Despite the xmms croud's loud cries of trying to get the kernel to fix their player's performance which seems to always suffer more than any other player i've tried.

Quoted 8 lines
| Don't take me wrong, I don't want to whine nor offend anyone here. I
| think that Ingo and other people like Con have done a very great job
| at optimizing this scheduler. I just wish we could choose one depending
| on what we want to do with it.

It has been proposed, but people more influentional than I, that scheduling be a module with some base doorknob scheduler as default if not better scheduler is chosen.

having to manually adjust the schedular is seen by many as a fault in the design of the schedular. The perfect schedular would be able to adjust itself automatically on it's own. If that's perfect, then even if it's likely impossible to achieve it, it makes sense to strive to get as close to it as possible rather than create a set of separate schedulars which the root user (which really shouldn't be doing anything on the system all the time anyway) has to select whenever their workload changes from one goal to another.

#17 lore raw
In reply to Joel Becker

In article <[email protected]>, Joel Becker <[email protected]> wrote:

| 	Just another datapoint.  On my 300MHz PII laptop, ls and tab
| completion often hang, taking up 100% CPU on -test11.  2.4.19-pre3-ac2,
| my 2.4 kernel, doesn't even blip the CPU.

That's funny! I'm running 2.4.19-pre2-ac2 plus three patches which solved something I'd have to rethink to describe. But most of my laptops suspend fine with APM and 2.4, and suspend fine with 2.6 and ACPI but never return to life... I realize APM is depreciated with 2.6, so I'm resigned to 2.4 on those machines.

| 	That said, -test11 performs much better than 2.4.2[01], which
| used to pause the system entirely for 30 seconds or more.
| 	If there are any knobs I can turn to tweak this, I'm interested.

The last time I tried Nick's patches was on test15, there are only so many hours in my day, and my best test machine is slow enough to discourage building a lot of kernels. You might see if his version 15 patches will work on test11, or if test10-mm1 works better for you. Since you're looking for knobs... You might also look at the swappiness (/proc/sys/vm/swappiness) to see if that changes the stuff which bugs you.

Signature · 3 lines
bill davidsen <[email protected]>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
#20 lore raw
In reply to Willy Tarreau

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Willy Tarreau wrote:
| On Wed, Dec 03, 2003 at 07:01:39PM +0000, bill davidsen wrote:

| For instance, time typically reports 0.03u, 0.03s, 2.8 real. It seems as
| each line sent to xterm consumes one full clock tick doing nothing. I
| never reported it yet because I don't have time to investigate, and it
| seems more important that people don't hear skips in xmms while compiling
| their kernel with "make -j 256" on a 16 MB machine. Second test : launch
| 10 times : xterm -e "find /" & and look how some windows freeze for up
| to 10 seconds... I don't think this is a problem right now. We've seen
| lots of work in the scheduler area, many people proposing theirs, and
| this will stabilize once 2.6 is out and people start to describe what
| they really do with it and what they feel.

Well, I had to try that here. I've got a Celeron 650Mhz with 320MB ram and a crappy 14GB HD and yes the finds in the xterms are stopping for some time ... BUT X is 100% responsive. there is no sluggishness, I can use mozilla, etc without a problem. so seriously, who makes 10 finds at the same time and finds are read from FS (I have XFS) so it might be a problem with that. So I don't think the scheduler is bad, I think it is great. When I switched to 2.5 the first time on that box it was like "WOW", so little swapping and KDE is so smooth ... thats so wow ...

Still there are some minor problems (japanese keyboard eg) but that will smooth out when Programs get adapted.

But for your problem, it might get better for these kind of things in later versions :)

- --
Clemens Schwaighofer - IT Engineer & System Administration
==========================================================
Tequila Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
http://www.tequila.jp
==========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/zoEPjBz/yQjBxz8RAjsEAKCO3Nvs/5r/6HgRh9Z83T2SlQmfIgCfQHl5 jbHM0IQVD/buJjD/I2Shv9k=
=YOth
-----END PGP SIGNATURE-----

#19 lore raw
In reply to Ed Sweetman
Quoted 4 lines · Ed Sweetman

The windows can freeze for many reasons. You could be running X in a lower priority, painting X terms is heavy on X using that command and it can steal cpu from the terminal who's process is working in retrieving data from the fs. No dma on the hdds, Etc.

sorry I gave no info. disk is SCSI and is *not* sollicited at all because everything fits in cache. If I was speaking about the scheduler, it's because it's really a CU scheduling behaviour and not an I/O scheduling behaviour. I never changed my X priority, and in 2.4, all windows are fluid because timeslices are evenly distributed.

Quoted 5 lines

I ran this command using
test11 with akpm's test10-mm1 patch applied and 10 were going just fine.
All going at the same time along with mplayer playing a divx movie. No
skips in video or audio and all the terminals were updating as rapidly as they could with no pauses of noticable length.

bingo ! you're in the exact case where people try to detect skips in their players. I suspect that your player and your xterms don't go too fast and are detected as interactive task by the scheduler. So they don't go very fast, but they are all fluid. Now if you can feed saturate a CPU by feeding 6000 lines/s to an xterm during 1 minute and can repeat this on 10 xterms, they won't become interactive at all, and now you'll see that some of them scroll smoothly while others are stopped. If you put your pointer into them and strike a key, they often start again.

Quoted 2 lines

The schedular is nothing short of incredibly better than 2.4.x and prior.

I also think it's better for many workloads. I only say that we can easily identify *some* workloads for which it simply fails to be fair, and although these workload are not more representative than xmms while compiling a kernel, they might match other applications' behaviour. For instance, I don't know if a system which runs all the day at 100% CPU compressing logs asynchronously won't suffer from this.

Quoted 3 lines

Despite the xmms croud's loud cries of trying to get the kernel to fix their player's performance which seems to always suffer more than any other player i've tried.

I totally agree. I've used mpg123 from my old P166+ years ago, to my dual xp1800 and on my notebooks, I've also tried madplay, and I've yet to hear what a skip sounds like.

Quoted 3 lines

having to manually adjust the schedular is seen by many as a fault in the design of the schedular. The perfect schedular would be able to adjust itself automatically on it's own.

I don't agree here. No system knows better than the admin what he's doing. If this was the case, the 'nice' command would never have been invented.

Quoted 5 lines

if it's likely impossible to achieve it, it makes sense to strive to get as close to it as possible rather than create a set of separate schedulars which the root user (which really shouldn't be doing anything on the system all the time anyway) has to select whenever their workload changes from one goal to another.

The root you're talking about is also the same person who installs a server for a dedicated task and sometimes the same person who discovered a profund scheduling problem on the same system two racks away. As long as your systems don't share their experiences, it's up to the humans to tell them.

Willy

#21 lore raw
In reply to Clemens Schwaighofer
Quoted 6 lines · Clemens Schwaighofer

Well, I had to try that here. I've got a Celeron 650Mhz with 320MB ram and a crappy 14GB HD and yes the finds in the xterms are stopping for some time ... BUT X is 100% responsive. there is no sluggishness, I can use mozilla, etc without a problem. so seriously, who makes 10 finds at the same time and finds are read from FS (I have XFS) so it might be a problem with that.

This exact workload is probably not needed by anybody. But my concern is that if it fails here, then possibily other realistic workloads will fail too. But since it's hard to identify, that's why I'm waiting for distros to ship first releases, and for a few people to tell us about particular cases where they are annoyed. Ingo, Con, Nick and others obviously cannot make the greatest scheduler in the world without valuable feedback. And I have the feeling that all they got was "bad...bad...bad.. STOP!! don't touch anything, XMMS is now great".

Production workloads are typically different. Perhaps my 10 xterms produce the same type of load as 10 persons grepping gigs of logs from memory ? And perhaps my "ls -ltr" produce the same workload as... someone searching a recent file with "ls -ltr".

Quoted 3 lines

So I don't think the scheduler is bad, I think it is great. When I switched to 2.5 the first time on that box it was like "WOW", so little swapping and KDE is so smooth ... thats so wow ...

I too think it's great and smoother than 2.4. It obviously makes a difference if you use X (and I don't use these KDE, etc...). But the smoothness was also brought to 2.4 by patches such as rmap, preempt, variable-hz. All of them have been merged into 2.6, so we cannot deny that they helped too.

Quoted 2 lines

But for your problem, it might get better for these kind of things in later versions :)

-test10 was NOK. I'll try test11, and when I've time I'll try Nick's scheduler too.

Cheers,
Willy

#22 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Willy Tarreau wrote:
| On Thu, Dec 04, 2003 at 09:34:23AM +0900, Clemens Schwaighofer wrote:

| Production workloads are typically different. Perhaps my 10 xterms produce
| the same type of load as 10 persons grepping gigs of logs from memory ?
| And perhaps my "ls -ltr" produce the same workload as... someone searching
| a recent file with "ls -ltr"

well I don't know, I don't use this box full time, but quite a lot, I do a lot of compiling on it. Run Mozilla, etc on it, copy big files, etc, but I never had any serious "lock" problems, where everthing freezes for a second like I have from time to time in 2.4

|>So I don't think the scheduler is bad, I think it is
|>great. When I switched to 2.5 the first time on that box it was like
|>"WOW", so little swapping and KDE is so smooth ... thats so wow ...
|
|
| I too think it's great and smoother than 2.4. It obviously makes a
difference
| if you use X (and I don't use these KDE, etc...). But the smoothness was
| also brought to 2.4 by patches such as rmap, preempt, variable-hz. All of
| them have been merged into 2.6, so we cannot deny that they helped too.

well on my working bux I run 2.4.22-ck3 and this has a lot of preempt workstation speedup stuff inside, but it still freezes from time to time if there is a peak in workload.

|>But for your problem, it might get better for these kind of things in
|>later versions :)
|
| -test10 was NOK. I'll try test11, and when I've time I'll try Nick's
| scheduler too.

well test11 is very smooth. I haven't tried Nick scheduler but I might give it a shot, just to see how the "xterm craziness" goes ... :)

- --
Clemens Schwaighofer - IT Engineer & System Administration
==========================================================
Tequila Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
Tel: +81-(0)3-3545-7703 Fax: +81-(0)3-3545-7343
http://www.tequila.jp
==========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/zwjGjBz/yQjBxz8RAmJyAJ4jA3q9yqaYxIjI3PT1ueHHwjUeuACeOWdS Lp4cfDBErPBrd0df27xRygY=
=ffb4
-----END PGP SIGNATURE-----

#36 lore raw

Re: 2.4 vs 2.6

In reply to Marcelo Tosatti
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Marcelo" == Marcelo Tosatti <[email protected]> writes:

[...]
Marcelo> 2.6 is already stable enough for people to use it.

Yes, that's an old post I'm responding to, but I've just given 2.6 a try on my desktop machine, and the above statement seems even more annoying. I hit the following problems:

-- I had to wrestle ATI drivers into compiling, they finally did, but
the kernel prints scary-looking warnings with call stacks, about "sleeping function called from invalid context at mm/slab.c:1856,
-- modules don't autoload for some reason (though I'm sure that could
be solved),
-- bttv does not compile, so no video input for me,
-- drivers for my telephony card (from Digium) are not 2.6-ready, so
no telephony support for me,
-- I have just frozen the machine hard by copying files over NFS and
doing a simulation write to an ATAPI CD-RW at the same time.

I haven't even gotten to VMware and user-mode Linux, which I also need, and I'm not even dreaming about getting my scanner to work. Not to mention that on my laptop there would be an entirely different set of issues, and software suspend in 2.6 is, well, still lacking.

So, as for me, 2.6 is a definite no-no. I see no advantage whatsoever in running it, it caused me nothing but pain, and there is no improvement that I could see that would justify the upgrade.

So please be careful when making statements like that. 2.6 is *NOT* stable enough nor ready enough for people to use it, unless those people have a narrow range of hardware on which the 2.6 kernel has actually been tested (translation: they have the same hardware as the main developers do).

--J.

#37 lore raw

Re: 2.4 vs 2.6

Quoted 5 lines · Jan Rychter
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Marcelo" == Marcelo Tosatti <[email protected]> writes:

[...]
Marcelo> 2.6 is already stable enough for people to use it.

Quoted 7 lines

Yes, that's an old post I'm responding to, but I've just given 2.6 a try on my desktop machine, and the above statement seems even more annoying. I hit the following problems:

-- I had to wrestle ATI drivers into compiling, they finally did, but
the kernel prints scary-looking warnings with call stacks, about "sleeping function called from invalid context at mm/slab.c:1856,

I have an nForce2 w/ Radeon 9000. No problems w/ DRI drivers (included in kernel) or thi ATI supplied drivers, which ATI says successfully compiled against 2.6.0-test6.

Quoted 2 lines

-- modules don't autoload for some reason (though I'm sure that could
be solved),

Make sure you have all the different module options turned on. In 2.6 there are different options for loading, unloading and force unloading modules.

Quoted 1 line

-- bttv does not compile, so no video input for me,

I don't know anything about video input. Did you try Google?

Quoted 2 lines

-- drivers for my telephony card (from Digium) are not 2.6-ready, so
no telephony support for me,

I don't know anything about telephony. Did you try Google?

Quoted 2 lines

-- I have just frozen the machine hard by copying files over NFS and
doing a simulation write to an ATAPI CD-RW at the same time.

What CPU/chipset do you have? There are timing issues with nForce2 and AMD CPUs. A quick search of the LKML archives will yield lots of discussion and patcheson this issue.

Quoted 5 lines

I haven't even gotten to VMware and user-mode Linux, which I also need, and I'm not even dreaming about getting my scanner to work. Not to mention that on my laptop there would be an entirely different set of issues, and software suspend in 2.6 is, well, still lacking.

VMWare won't work (according to the VMWare tech support people), but they will (probably) support 2.6 kernels in their next point release. I assume you are talking about their workstation product. SWSusp works fine on my laptop.

Quoted 4 lines

So, as for me, 2.6 is a definite no-no. I see no advantage whatsoever in running it, it caused me nothing but pain, and there is no improvement that I could see that would justify the upgrade.

But there is plenty of improvement for plenty of people.

Quoted 6 lines

So please be careful when making statements like that. 2.6 is *NOT* stable enough nor ready enough for people to use it, unless those people have a narrow range of hardware on which the 2.6 kernel has actually been tested (translation: they have the same hardware as the main developers do).

I doubt I have the same hardware as the main developers, but I did read the documentation. Did you? Even if it is stable enough for most people, it is still a beta kernel.

Quoted 2 lines

--J.

-Roberto.

#40 lore raw

Re: 2.4 vs 2.6

In reply to Jan Rychter

On Sat, 2003-12-13 at 20:08, Jan Rychter wrote:
<snip>

Quoted 5 lines

So please be careful when making statements like that. 2.6 is *NOT* stable enough nor ready enough for people to use it, unless those people have a narrow range of hardware on which the 2.6 kernel has actually been tested (translation: they have the same hardware as the main developers do).

I have a brand-spanken-new laptop (less than a month old), and all my hardware works great. In fact, ATI drivers (only in pre-release X) only work on 2.6, and ACPI never worked on 2.4. So, it works better for me than on 2.4. Please be careful when saying that 2.4 is better than 2.6, it's only that way for a narrow set of hardware.

Signature · 1 line
Daniel Gryniewicz <[email protected]>
#41 lore raw

Re: 2.4 vs 2.6

In reply to Jan Rychter
Quoted 11 lines · Jan Rychter

So, as for me, 2.6 is a definite no-no. I see no advantage whatsoever in running it, it caused me nothing but pain, and there is no improvement that I could see that would justify the upgrade.

So please be careful when making statements like that. 2.6 is *NOT* stable enough nor ready enough for people to use it, unless those people have a narrow range of hardware on which the 2.6 kernel has actually been tested (translation: they have the same hardware as the main developers do).

For every person who has problems with 2.6, there are probably 2 others who have none, and enjoy the benefits of the new features. 2.6 works great for me, and one a number of hardware configurations including:

- PII-266
- SMP dual PIII-550
- M10000 mini-itx
- 1.1 Ghz Athlon

all with a variety of video chipsets, USB devices, IDE / ATAPI disks and CD/DVD, sound cards, etc.

I doubt many of these are consistent with the main developers.

2.6 may not be usable for you, but this has no bearing on the utility of the branch for others. I have noticed benefits (mainly prempt, IPSEC, and the IDE device handling) which make it very worthwhile.

#43 lore raw

Re: 2.4 vs 2.6

In reply to Jan Rychter

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jan Rychter wrote:

|>>>>> "Marcelo" == Marcelo Tosatti
|>>>>> <[email protected]> writes:
|
| [...] Marcelo> 2.6 is already stable enough for people to use it.
|
| Yes, that's an old post I'm responding to, but I've just given 2.6
| a try on my desktop machine, and the above statement seems even
| more annoying. I hit the following problems:
|
| -- I had to wrestle ATI drivers into compiling, they finally did,
| but the kernel prints scary-looking warnings with call stacks,
| about "sleeping function called from invalid context at
| mm/slab.c:1856, -- modules don't autoload for some reason (though
| I'm sure that could be solved), -- bttv does not compile, so no
| video input for me, -- drivers for my telephony card (from Digium)
| are not 2.6-ready, so no telephony support for me, -- I have just
| frozen the machine hard by copying files over NFS and doing a
| simulation write to an ATAPI CD-RW at the same time.
|
| I haven't even gotten to VMware and user-mode Linux, which I also
| need, and I'm not even dreaming about getting my scanner to work.
| Not to mention that on my laptop there would be an entirely
| different set of issues, and software suspend in 2.6 is, well,
| still lacking.
|
| So, as for me, 2.6 is a definite no-no. I see no advantage
| whatsoever in running it, it caused me nothing but pain, and there
| is no improvement that I could see that would justify the upgrade.
|
| So please be careful when making statements like that. 2.6 is *NOT*
|  stable enough nor ready enough for people to use it, unless those
| people have a narrow range of hardware on which the 2.6 kernel has
| actually been tested (translation: they have the same hardware as
| the main developers do).
|
| --J.

My specs:
Cpu:Athlon XP 2500+ BARTON {10x190}
Mobo:EPOX 8RDA3 + NFORCE 2
Ram:Corsair TWINX 512 3200LL{dual channel/11-3-2-2.0} Fan:Cooler Master +7
Video:Hercules 3D Prophet 9600 PRO Radeon 128MB

My Hercules 3D Prophet 9600 PRO Radeon simply freezes my comp. with ati-drivers from ati.com so I need to press reset!(so I only can run console)
My sound (nvidia on board) works very shitty and I have no control on it (level sound I mean).
I was running 2.4.23 vanilla + lvm1 so I moved to 2.6 vanilla+lvm2 and now I can not move back

These are my biggest problems with 2.6.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/3Aurkj4I0Et8EMgRArxCAKDbp0uE5mIhA5/5C+v/71tscWneHQCg0h3R RF2NIf4bbQ3XEMjV6eEePJI=
=7jBp
-----END PGP SIGNATURE-----

#38 lore raw

Re: 2.4 vs 2.6

In reply to Roberto Sanchez
Quoted 6 lines · Roberto Sanchez
Quoted 5 lines

I haven't even gotten to VMware and user-mode Linux, which I also need, and I'm not even dreaming about getting my scanner to work. Not to mention that on my laptop there would be an entirely different set of issues, and software suspend in 2.6 is, well, still lacking.

VMWare won't work

I've run vmware on a 2.6 kernel. I found a little patch somewhere that made it work.

Signature · 2 lines
Måns Rullgård
[email protected]
#48 lore raw

Re: 2.4 vs 2.6

In reply to Jan Rychter
Quoted 1 line

-- bttv does not compile, so no video input for me,

I'm watching TV on 2.6.0-test11 with bttv properly loaded...

bttv: driver version 0.9.12 loaded

Fred

#44 lore raw

Re: 2.4 vs 2.6

In reply to Voicu Liviu
Quoted 15 lines · Voicu Liviu

My specs:
Cpu:Athlon XP 2500+ BARTON {10x190}
Mobo:EPOX 8RDA3 + NFORCE 2
Ram:Corsair TWINX 512 3200LL{dual channel/11-3-2-2.0} Fan:Cooler Master +7
Video:Hercules 3D Prophet 9600 PRO Radeon 128MB

My Hercules 3D Prophet 9600 PRO Radeon simply freezes my comp. with ati-drivers from ati.com so I need to press reset!(so I only can run console)
My sound (nvidia on board) works very shitty and I have no control on it (level sound I mean).
I was running 2.4.23 vanilla + lvm1 so I moved to 2.6 vanilla+lvm2 and now I can not move back

Quoted 1 line

These are my biggest problems with 2.6.

Have you treid the in kernel DRI drivers? They work with my Radeon 9000 on an nForce2.

Also, why can't you go back to 2.4.23?

-Roberto

#39 lore raw

Re: 2.4 vs 2.6

In reply to Måns Rullgård
Quoted 11 lines · Måns Rullgård
Quoted 6 lines · Roberto Sanchez
Quoted 5 lines

I haven't even gotten to VMware and user-mode Linux, which I also need, and I'm not even dreaming about getting my scanner to work. Not to mention that on my laptop there would be an entirely different set of issues, and software suspend in 2.6 is, well, still lacking.

VMWare won't work

I've run vmware on a 2.6 kernel. I found a little patch somewhere that made it work.

Gentoo automatically applies this patch. :)

Signature · 1 line
Daniel Gryniewicz <[email protected]>
#45 lore raw

Re: 2.4 vs 2.6

In reply to Roberto Sanchez
Quoted 17 lines · Roberto Sanchez
Quoted 15 lines · Voicu Liviu

My specs:
Cpu:Athlon XP 2500+ BARTON {10x190}
Mobo:EPOX 8RDA3 + NFORCE 2
Ram:Corsair TWINX 512 3200LL{dual channel/11-3-2-2.0} Fan:Cooler Master +7
Video:Hercules 3D Prophet 9600 PRO Radeon 128MB

My Hercules 3D Prophet 9600 PRO Radeon simply freezes my comp. with ati-drivers from ati.com so I need to press reset!(so I only can run console)
My sound (nvidia on board) works very shitty and I have no control on it (level sound I mean).
I was running 2.4.23 vanilla + lvm1 so I moved to 2.6 vanilla+lvm2 and now I can not move back

Quoted 8 lines
Quoted 1 line

These are my biggest problems with 2.6.

Have you treid the in kernel DRI drivers? They work with my Radeon 9000 on an nForce2.

Also, why can't you go back to 2.4.23?

Because i use lvm2 and I could not find the way to get back to lvm1 Any clue?

Quoted 2 lines

-Roberto

Liviu

#42 lore raw

Re: 2.4 vs 2.6

In reply to coderman

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 11 lines · coderman
Quoted 9 lines · Jan Rychter

So, as for me, 2.6 is a definite no-no. I see no advantage whatsoever in running it, it caused me nothing but pain, and there is no improvement that I could see that would justify the upgrade.

So please be careful when making statements like that. 2.6 is *NOT* stable enough nor ready enough for people to use it, unless those people have a narrow range of hardware on which the 2.6 kernel has actually been tested (translation: they have the same hardware as the main developers do).

Quoted 3 lines

For every person who has problems with 2.6, there are probably 2 others who have none, and enjoy the benefits of the new features. 2.6 works great for me, and one a number of hardware configurations including:

Somehow, working for 2/3, or even 75% of cases is less than encouraging
to me.

Especially if I must not only set up boxes that I may not touch
physically for days, weeks, etc. Or I suggest which kernel for other people to use, due to security fixes (which, iirc, not all 2.4 fixes have been forward ported yet), features, etc.

2.6 is... getting there. and I DO much appreciate the work of the
developers. But with devfs deprecated, udev still coming into its own (Nice work GregKG btw); with the myriad of (user visible) input layer changes; the change in focus on initrds (it used to be a nice thing that only serious people use. Now, although still optional, it is now becoming much more important). Or mebbe consider that the last time I tried to install the new modutils (I'm blaming my distro vendor for this), it broke my 2.4 modutils, requiring me to boot with init=/bin/sh and fix it up.

Sure. little things, but altogether, they add up to a lot more work to learn.

<snip>

Quoted 5 lines

2.6 may not be usable for you, but this has no bearing on the utility of the branch for others. I have noticed benefits (mainly prempt, IPSEC, and the IDE device handling) which make it very worthwhile.

- --
tabris
- -
When asked by an anthropologist what the Indians called America before the white men came, an Indian said simply "Ours."
-- Vine Deloria, Jr.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/3May1U5ZaPMbKQcRApmfAJ9IQexnFORYTaOEpTiyPQnHt3qCMgCeJimh 8hR+oaEqXhBXbVB9tRg9g5M=
=/Cnp
-----END PGP SIGNATURE-----

#46 lore raw

Re: 2.4 vs 2.6

In reply to Voicu Liviu
Quoted 2 lines · Voicu Liviu

Because i use lvm2 and I could not find the way to get back to lvm1 Any clue?

How about using the patches for 2.4 to give you LVM2 support?

http://people.sistina.com/~thornber/

We have it running on one system right now, in fact it is part of the reason that we manually patched our 2.4.21 to fix the local root exploit that was fixed in 2.4.23, we just had too many external patches (FreeSwan, DeviceMapper, XFS, etc) on that system, to do patch and recompile in a reasonable amount of time.

Harry

Quoted 1 line

Liviu

#47 lore raw

Re: 2.4 vs 2.6

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Harry McGregor wrote:

| On Sun, 2003-12-14 at 10:32, Voicu Liviu wrote:
|
|> Because i use lvm2 and I could not find the way to get back to
|> lvm1 Any clue?
|
|
| How about using the patches for 2.4 to give you LVM2 support?
|
| http://people.sistina.com/~thornber/

This url?
http://people.sistina.com/~thornber/patches/2.4-stable/2.4.22/2.4.22-dm-1/
I'll just get the 2.4.23 vanilla and patch it? I'll try Thanks

|
| We have it running on one system right now, in fact it is part of
| the reason that we manually patched our 2.4.21 to fix the local
| root exploit that was fixed in 2.4.23, we just had too many
| external patches (FreeSwan, DeviceMapper, XFS, etc) on that system,
| to do patch and recompile in a reasonable amount of time.
|
|
| Harry
|
|> Liviu
|
|
|
| - To unsubscribe from this list: send the line "unsubscribe
| linux-kernel" in the body of a message to [email protected]
|  More majordomo info at  http://vger.kernel.org/majordomo-info.html
|  Please read the FAQ at  http://www.tux.org/lkml/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/3WgCkj4I0Et8EMgRApIvAKDO8umYrrSqDodby3OWmxwY9x5ejgCg7wZ+ u5SiceDoteNq61XIVK7vD54=
=5qUw
-----END PGP SIGNATURE-----