OK, so you reject softupdates because it took time to mature and you
assume it stopped improving when you stopped paying attention.How long do you think it will take for HAMMER to mature? Realistically?
How long will HAMMER be "a huge source of bugs in the system" before it
stabilizes?Think back to when you started DragonFly. How soon did you expect it to
overtake FreeBSD in SMP performance? And how long did it actually take?
Actually, it never happened - DrangonFly doesn't scale at all across
multiple cores, while FreeBSD 7 leads the pack.Perhaps you should adjust your expectations a bit. I don't doubt that
HAMMER will be a very interesting file system when it's stable, but I
doubt very much that will happen any time soon. In fact, I think it
will take about as long for HAMMER to mature as it took for softupdates
and SMPng.DES
--
Dag-Erling Smørgrav - des@des.no
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
And softupdates are still buggy :( I had a panic with something about
softupdates and inode right before New Year (kernel binaries have been
rebuilt before then, so I could not really debug).The "Failed to flush worklist" error continues to appear every once in a while
too, preventing clean unmounts...Usable? Mostly. Mature? No...
-mi
######################################################################
The information contained in this communication is confidential and
may contain information that is privileged or exempt from disclosure
under applicable law. If you are not a named addressee, please notify
the sender immediately and delete this email from your system.
If you have received this communication, and are not a named
recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited.
######################################################################
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Wow, pretty neat. If HAMMER becomes the default filesystem and snapshots
are low cost and easy are they any plans to leverage these features? :-)
If I understand some of the opensolaris work correctly they are
starting to make use of zfs snapshots for upgrades/updates and packaging
systems.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
There are better lists on which to discuss DragonflyBSD vaporware.
Scott
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Jeff Garzik | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Christoph Hellwig | Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux interface for on access scan... |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Emmanuel Dreyfus | fixing send(2) semantics (kern/29750) |
| Christos Zoulas | Re: Melting down your network [Subject changed] |
| Juan RP | Changing the I/O scheduler on-the-fly |
| Emmanuel Dreyfus | Re: fixing send(2) semantics (kern/29750) |
