Don't mistake the existance of the MP lock for a lack of SMP coding. All kernel coding done in DragonFly these days is SMP oriented because all the APIs are SMP oriented, whether the MP lock is held or not. We are better positioned there then you think we are. If I am overly conservative when it comes to maintaining system stability, well, that's just a quirk of mine. I don't feel there's much of a point to having cool bells and whistles if it also means getting crashes...

I can query the LDAP database with a username and get a list of groups effectively, but there is no existing API that can make use of this. See the above link for discussion and reasons for adding getgroupmembership instead of altering existing APIs. -- Frode Nordahl _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd....

Thank you for letting me know, this is fantastic!! :-) A big thank you to everyone involved in making this happen. I will attempt to put this to test in a production system in good time before 7.1 so any issues can be resolved before release. Any chance the patch will apply on 6.x? -- Frode Nordahl _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "fre...

This argument has sides/issues, one is the 'distribution', and here I agree that one universal-fit-all is not the way to go. I'm concerned in trying to solve a problem we are facing here, were students/researchers danny _______________________________________________ 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"

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am using 8-current (including the latest pmap mods) amd64 on a MSI Neo-F mobo (P35+IHC9R with intergrated re(4) and sata) with a Plextor px-755a SATA dvd+/-rw. I have the following issues with /dev/acd0: If there is blank media present at boot time (have not tested with non-blank media) depending on media type the following happens: 1. re(4) disappears (cd-r) 2. named fails but re(4) is present (cd-rw) 3. goes into infinite stall (not hang) (dv...

Hi No crashes so far. ftp2.ch.freebsd.org is running FreeBSD 7 Beta4 with ZFS on a 64bit Intel Quad Core with 4GB since 2-3 months. We provide a cvsup mirror with cvsup.ch.freebsd.org and a portsnap mirror with portsnap3.freebsd.org too. As an official mirror for kde, mysql, fedora, opensuse, openoffice we run several rsync processes a day and offer rsync for mirroring. No problem so far. I never had any ZFS related crash. I just set two paramters in the loader.conf: vm.kmem_size_max="...

Hi Josh, You can try the latest wpi driver from perforce - http://www.clearchain.com/wiki/Wpi I'm using http://www.turbocat.net/~hselasky/usb4bsd/index.html, which First time I saw this in RC1 - never with 7-CURRENT or -BETAX (I'm -- Best Wishes, Stefan Lambrev ICQ# 24134177 _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@fre...

Yes, but when they have a multi-gigabyte-RAM server, and told that Linux will be better - no matter they are technically so competent or not, we I've heard about disabling it for selected processes or things like memory reservation backed by temporary files done by OS (afair, it was HP-UX). Or Linux overcommit switch, for which this ordinary people are happy enough to not blame (here are defaults): master:~# cat /proc/sys/vm/overcommit_ratio 50 master:~# cat /proc/sys/vm/overcommit_m...

T24gMDcvMDEvMjAwOCwgRGFnLUVybGluZyBTbcO4cmdyYXYgPGRlc0BkZXMubm8+IHdyb3RlOgoK PiBZb3VyIHF1ZXN0aW9uIGlzIGJhc2VkIG9uIHRoZSBwcmVtaXNlIHRoYXQgWkZTIGluIEZyZWVC U0QgNyBpcyB1bnN0YWJsZS4KPiBUaGF0IHByZW1pc2UgaXMgZmFsc2UuCgpBdCBtb3N0LCB3ZSds bCBoYXZlIHRvIGFncmVlIHRvIGRpc2FncmVlLiBBICJ0dW5pbmciIG9mIHRoZSBzeXN0ZW0gKGF0 CmxlYXN0IGZyb20gbXkgZXhwZXJpZW5jZSkgaXMgYWJvdXQgc3lzdGVtIHBlcmZvcm1hbmNlLCBu b3Qgd2hldGhlciB0aGUKc3lzdGVtIHdpbGwgY3Jhc2ggb3Igbm90LiBZb3UgbWF5IGRlZmluZSB0 aGUgd29yZCB0byBtZWFuIHNvbWV0aGluZwplbHNlIGJ1...

To sum up this thread, let me present ZFS status as of today. Before I do that, one explanation. I was away from FreeBSD for like 3-4 weeks, because of real life issues, etc. I hope, I'm now back for good. Let me also use this again to invite any interested committers to help working on ZFS (I'm inviting people to help from a day one). Ok. The most pressing issues currently are: 1. kmem_map exhaustion. 2. Low memory deadlocks in ZFS itself. I believe 2nd problem is already fixed in OpenSo...

Having read the thread and people's reasons for using the ZFS, it does seem that they are trying to use ZFS to solve non-problem problems, especially that someone commented that they use 1:10 kmem:HD space ratio! Igor :-) _______________________________________________ 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"

From the Wikipedia article on Lustre... "...Sun completed its acquisition of Cluster File Systems, Inc., including the Lustre file system, on October 2, 2007, with the intention of bringing the benefits of Lustre technologies to Sun's ZFS file system and the Solaris operating system." So Sun has had what? 2+ months? to try to fill a ZFS 'hole' that was worth a major investment? See also traffic on *Sun's* ZFS list. Far more features than that - 'robust', 'fault tolerant', 'Disaster Rec...

Um, I don't think this part of the post means what I wanted it to mean - = please ignore it - ETOOTIRED :)

100% agreement. If you want to go to extremes, require the user to put=20 zfs.zfs.run_on_32_bit_and_i_understand_i_am_an_idiot_and_this_is_not_recomm= ended=3D1=20 in loader.conf, or else have the kernel panic by design on boot. But don't make it totally impossible without patching the source, *please*. Obviously the exception is if development for i386 stops such that it actua= lly=20 does not work. But disallowing it for artificial reasons... please leave=20 things like that to proprietar...

[Empty message]

Hello igor, With ZFS there aren't fixed boundaries as there are with the slice/partition theme. You can use reservation and quota to determine how much free space is guaranteed for a ZFS and the maximum size a ZFS is allowed to grow to. If you feel that these boundaries/limitations aren't of any use Christian _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "free...

I enjoy my i386/ZFS Servers. It is running with just 384MB RAM as the only instability it currently has is because the / disk ist dying. But even with this it has 71 days uptime. And my backup server is also based on ZFS with just 196MB RAM. This one isn't running stable, but it is stable for just doing the zfs imports and restoring some files. The only 64 bit machines I have at home are alpha and spac64, so no option for ZFS right now. I don't see a real difference between running a 2G i386 an...

Did you have any luck raising interest from Paulo regarding this problem? Is there a PR I can take a look at? I'm not really familiar with the code, so I'd prefer someone who was a bit more familiar with it looked after it, but I This is a bit complicated to answer, but I'll try to capture the gist in a short space. The kernel memory map is an address space in which pages can be placed to be used by the kernel. Those pages are often allocated using one of two kernel allocators, mallo...

Possibly we should rename the "FREE" column to "CACHE" -- the free count is the number of items in the UMA cache. These may be hung in buckets off the per-CPU cache, or be spare buckets in the zone. Either way, the memory has to be reclaimed before it can be used for other purposes, and generally for complex objects, it can be allocated much more quickly than going back to VM for more memory. LIMIT is an administrative limit that may be configured on the zone, and is configured for some b...

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 i...

This depends on what SIGDANGER is supposed to indicate. IMO, a single signal is inadequate - you need a "free memory is less than desirable, please reduce memory use if possible" and one (or maybe several levels of) "memory is really short, if you're not important, please die". The former could reasonably default to SIG_IGN - processes that are in a position to release memory on demand could provide a handler to do so. (This could potentially include malloc returning space on its freelist to th...

That makes the userland side of unnecessarily overcomplicated. If a process handles SIGDANGER then let it do so and assume it's important enough to be left alone, if a process doesn't handle SIGDANGER then send SIGTERM to them then SIGKILL; but in any case SIGTERM *should* precede SIGKILL - the processes ought to be allowed to terminate gracefully. Igor :-) _______________________________________________ freebsd-current@freebsd.org mailing list [ message continues ]

On Mon, 07 Jan 2008 13:18:47 +0000 How could you hide it inside malloc? Would malloc start returning 0 after receiving the "less mem than desirable" signal? Would it ever go back to returning non-zero? I thought that the idea of things like SIGDANGER was that applications would be written to have a mode where they could shut down some aspect of their operation, and free resources. I don't see how you can do that, autonomously, from within malloc? Maybe introduce a special flavour of pointer...

On Mon, 07 Jan 2008 10:42:49 +0100 How is that useful? I386 executables can run on the same hardware with the same changes of kernel. If you're not planning to change kernel, then you can use amd64-only. I thought that the whole fat-binary issue revolved around binary distribution (also by networked file systems) to *different* architectures. Well, that's what Apple and NeXT seem to have used them for. Apollo, Sun, MIPS/SGI, HP(?) always seemed to manage with PATH configurations and/or varian...

We'd need the actual panic message I think. -- John Baldwin _______________________________________________ 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"