Linux-kernel mailing list archive 2000-23,: Re: (reiserfs) Re: New Linux 2.5 - 2.6 TODO (Alan Cox suggestsdelaying

# Re: (reiserfs) Re: New Linux 2.5 - 2.6 TODO (Alan Cox suggestsdelaying

Lutz Vieweg (lkv@isg.de)
Tue, 06 Jun 2000 16:15:03 +0200

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Khimenko Victor: "Re: (reiserfs) Re: New Linux 2.5 - 2.6 TODO (Alan Cox"
- Previous message: David Woodhouse: "Re: (reiserfs) Re: New Linux 2.5 - 2.6 TODO (Alan Cox"

This is a cryptographically signed message in MIME format.

--------------ms5D0EFDEC476CA16224FE6F62
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

James Sutherland wrote:

> There is a difference between progress (better implementation) and changes
> to the actual structure. If the version of ReiserFS built into the 2.4
> series will not remain stable (backwards and forwards compatability, from
> 2.4.0 to 2.4.999, transparently), or it may not be properly maintained
> throughout that period, then it should remain external until 2.5.

The reiserfs developers are already willing (and also pushed by many users
and sponsors) to provide a sensible amount of forward- and backward-compatibility.
Inclusion in the main kernel tree would be just another reason to care
about that.

> Do not reinvent the wheel, even if your new wheel has better benchmark
> results. Improve/replace the existing one, by all means - just don't go
> adding new proprietary wheels to make your code a bit faster.

There is no "wheel" (that is, a good, standardized journaling API) yet -
so there's no "reinvenstion".

Also, performance _is_ an issue. We're running a number of mission critical
servers which hit their limits even using the fastest available SCSI harddisks,
and using reiserfs instead of ext2 bought us some very valuable time to
seek solutions.

But the most important point I want to make is that reiserfs is _by_far_
more mature and better supported than dozens of experimental features
that have been included in the kernel for ages.

Just think of funny things like the experimental "bridging" feature (which
never really got stable) and alike.

I think the fast progress reiserfs undergoes is a reason _for_, not against
inclusion. There are other features which cause much more problems
due to rapidly changing re-designs - such as the setup-methods for firewall
rules...

Regards,

Lutz Vieweg

    --
     Dipl. Phys. Lutz Vieweg | email: lkv@isg.de
     Innovative Software AG  | Phone/Fax: +49-69-505030 -20/-50
     Feuerbachstrasse 26-32  | http://www.isg.de/persons/lkv/
     60325 Frankfurt am Main | ^^^ PGP key available here ^^^
    --------------ms5D0EFDEC476CA16224FE6F62
    Content-Type: application/x-pkcs7-signature; name="smime.p7s"
    Content-Transfer-Encoding: base64
    Content-Disposition: attachment; filename="smime.p7s"
    Content-Description: S/MIME Cryptographic Signature

    MIIGbAYJKoZIhvcNAQcCoIIGXTCCBlkCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
    BDwwggQ4MIIDoaADAgECAgEDMA0GCSqGSIb3DQEBBAUAMIG+MQswCQYDVQQGEwJERTEPMA0G
    A1UECBMGSGVzc2VuMRowGAYDVQQHExFGcmFua2Z1cnQgYW0gTWFpbjEhMB8GA1UEChMYSW5u
    b3ZhdGl2ZSBTb2Z0d2FyZSBHbWJIMR8wHQYDVQQLExZOZXR3b3JrIEFkbWluaXN0cmF0aW9u
    MSIwIAYDVQQDExlJU0cgQ2VydGlmaWNhdGUgQXV0aG9yaXR5MRowGAYJKoZIhvcNAQkBFgtp
    bmZvQGlzZy5kZTAeFw05OTA1MzExMDQwMDRaFw0wOTAyMjcxMDQwMDRaMIG2MQswCQYDVQQG
    EwJERTEPMA0GA1UECBMGSGVzc2VuMRowGAYDVQQHExFGcmFua2Z1cnQgYW0gTWFpbjEhMB8G
    A1UEChMYSW5ub3ZhdGl2ZSBTb2Z0d2FyZSBHbWJIMR0wGwYDVQQLExRTb2Z0d2FyZSBEZXZl
    bG9wbWVudDEdMBsGA1UEAxMUTHV0eiBWaWV3ZWcgKElTRyBDQSkxGTAXBgkqhkiG9w0BCQEW
    CmxrdkBpc2cuZGUwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALFztTsWPkDm6li1E/Ba
    PRCokqAHXUb/GmItWq6xGEIseL6T+WsYn46FCInqyayHwxECLFDBFezCQyEvOwM/LfrZIyzF
    gYPudLqKYQvomS/61sMGspf0Q55ZIECVcpxWqKuh3XdN2TbeNz2o61jDCi3LkanQDrvp+zk7
    Lk5jsM3LAgMBAAGjggFKMIIBRjAJBgNVHRMEAjAAMCwGCWCGSAGG+EIBDQQfFh1PcGVuU1NM
    IEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUJHYIC+y3VjL811P7DUoQQWd/YEMw
    gesGA1UdIwSB4zCB4IAUnLMIpiBUdLGe0Y2QoriseGaX0bqhgcSkgcEwgb4xCzAJBgNVBAYT
    AkRFMQ8wDQYDVQQIEwZIZXNzZW4xGjAYBgNVBAcTEUZyYW5rZnVydCBhbSBNYWluMSEwHwYD
    VQQKExhJbm5vdmF0aXZlIFNvZnR3YXJlIEdtYkgxHzAdBgNVBAsTFk5ldHdvcmsgQWRtaW5p
    c3RyYXRpb24xIjAgBgNVBAMTGUlTRyBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxGjAYBgkqhkiG
    9w0BCQEWC2luZm9AaXNnLmRlggEAMA0GCSqGSIb3DQEBBAUAA4GBACDktkQEA6b2sDzPjNKu
    CIM+WJKKmmfpMK/9dDYzIVWmysK2ZQhtx43QnW1xYvQ2diOCRikEIzBEhmuE8XqjK8l5bRbR
    AOIhjURqh0JyCVkVEn/dYDF84eiAxgySBEZK+r//rfCXDQN+JHnuCDuRlkkYF8xk/4i9tx87
    jkVXWrv8MYIB+DCCAfQCAQEwgcQwgb4xCzAJBgNVBAYTAkRFMQ8wDQYDVQQIEwZIZXNzZW4x
    GjAYBgNVBAcTEUZyYW5rZnVydCBhbSBNYWluMSEwHwYDVQQKExhJbm5vdmF0aXZlIFNvZnR3
    YXJlIEdtYkgxHzAdBgNVBAsTFk5ldHdvcmsgQWRtaW5pc3RyYXRpb24xIjAgBgNVBAMTGUlT
    RyBDZXJ0aWZpY2F0ZSBBdXRob3JpdHkxGjAYBgkqhkiG9w0BCQEWC2luZm9AaXNnLmRlAgED
    MAkGBSsOAwIaBQCggYowGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUx
    DxcNMDAwNjA2MTQxNTAzWjAjBgkqhkiG9w0BCQQxFgQUml4JIUlymvD/fyg4W8N27N1oyacw
    KwYJKoZIhvcNAQkPMR4wHDAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYJKoZIhvcN
    AQEBBQAEgYCfSgfASmPemKv7osOrBaQpI+BFgcuDotJMdZafSmZWw3WhsyDRf7qVran9FJMS
    bjwJX7+lE6dXEHPeH21xpkewZIj0th8c3nU8aAbKoOUE2Aiboo3KchFMl8n7aU9zKXxFzxHe
    PD9DkAS1QbyD5jdZR3RBefcE9Xiok7F2hBfpYQ==
    --------------ms5D0EFDEC476CA16224FE6F62--

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

- Next message: Khimenko Victor: "Re: (reiserfs) Re: New Linux 2.5 - 2.6 TODO (Alan Cox"
- Previous message: David Woodhouse: "Re: (reiserfs) Re: New Linux 2.5 - 2.6 TODO (Alan Cox"