Status of SCHED_ULE?
Hello everyone, I was wondering about the status of the ULE scheduler. Is it very experimental still or is it reasonably suitable for everyday (i.e. non-mission-critical) use? Regards, Roderick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Benchmarking KSE and SMPng
Hello everyone,
I've got a big bad quad Pentium III Xeon sitting here that needs
reinstalling, and I would like to take the time to do some KSE and SMPng
benchmarking. Question is how to go about doing it.
I reckon I should basically go for four test setups:
1. FreeBSD 4-STABLE
2. FreeBSD 5-STABLE, libc_r
3. FreeBSD 5-STABLE, all libkse enabled
4. FreeBSD 5-STABLE, all libthr enabled
Question is then which {application,theoretical} benchmarks to run under
which circumstances. Although I've heard of bonnie et al, I'm new to the
benchmarking business and welcome any suggestions.
TIA,
Roderick
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Benchmarking KSE and SMPng
Just in case you don't know, there is no 5-STABLE yet. All the 5.x
Releases have
been based on -CURRENT.
Indeed, I stand corrected.
Question is then which {application,theoretical} benchmarks to run under
which circumstances. Although I've heard of bonnie et al, I'm new to the
benchmarking business and welcome any suggestions.
Something that might be interesting to try is running mysql with libc_r,
linuxthreads, libkse, and libthr, using the included mysql benchmarks that
come
with mysql. I used those benchmarks to test mysql on a few of the machines
I
needed to install it on at one point, and I know mysql utilizes threads.
Off
the top of my head I can't think of anything other than databases that
performed badly on FreeBSD before due to threading issues.
How about Apache2 or locked subsystems (I/O and networking spring to mind)?
Regards,
Roderick
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP! ATAng committed
ATAng has just been committed. You need to make world after this update as atacontrol etc needs to pick up the changes. Coolness. Judging from the CVS log, it also gets ATA out under Giant? That should make ATA-run SMP boxes eligible for an impressive increase in I/O performance... has anyone noticed? Regards, Roderick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
DEVICE_POLLING not in NOTES?
Is there any particular reason DEVICE_POLLING is no longer available in NOTES? (Or should I say isn't linted any more? :-) It still appears to be available in fxp et al. Regards, Roderick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Support DHCP in rc.firewall by default?
Right now, rc.firewall isn't set up to support DHCP configurations although it could easily be done so. Googling comes up with many references, for example http://www.freebsddiary.org/firewall.php (section ipfw with DHCP etc at the bottom of the page). Are there any reasons against having rc.firewall contain such lines? I reckon it would even come in handy for statically configured users: they'd only need to specify their network interface(s) once. Roderick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.0 RC3 now available
I would like to point to a currently unresolved issue that Thomas Moestl is helping me solve on freebsd-sparc@. It isn't listed on the Open Issues page, but I'd say it's something that needs to be resolved before the release is rolled. The thread is titled panic: trap: fast data access mmu miss and is about an error causing the sym SCSI controller to fail to mount root at best, and panic at worst. The sym controller is listed as supported hardware, and used in several Sun boxes, so IMHO I'd say it warrants the attention. Regards, Roderick To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic: trap: fast data access mmu miss
Running on a Sun Enterprise 250 with a single UltraSparc-II CPU, 512 MB RAM and three Fujitsu SCSI-II hard disks. I've had this same problem with sources over the past few (three?) days. I had to copy this dmesg by hand, so please bear with any possible typos. --8-- picb1: PCI-PCI bridge at device 2.0 on pci0 pci1: PCI bus on pcib1 isp0: Qlogic ISP 1020/1040 PCI SCSI Adapter port 0x1000-0x10ff mem 0x4008000-0x4008fff irq 16 at device 4.0 on pci1 isp0: invalid NVRAM header sym0: 875 port 0x2000-0x20ff mem 0x410a000-0x410afff,0x4108000-0x41080ff irq 32 at device 3.0 on pci0 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: 875 port 0x2400-0x24ff mem 0x410e000-0x410efff,0x410c000-0x410c0ff irq 38 at device 3.1 on pci0 panic: trap: fast data access mmu miss cpuid = 0; Debugger(panic) Stopped at Debugger+0x1c: ta %xcc, 1 db trace panic() at panic+0x134 trap() at trap+0x414 -- fast data access mmu miss tar=0 %o7=0xc0248c00 -- getbaddrcb() at getbaddrcb psycho_dmamap_load() at psycho_dmamap_load+0x30 ___dma_getp() at ___dma_getp+0xb8 ___sym_malloc() at ___sym_malloc+0x70 __sym_calloc2() at __sym_calloc2+0xc __sym_calloc_dma() at __sym_calloc_dma+0x64 sym_pci_attach() at sym_pci_attach+0x38 device_probe_and_attach at device_probe_and_attach+0xb8 bus_generic_attach() at bus_generic_attach+0x10 pci_attach() at pci_attach+0x9c device_probe_and_attach at device_probe_and_attach+0xb8 bus_generic_attach() at bus_generic_attach+0x10 psycho_attach() at psycho_attach+0x9d8 device_probe_and_attach at device_probe_and_attach+0xb8 bus_generic_attach() at bus_generic_attach+0x10 device_probe_and_attach at device_probe_and_attach+0xb8 root_bus_configure() at root_bus_configure+0x18 configure() at configure+0x20 mi_startup() at mi_startup+0x12c btext() at btext+0x30 db To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
buildworld failure
Sources updated Dec 31 from anoncvs.freebsd.org on a sparc64. Didn't matter whether I used cvs update with -P or without -P. Got the following error during cleaning: === usr.sbin/fwcontrol cd: can't cd to /usr/src/usr.sbin/fwcontrol *** Error code 2 Stop in /usr/src/usr.sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. # To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: buildworld failure
Sources updated Dec 31 from anoncvs.freebsd.org on a sparc64. Didn't matter whether I used cvs update with -P or without -P. Try cvs co -P. No, -Pd. A simple -P seemed to work, thanks! I'm kind of new to this CVS stuff. Hope you will succeed in Modula-3 ported to sparc64 soon. Perhaps it would be a good idea to add a how to fetch or update the source over anoncvs section to the handbook. The one that there's now doesn't mention the commands necessary to do so successfully, and for me this has been the second time I've run into such pruning problems. Roderick To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ep0 hard lockup during install
Hello, For three days in a row now I have tried installing the most recent 5.0 snapshots on my Armada V300 from floppies. I have also tried the RC2 floppies. Unfortunately, the system freezes up solid when it configures ep0. I have a DHCP server here but manually entering the IP configuration results in the same hard lockup. No error messages of any kind are given, I can't switch to pty2 and the kernel doesn't panic. It just locks up completely and indefinitely. ep0 is a PCMCIA card. I have two of such cards, one being a 3C589, the other a 3CXE589DC. Both cards produce the same result but worked fine on 4-STABLE. I have tried reinserting the cards both before and during the network configuration and have also fiddled with the USB legacy support setting in the system BIOS (not too much options to fiddle with unfortunately), but to no avail. The kernel messages on pty1 and debug messages on pty2 show no deviating messages. Hope you can help! Roderick To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
