Re: FreeBSD MachO File format, your comments on it.
> Am 24.03.2016 um 10:13 schrieb mokhi : > > Hi guys. > I'm Mahdi Mokhtari (aka Mokhi between FreeBSD friends). > > I am working on adding Mach-O binary format to supported formats for FreeBSD. Would that project end in having an intelligent loader that will only map the relevant architecture to memory (i. e. I’ll have extremely fat executables supporting any known architecture in the universe on /usr/local or even for all files that can be shared between machines) and keep the load on memory and network as low as possible? Cool. I’ll buy immediately. Now if someone would add completely hassle-free automatic cross-compilation to building I feel like Christmas came early. (Just imagine an “one stick fits them all”-installer…) Achim smime.p7s Description: S/MIME cryptographic signature
Re: mfi driver performance
Am 10.09.2012 um 14:57 schrieb Steven Hartland: > How are you intending to use the controller? As a “launch-and-forget” RAID 1+0 sub-system using UFS (which reminds me to complain about sysinstall on volumes > 2 TB later). > If you're looking to put a load of disk in for say ZFS have you tried > flashing to a none RAID firmware so it uses mps instead of mfi? That would be wasting a perfectly good brain; the on-board SAS controller would be sufficient for that. Achim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
mfi driver performance
Hi!
We’re testing a new Intel S2600GL-based server with their recommended RAID
adapter ("Intel(R) Integrated RAID Module RMS25CB080”) which is identified as
mfi0: port 0x2000-0x20ff mem
0xd0c6-0xd0c63fff,0xd0c0-0xd0c3 irq 34 at device 0.0 on pci5
mfi0: Using MSI
mfi0: Megaraid SAS driver Ver 4.23
mfi0: MaxCmd = 3f0 MaxSgl = 46 state = b75003f0
or
mfi0@pci0:5:0:0:class=0x010400 card=0x35138086 chip=0x005b1000 rev=0x03
hdr=0x00
vendor = 'LSI Logic / Symbios Logic'
device = 'MegaRAID SAS 2208 [Thunderbolt]'
class = mass storage
subclass = RAID
and seems to be doing quite well.
As long as it isn’t used…
When the system is getting a bit more IO load it is getting close to unusable
as soon as there are a few writes (independent of configuration, it is even
sucking as a glorified S-ATA controller). Equipping it with an older
(unsupported) controller like an SRCSASRB
(mfi0@pci0:10:0:0: class=0x010400 card=0x100a8086 chip=0x00601000
rev=0x04 hdr=0x00
vendor = 'LSI Logic / Symbios Logic'
device = 'MegaRAID SAS 1078'
class = mass storage
subclass = RAID) solves the problem but won’t make Intel’s support happy.
Has anybody similar experiences with the mfi driver? Any good ideas besides
running an unsupported configuration?
Achim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Current, XEON and MP performance
I don't know where to ask first (or what to look at) so I'd like some creative guessing by some people closer to the sources... Running the same programs on nearly identically configured -CURRENT kernels on a HP NetServer LH4 (four 550 MHz PIII Xeon with 512MB Cache, supposed to be an INTEL 450NX-based chipset) with one GB RAM and a home-grown ASUS P2-BDS based system (two 450 MHz PIII) with 512 MB RAM I find that the programs (running on the same input data) on the "smaller" machine tend to take only a third of the CPU time they need on the LH4. [Worse: The LH4 behaves like a spoilt brat when it comes to hardware, disliking the Intel EtherExpress that came with it (generating bus mastering problems after bringing it up), having interrupt routing problems with two DEC TULIP based ethernet cards sharing the same IRQ and being picky just which 3C906B-TX it gets plugged in. It's a bitch and I'd like shooting it. Oh yes - HP has been very helpful, telling me that I was at least 10 years behind wanting to run a BSD and that only WinNT, HP-Sux and Linux were supported on this hardware.] Back to the topic: Are there any reasons for these observations? If someone liked taking a closer look at it I could provide them with access to the machine (and its console). I ran out of clues... Achim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
