From owner-freebsd-smp Mon May 14 12:41:25 2001 Delivered-To: freebsd-smp@freebsd.org Received: from munin.odin-corporation.com (munin.odin-corporation.com [216.233.173.18]) by hub.freebsd.org (Postfix) with ESMTP id 5DFEB37B423 for ; Mon, 14 May 2001 12:41:09 -0700 (PDT) (envelope-from lars@odin-corporation.com) Received: from odin-corporation.com (localhost [127.0.0.1]) by munin.odin-corporation.com (8.11.3/8.11.1) with ESMTP id f4EJewc01131 for ; Mon, 14 May 2001 14:40:58 -0500 (CDT) (envelope-from lars@odin-corporation.com) Message-ID: <3B0034CA.D6692771@odin-corporation.com> Date: Mon, 14 May 2001 14:40:58 -0500 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: smp@freebsd.org Subject: Any reason why we don't use irqs above 15 on SMP systems? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, A while back I seem to recall that if you ran on an SMP system, that you would end up with essentially 32 irqs. That doesn't seem to happen any more. This particular motherboard (Supermicro P6DNE) is configured with PNP OS set to yes. That is the only way I can get this box up and running. Otherwise, it assigns every PCI board irq 11, and a that point, no interupts are comming through. Thanks, Lars My mptable shows: =============================================================================== MPTable, version 2.0.15 looking for EBDA pointer @ 0x040e, found, searching EBDA @ 0x0009fc00 searching CMOS 'top of mem' @ 0x0009f800 (638K) searching default 'top of mem' @ 0x0009fc00 (639K) searching BIOS @ 0x000f0000 MP FPS found in BIOS @ physical addr: 0x000fb860 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000fb860 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0x46 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f7bd0 signature: 'PCMP' base table length: 252 version: 1.4 checksum: 0x02 OEM ID: 'INTEL ' Product ID: '440FX ' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 23 local APIC address: 0xfee00000 extended table length: 8 extended table checksum: 117 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 6 1 9 0xfbff 1 0x11 AP, usable 6 1 7 0xfbff -- Bus: Bus ID Type 0 PCI 1 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 1 0 2 0 INT conforms conforms 1 1 2 1 INT conforms conforms 1 0 2 2 INT conforms conforms 1 3 2 3 INT conforms conforms 1 4 2 4 INT conforms conforms 1 6 2 6 INT conforms conforms 1 8 2 8 INT conforms conforms 1 10 2 10 INT conforms conforms 1 12 2 12 INT conforms conforms 1 13 2 13 INT conforms conforms 1 14 2 14 INT conforms conforms 1 15 2 20 INT active-lo level 1 7 2 16 INT active-lo level 1 5 2 17 INT active-lo level 1 9 2 18 INT active-lo level 1 11 2 19 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0:A 255 0 NMI conforms conforms 0 0:A 255 1 ------------------------------------------------------------------------------- MP Config Extended Table Entries: -- Bus Heirarchy bus ID: 1 bus info: 0x01 parent bus ID: 0 =============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue May 15 8:31:44 2001 Delivered-To: freebsd-smp@freebsd.org Received: from midten.fast.no (midten.fast.no [213.188.8.11]) by hub.freebsd.org (Postfix) with ESMTP id 15F4E37B422 for ; Tue, 15 May 2001 08:31:40 -0700 (PDT) (envelope-from Tor.Egge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [213.188.8.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id RAA48069; Tue, 15 May 2001 17:31:35 +0200 (CEST) Message-Id: <200105151531.RAA48069@midten.fast.no> To: lars@odin-corporation.com Cc: smp@FreeBSD.ORG Subject: Re: Any reason why we don't use irqs above 15 on SMP systems? From: Tor.Egge@fast.no In-Reply-To: Your message of "Mon, 14 May 2001 14:40:58 -0500" References: <3B0034CA.D6692771@odin-corporation.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 15 May 2001 17:31:35 +0200 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > A while back I seem to recall that if you ran on an SMP system, that you > would end up with essentially 32 irqs. That doesn't seem to happen any > more. This particular motherboard (Supermicro P6DNE) is configured with > PNP OS set to yes. That is the only way I can get this box up and > running. Otherwise, it assigns every PCI board irq 11, and a that > point, no interupts are comming through. On -stable, it's 24 low level interrupt handlers. The binding of (APIC id, intpin) pairs to low level interrupt handler numbers is deferred for PCI devices until the probe routine asks for which interrupt the device uses. The first free low level interrupt handler is then allocated for that (APIC id, intpin) pair. Multiple PCI devices described in the MP table as sharing the same (APIC id, intpin) pair will share the same low level interrupt handler. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue May 15 13:58: 5 2001 Delivered-To: freebsd-smp@freebsd.org Received: from square.cnd.mcgill.ca (square.CND.McGill.CA [132.206.114.119]) by hub.freebsd.org (Postfix) with ESMTP id CD5F137B422 for ; Tue, 15 May 2001 13:58:00 -0700 (PDT) (envelope-from mat@square.cnd.mcgill.ca) Received: (from mat@localhost) by square.cnd.mcgill.ca (8.9.3/8.9.3) id QAA62597 for freebsd-smp@freebsd.org; Tue, 15 May 2001 16:58:00 -0400 (EDT) (envelope-from mat) Date: Tue, 15 May 2001 16:58:00 -0400 From: Mathew Kanner To: freebsd-smp@freebsd.org Subject: Success: DELL POWEREDGE 6450 Message-ID: <20010515165800.A62545@cnd.mcgill.ca> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: I speak for myself, operating in Montreal, CANADA Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello Group, Just a note to report that I've just had a great experience with FreeBSD 4.3 and a Dell PowerEdge 6450 Quad Pentium Xeon machine. Much to my surprise, I had the machine out of the box and installed with an SMP kernel within a half an hour. I did a floppy/network install, recompiled the kernel and added a local package to config for our network. Not a single problem or glitch. I've attached a dmesg for anybody who's curious. Many Thanks, --Mat --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.cube" Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-RELEASE #0: Tue May 15 11:25:38 GMT 2001 root@cube.cnd.mcgill.ca:/usr/src/sys/compile/CUBE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (699.29-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6a1 Stepping = 1 Features=0x383fbff real memory = 2147475456 (2097144K bytes) avail memory = 2087964672 (2039028K bytes) Changing APIC ID for IO APIC #0 from 0 to 4 on chip Changing APIC ID for IO APIC #1 from 0 to 5 on chip Programming 16 pins in IOAPIC #0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 3, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu2 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu3 (AP): apic id: 2, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 4, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000 Preloaded elf kernel "kernel" at 0xc03de000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib3: on motherboard IOAPIC #1 intpin 7 -> irq 2 IOAPIC #1 intpin 9 -> irq 5 pci3: on pcib3 pcib1: at device 9.0 on pci3 pci4: on pcib1 amr0: mem 0xfdc00000-0xfdffffff irq 2 at device 9.1 on pci3 amr0: Firmware 1.01, BIOS 1p00, 128MB RAM fxp0: port 0xccc0-0xccff mem 0xfaa00000-0xfaafffff,0xfabff000-0xfabfffff irq 5 at device 11.0 on pci3 fxp0: Ethernet address 00:02:b3:38:52:d2 pcib0: on motherboard IOAPIC #1 intpin 1 -> irq 10 IOAPIC #1 intpin 2 -> irq 11 IOAPIC #1 intpin 10 -> irq 13 IOAPIC #1 intpin 15 -> irq 16 pci0: on pcib0 pci0: at 4.0 ahc0: port 0xe800-0xe8ff mem 0xfbefe000-0xfbefefff irq 10 at device 5.0 on pci0 aic7899: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xe400-0xe4ff mem 0xfbefd000-0xfbefdfff irq 11 at device 5.1 on pci0 aic7899: Wide Channel B, SCSI Id=7, 32/255 SCBs fxp1: port 0xe0c0-0xe0ff mem 0xfbd00000-0xfbdfffff,0xfbefc000-0xfbefcfff irq 13 at device 8.0 on pci0 fxp1: Ethernet address 00:b0:d0:d0:f3:2b isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x8b0-0x8bf at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ohci0: mem 0xfbefb000-0xfbefbfff irq 16 at device 15.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (unknown) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pcib4: on motherboard pci5: on pcib4 pcib13: on motherboard pci13: on pcib13 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! acd0: CDROM at ata0-master using PIO4 Waiting 15 seconds for SCSI devices to settle amrd0: on amr0 amrd0: 34678MB (71020544 sectors) RAID 1 (optimal) amrd1: on amr0 amrd1: 34678MB (71020544 sectors) RAID 1 (optimal) no devsw (majdev=0 bootdev=0xa0200000) Mounting root from ufs:/dev/amrd0s1a --YZ5djTAD1cGYuMQK-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue May 15 15:38:21 2001 Delivered-To: freebsd-smp@freebsd.org Received: from hotmail.com (oe74.pav1.hotmail.com [64.4.30.209]) by hub.freebsd.org (Postfix) with ESMTP id 80D6537B423 for ; Tue, 15 May 2001 15:38:16 -0700 (PDT) (envelope-from claudevms@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 15 May 2001 15:38:15 -0700 X-Originating-IP: [204.124.92.190] From: "Bruce Allen" To: Cc: Subject: Ready to code... When can I start? Date: Tue, 15 May 2001 16:39:45 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C0DD5D.A640DE60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: X-OriginalArrivalTime: 15 May 2001 22:38:15.0792 (UTC) FILETIME=[BB3F3F00:01C0DD8F] Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C0DD5D.A640DE60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Operating system internals are fun. I just wish I had more time - I'm = married! What can I work on? I once added context switching to PC-XINU for the = math co-processor. I have programmed in assembly language and I know C.=20 Has anyone looked at how VMS handles interrupts (HW and SW)? I have, but = I'm partial to VMS. How about how VMS does threading? Or perhaps how VMS has asynchronous = system traps (ASTs) for allowing the programmer to do asynchronous programming. NT stole = ASTs from VMS and=20 broke them. There's many ways to skin the cat - unless you are an animal = rights person. I would love to see FreeBSD implement an interrptable kernel and support = the execution of application code in kernel mode through a system call. The global lock approach I read = about on your site sounds=20 like how DOS serialized its I/O - yuk! Other OSes have good features = that FreeBSD could benefit from. The Lustre project is attempting to create a VMS-like distributed lock = manager for Linux. I am working on doing the same thing for FreeBSD since I like the FreeBSD license = agreement better. I am also working on how=20 to make a share everything cluster work on FreeBSD. I'm still in the = very early stages. What efforts need help? My current job is boring and I miss the hell out = of software development - however it pays well! Thanks, Bruce ------=_NextPart_000_0007_01C0DD5D.A640DE60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
Operating system internals are fun. I just wish I = had more=20 time - I'm married!
What can I work on? I once added context switching = to PC-XINU=20 for the math co-processor.
I have programmed in assembly language and I know C. =
 
Has anyone looked at how VMS handles interrupts (HW = and SW)? I=20 have, but I'm partial to VMS.
How about how VMS does threading? Or perhaps how VMS = has=20 asynchronous system traps (ASTs)
for allowing the programmer to do asynchronous = programming. NT=20 stole ASTs from VMS and
broke them. There's many ways to skin the cat - = unless you are=20 an animal rights person.
I would love to see FreeBSD implement an = interrptable kernel=20 and support the execution of application code
in kernel mode through a system call. The global = lock approach=20 I read about on your site sounds
like how DOS serialized its I/O - yuk! Other OSes = have good=20 features that FreeBSD could benefit from.
 
The Lustre project is attempting to create a = VMS-like=20 distributed lock manager for Linux. I am working on
doing the same thing for FreeBSD since I like the = FreeBSD=20 license agreement better. I am also working on how
to make a share everything cluster work on FreeBSD. = I'm still=20 in the very early stages.
 
What efforts need help? My current job is boring and = I miss=20 the hell out of software development - however it pays = well!
 
 
Thanks,
 
Bruce
 
 
------=_NextPart_000_0007_01C0DD5D.A640DE60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue May 15 16:46:20 2001 Delivered-To: freebsd-smp@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 4DE9D37B423 for ; Tue, 15 May 2001 16:46:13 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 7A09E6ACBE; Wed, 16 May 2001 09:16:10 +0930 (CST) Date: Wed, 16 May 2001 09:16:10 +0930 From: Greg Lehey To: Bruce Allen Cc: freebsd-smp@freebsd.org, claudevms@home.com Subject: Re: Ready to code... When can I start? Message-ID: <20010516091610.J59553@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from claudevms@hotmail.com on Tue, May 15, 2001 at 04:39:45PM -0600 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Format recovered--see http://www.lemis.com/email/email-format.html] > Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C0DD5D.A640DE60" > X-Mailer: Microsoft Outlook Express 5.50.4133.2400 Your MUA is a known rogue which creates badly mutilated text. In this message, lines were up to 120 characters long. On Tuesday, 15 May 2001 at 16:39:45 -0600, Bruce Allen wrote: > Hi, > > Operating system internals are fun. I just wish I had more time - > I'm married! What can I work on? I once added context switching to > PC-XINU for the math co-processor. I have programmed in assembly > language and I know C. > > Has anyone looked at how VMS handles interrupts (HW and SW)? I have, > but I'm partial to VMS. How about how VMS does threading? Or > perhaps how VMS has asynchronous system traps (ASTs) for allowing > the programmer to do asynchronous programming. NT stole ASTs from > VMS and broke them. There's many ways to skin the cat - unless you > are an animal rights person. I would love to see FreeBSD implement > an interrptable kernel and support the execution of application code > in kernel mode through a system call. The global lock approach I > read about on your site sounds like how DOS serialized its I/O - > yuk! Other OSes have good features that FreeBSD could benefit from. I suspect you haven't read the paper at http://www.lemis.com/~grog/SMPng/USENIX/. We no longer have a giant lock. Note that VMS and UNIX are not very similar under the covers, and what works (well?) for VMS won't necessarily be appropriate for UNIX. I'd recommend that you get more familiar with what we've done so far, then compare that with the VMS solution. > The Lustre project is attempting to create a VMS-like distributed > lock manager for Linux. I am working on doing the same thing for > FreeBSD since I like the FreeBSD license agreement better. I am also > working on how to make a share everything cluster work on > FreeBSD. I'm still in the very early stages. I can't make much comment about distributed lock managers. Hopefully others will chip in. > What efforts need help? My current job is boring and I miss the hell > out of software development - however it pays well! Take a look at http://people.freebsd.org/~jasone/smp/. There's a lot of stuff there. Greg -- When replying to this message, please take care not to mutilate the original text. For more information, see http://www.lemis.com/email.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed May 16 6:52:45 2001 Delivered-To: freebsd-smp@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 05CFA37B424 for ; Wed, 16 May 2001 06:52:39 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id HAA62300; Wed, 16 May 2001 07:23:08 -0700 (PDT) Message-ID: <3B024E9A.57CB9C8D@elischer.org> Date: Wed, 16 May 2001 02:55:38 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Bruce Allen Cc: freebsd-smp@freebsd.org, claudevms@home.com Subject: Re: Ready to code... When can I start? References: Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Bruce Allen wrote: > > Hi, > > Operating system internals are fun. I just wish I had more time - I'm married! > What can I work on? I once added context switching to PC-XINU for the math > co-processor. > I have programmed in assembly language and I know C. > > Has anyone looked at how VMS handles interrupts (HW and SW)? I have, but I'm > partial to VMS. > How about how VMS does threading? Or perhaps how VMS has asynchronous system > traps (ASTs) > for allowing the programmer to do asynchronous programming. NT stole ASTs from > VMS and > broke them. There's many ways to skin the cat - unless you are an animal > rights person. > I would love to see FreeBSD implement an interrptable kernel and support the > execution of application code > in kernel mode through a system call. The global lock approach I read about on > your site sounds > like how DOS serialized its I/O - yuk! Other OSes have good features that > FreeBSD could benefit from. > > The Lustre project is attempting to create a VMS-like distributed lock manager > for Linux. I am working on > doing the same thing for FreeBSD since I like the FreeBSD license agreement > better. I am also working on how > to make a share everything cluster work on FreeBSD. I'm still in the very > early stages. At one stage simon shapiro (shimon@shapiro.org I think) did a distributed lock manager.. > > What efforts need help? My current job is boring and I > miss the hell out of > software development - however it pays well! Pick anything that interests you, see who else is interested (mainling list archives and cvs logs) and start. get ino the -current and -hackers lists and enjoy yourself.. You don't need to be invited in.. > > > Thanks, > > Bruce > > -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu May 17 1:11:22 2001 Delivered-To: freebsd-smp@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id 12D5337B423; Thu, 17 May 2001 01:11:19 -0700 (PDT) (envelope-from bright@superconductor.rush.net) Received: (from bright@localhost) by superconductor.rush.net (8.11.2/8.11.2) id f4H8BIR25613; Thu, 17 May 2001 04:11:18 -0400 (EDT) Date: Thu, 17 May 2001 04:11:17 -0400 From: Alfred Perlstein To: smp@freebsd.org Cc: jake@freebsd.org, jhb@freebsd.org, bp@freebsd.org Subject: please review, that pesky vm lock Message-ID: <20010517041116.O12365@superconductor.rush.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us X-all-your-base: are belong to us. Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The giant vm lock is pretty stable. The patch is here: http://people.freebsd.org/~alfred/vm.diff It makes it through a -j128 buildworld over FFS, and seems ok on NFS. Other filesystems will need a bit of work. I've cc'd some people directly. John, because you seem to be the SMPng lead right now. Jake, because you've taken an interest and been very helpful with this already Boris because of the VFS interaction. I'd appreciate getting your viewpoints on the patch. I'll having timing info on it RSN. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri May 18 1:35:55 2001 Delivered-To: freebsd-smp@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id C5F0537B423; Fri, 18 May 2001 01:35:52 -0700 (PDT) (envelope-from bright@superconductor.rush.net) Received: (from bright@localhost) by superconductor.rush.net (8.11.2/8.11.2) id f4I8Zqa07851; Fri, 18 May 2001 04:35:52 -0400 (EDT) Date: Fri, 18 May 2001 04:35:50 -0400 From: Alfred Perlstein To: smp@freebsd.org Cc: jake@freebsd.org, jhb@freebsd.org, bp@freebsd.org Subject: Re: please review, that pesky vm lock Message-ID: <20010518043550.O7118@superconductor.rush.net> References: <20010517041116.O12365@superconductor.rush.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <20010517041116.O12365@superconductor.rush.net>; from bright@rush.net on Thu, May 17, 2001 at 04:11:17AM -0400 X-all-your-base: are belong to us. Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: X-Loop: FreeBSD.org * Alfred Perlstein [010517 04:11] wrote: > The giant vm lock is pretty stable. The patch is here: > http://people.freebsd.org/~alfred/vm.diff > Updated patch is at the above url, several things were fixed: .) a race with vnode locking in the vnode pager was fixed. (alfred) .) vm_mtxp -> &vm_mtx (jake) .) all hadlock/haslock/waslock -> hadvmlock (jhb, jake) .) but with ordering trap_fatal fixed (jake) .) style (jhb, jake) .) don't aquire the lock just to drop it right away (jhb) .) don't aquire the lock just to test flags in the vmobject (jhb) .) fix comments to reflect the actual changes (jhb) -- -Alfred Perlstein [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri May 18 20: 4:46 2001 Delivered-To: freebsd-smp@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 3F93637B424; Fri, 18 May 2001 20:04:43 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id XAA08334; Fri, 18 May 2001 23:04:42 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f4J34C651777; Fri, 18 May 2001 23:04:12 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15109.58028.650986.78190@grasshopper.cs.duke.edu> Date: Fri, 18 May 2001 23:04:12 -0400 (EDT) To: Alfred Perlstein Cc: smp@freebsd.org, jake@freebsd.org, jhb@freebsd.org, bp@freebsd.org Subject: Re: please review, that pesky vm lock In-Reply-To: <20010518043550.O7118@superconductor.rush.net> References: <20010517041116.O12365@superconductor.rush.net> <20010518043550.O7118@superconductor.rush.net> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Alfred Perlstein writes: > * Alfred Perlstein [010517 04:11] wrote: > > The giant vm lock is pretty stable. The patch is here: > > http://people.freebsd.org/~alfred/vm.diff > > > > Updated patch is at the above url, several things were fixed: Two questions: Are you planning to make a pass through the MD code of other archs such as alpha & ia64 prior to commit? If not, please give me a heads up of at least 24-48 hours before you commit so that I can do alpha. I'd rather you did it, but I'm willing to take it on if nobody else is... Also, a number of files in the patch appear to have the addition of #include as their only change (coda/coda_namecache.c, linprocfs_misc.c, etc). Is this intentional? Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri May 18 20:49:30 2001 Delivered-To: freebsd-smp@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id BE9E937B422; Fri, 18 May 2001 20:49:27 -0700 (PDT) (envelope-from bright@superconductor.rush.net) Received: (from bright@localhost) by superconductor.rush.net (8.11.2/8.11.2) id f4J3nL916036; Fri, 18 May 2001 23:49:21 -0400 (EDT) Date: Fri, 18 May 2001 23:49:20 -0400 From: Alfred Perlstein To: Andrew Gallatin Cc: smp@FreeBSD.ORG, jake@FreeBSD.ORG, jhb@FreeBSD.ORG, bp@FreeBSD.ORG Subject: Re: please review, that pesky vm lock Message-ID: <20010518234920.T7118@superconductor.rush.net> References: <20010517041116.O12365@superconductor.rush.net> <20010518043550.O7118@superconductor.rush.net> <15109.58028.650986.78190@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <15109.58028.650986.78190@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Fri, May 18, 2001 at 11:04:12PM -0400 X-all-your-base: are belong to us. Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * Andrew Gallatin [010518 23:04] wrote: > > Alfred Perlstein writes: > > * Alfred Perlstein [010517 04:11] wrote: > > > The giant vm lock is pretty stable. The patch is here: > > > http://people.freebsd.org/~alfred/vm.diff > > > > > > > Updated patch is at the above url, several things were fixed: > > Two questions: > > Are you planning to make a pass through the MD code of other archs > such as alpha & ia64 prior to commit? If not, please give me a heads > up of at least 24-48 hours before you commit so that I can do alpha. > I'd rather you did it, but I'm willing to take it on if nobody else > is... I'm sorry, I had the patchset up for quite a while and committed it shortly before getting your message. As far as the alpha/ia64 the fixes should be trivial, you basically have: .) a couple of places where you'll catch assertions unless the vm lock is held, .) the chance to remove aquiring Giant from trap() .) a couple of places where you'll need to include sys/mutex.h to squash compiler errors. > Also, a number of files in the patch appear to have the addition of > #include as their only change (coda/coda_namecache.c, > linprocfs_misc.c, etc). Is this intentional? Yes, because of inline functions in the vm headers they require that certain defines are present for the assertions and structures used in those inlines. -- -Alfred Perlstein [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message