From owner-linux@cthulhu.engr.sgi.com Sat Feb 24 02:21:37 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id CAA01353; Sat, 24 Feb 1996 02:21:37 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) id CAA19391; Sat, 24 Feb 1996 02:21:36 -0800 Date: Sat, 24 Feb 1996 02:21:36 -0800 Message-Id: <199602241021.CAA19391@cthulhu.engr.sgi.com> To: linux-archive@neteng.engr.sgi.com From: Majordomo@cthulhu.engr.sgi.com Subject: Welcome to linux Reply-To: Majordomo@cthulhu.engr.sgi.com -- Welcome to the linux mailing list! If you ever want to remove yourself from this mailing list, you can send mail to "Majordomo@relay.engr.sgi.com" with the following command in the body of your email message: unsubscribe linux linux-archive@neteng.engr Here's the general information for the list you've subscribed to, in case you don't already have it: [Last updated on: Sat Feb 24 3:32:43 1996] This linux@engr.sgi.com mailing list is for those of us at SGI who believe Linux is a good thing that we shouldn't ignore or even better: do something proactive about it. As a first step we would like to see a port of Linux to the MIPS architecture happen. A mailing list of the interested people may accelerate this process by bringing the right people together. If you no longer wish to receive this list, send the following to linux-request@relay.engr.sgi.com: unsubscribe linux Ariel Faigon (ariel@engr) is the owner of this list. Happy Linuxing. From owner-linux@cthulhu.engr.sgi.com Wed Feb 28 10:16:37 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id KAA03923; Wed, 28 Feb 1996 10:16:37 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id KAA09495; Wed, 28 Feb 1996 10:16:34 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id KAA09486; Wed, 28 Feb 1996 10:16:32 -0800 Received: from localhost by neteng.engr.sgi.com via SMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id KAA03916; Wed, 28 Feb 1996 10:16:30 -0800 Message-Id: <199602281816.KAA03916@neteng.engr.sgi.com> To: linux@neteng.engr.sgi.com, greg@neteng.engr.sgi.com, jmb@neteng.engr.sgi.com, jmw@neteng.engr.sgi.com, nn@neteng.engr.sgi.com, aje@neteng.engr.sgi.com Subject: a chuckle for you Date: Wed, 28 Feb 1996 10:16:30 -0800 From: Larry McVoy Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Linus has a 300Mhz Alpha running linux. He's pissed at me because I didn't ever anticipate any OS being able to do a null system call (write a byte /dev/null) in a really short time. I measure in usecs, he needs nanoseconds. Think about it: he has an entry into the system so fast that he needs to measure it in nanoseconds. I included R10K, Ultrasparc, Alpha, and P6 numbers below Linus' note. --lm But Larry: we really do need more than microsecond accuracy: [torvalds@tiirakari linux]$ ./lat_syscall $Id: lat_syscall.c,v 1.2 1995/09/24 01:32:37 lm Exp $ Null syscall: 1 microseconds We're definitely approaching the limit.. Linus L M B E N C H 1 . 1 S U M M A R Y ------------------------------------ Processor, Processes - times in microseconds - smaller is better ---------------------------------------------------------------- Host OS Mhz Null sig sig fork exec sh call inst hndl Proc Proc Proc --------- ------------- ---- ---- ---- ---- ---- ---- ---- Alpha300 Linux 1.3.70 300 1 8 1 0.4K 1K 6K P6-aurora Linux 1.3.37 200 4 7 3 0.4K 5K 14K ultraspar SunOS 5.5 167 6 59 5 3.7K 20K 37K R10K IRIX64 6.2-no 200 4 15 9 1.8K 8K 13K Context switching - times in microseconds - smaller is better ------------------------------------------------------------- Host OS 2p/0K 2p/16K 2p/64K 8p/16K 8p/64K 16p/16K 16p/64K ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw --------- ------------- ----- ------ ------ ------ ------ ------- ------- Alpha300 Linux 1.3.70 2 14 97 26 150 35 151 P6-aurora Linux 1.3.37 6 12 32 14 325 50 327 ultraspar SunOS 5.5 14 51 30 90 185 96 204 R10K IRIX64 6.2-no 21 24 25 32 48 72 223 *Local* Communication latencies in microseconds - smaller is better ------------------------------------------------------------------- Host OS 2p/0K Pipe UDP RPC/ TCP RPC/ TCP ctxsw UDP TCP conn --------- ------------- ----- ----- ----- ----- ----- ----- ---- Alpha300 Linux 1.3.70 2 12 73 152 97 204 0 P6-aurora Linux 1.3.37 6 26 93 180 216 346 263 ultraspar SunOS 5.5 14 62 197 267 162 346 852 R10K IRIX64 6.2-no 21 74 362 829 197 390 951 File & VM system latencies in microseconds - smaller is better -------------------------------------------------------------- Host OS 0K File 10K File Mmap Prot Page Create Delete Create Delete Latency Fault Fault --------- ------------- ------ ------ ------ ------ ------- ----- ----- Alpha300 Linux 1.3.70 49 4 83 11 10 -1 0.0K P6-aurora Linux 1.3.37 75 4 213 35 36 -1 0.0K ultraspar SunOS 5.5 1818 833 2564 1851 212 -1 2.7K R10K IRIX64 6.2-no 374 389 353 387 55 -1 21.5K *Local* Communication bandwidths in MB/s - bigger is better ----------------------------------------------------------- Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem reread reread (libc) (hand) read write --------- ------------- ---- ---- ------ ------ ------ ------ ---- ----- Alpha300 Linux 1.3.70 131 38 108 114 65 66 129 110 P6-aurora Linux 1.3.37 89 18 40 36 56 42 208 56 ultraspar SunOS 5.5 61 51 85 101 167 85 129 152 R10K IRIX64 6.2-no 85 53 75 92 44 59 101 84 Memory latencies in nanoseconds - smaller is better (WARNING - may not be correct, check graphs) --------------------------------------------------- Host OS Mhz L1 $ L2 $ Main mem Guesses --------- ------------- --- ---- ---- -------- ------- Alpha300 Linux 1.3.70 300 0 48 360 P6-aurora Linux 1.3.37 200 10 53 179 ultraspar SunOS 5.5 166 6 42 270 R10K IRIX64 6.2-no 200 5 55 1115 From owner-linux@cthulhu.engr.sgi.com Thu Feb 29 10:26:55 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id KAA25174; Thu, 29 Feb 1996 10:26:55 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id KAA15611; Thu, 29 Feb 1996 10:26:13 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id KAA15600; Thu, 29 Feb 1996 10:26:12 -0800 Received: by neteng.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux@engr id KAA25153; Thu, 29 Feb 1996 10:26:11 -0800 Date: Thu, 29 Feb 1996 10:26:11 -0800 From: lm@neteng.engr.sgi.com (Larry McVoy) Message-Id: <199602291826.KAA25153@neteng.engr.sgi.com> To: linux@cthulhu.engr.sgi.com Subject: kernel hacking noise Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hi- I'm working with a guy at Rutgers that is doing the sparc linux ports. We're trying to get him in here this summer to do a mips linux port. Anyway, we have a lot of discussions going on about kernel performance hacks, etc. To me, and possibly to other OS hackers, they are really interesting (stuff like optimizing system entry costs - he went from 128 usecs to 3 on a sparc classic). I know there is a subset of the people on this list that might be interested in seeing this mail, but I don't know if the whole list wants to see it. The volume is typically 1-10 messages / day. What I want to know is would anyone on this list _not_ like to see this mail? If you don't reply, I'll assume it is OK with you. If you do reply, then I'll create a separate list for the kernel hacking. Thanks, --lm --- Larry McVoy lm@sgi.com http://reality.sgi.com/lm (415) 933-1804 Copyright 1996, all rights reserved. Microsoft Network is prohibited from redistributing this work in any form, in whole or in part without license. License to distribute this work is available to Microsoft at $500. Transmission without permission constitutes an agreement to these terms. From owner-linux@cthulhu.engr.sgi.com Thu Feb 29 22:40:25 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id WAA20453; Thu, 29 Feb 1996 22:40:24 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id WAA28253; Thu, 29 Feb 1996 22:40:01 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id WAA28248; Thu, 29 Feb 1996 22:40:00 -0800 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id WAA20448; Thu, 29 Feb 1996 22:39:58 -0800 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id WAA28241; Thu, 29 Feb 1996 22:39:50 -0800 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id WAA00361; Thu, 29 Feb 1996 22:39:41 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id BAA25636 for ; Fri, 1 Mar 1996 01:39:38 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id BAA23841; Fri, 1 Mar 1996 01:39:37 -0500 Date: Fri, 1 Mar 1996 01:39:37 -0500 Message-Id: <199603010639.BAA23841@huahaga.rutgers.edu> From: "David S. Miller" To: lmlinux@neteng.engr.sgi.com Subject: ./lat_syscall Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I was bored and got the benchmark down to 2 microseconds on the SparcClassic 50mhz cpus... pushing the envelope a bit I guess, I'll optimize other things now ;-) Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Fri Mar 1 05:13:55 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id FAA23971; Fri, 1 Mar 1996 05:13:55 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id PAA09124; Thu, 29 Feb 1996 15:33:43 -0800 Received: from leviathan.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id PAA09118; Thu, 29 Feb 1996 15:33:42 -0800 Received: by leviathan.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) id PAA19817; Thu, 29 Feb 1996 15:33:41 -0800 Date: Thu, 29 Feb 1996 15:33:41 -0800 From: brucet@leviathan.engr.sgi.com (Bruce A. Templeton) Message-Id: <199602292333.PAA19817@leviathan.engr.sgi.com> To: linux@leviathan.engr.sgi.com Subject: WWW: Linux in High-Performance Computing (fwd) Organization: Silicon Graphics, Inc. Mountain View, CA Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk ------- start of forwarded message ------- I'm starting a new WWW site devoted to research and applications of Linux in all aspects of high-performance computing, including parallel and distributed systems, high-speed networks and interconnects, symmetric multiprocessing, applications (including database systems, multimedia and machine vision, and file servers), and parallel languages. The goal of this page is to bring together links and documents on research projects as well as commercial products involving the use of Linux in these environments. Linux is a free POSIX-compatible UNIX clone which runs on 386/486/Pentium and Alpha-based systems. Because all of the source (including the kernel) is copylefted, it's an attractive operating system for people involved in operating systems and clustered-computing research. The complete operating system and thousands of applications are free, and it runs on inexpensive commidity PC hardware. I'd like to expose and promote Linux as an O/S alternative for research and teaching in high-performance systems. The Linux-HPC page is http://www.cs.cornell.edu/home/mdw/hpc/hpc.html If you're involved in parallel/networking systems work related to Linux, please feel free to contribute to these pages my sending e-mail to mdw@cs.cornell.edu. Thanks, M. Welsh, mdw@cs.cornell.edu U-Net hacker Cornell University Computer Science Department ------- end of forwarded message ------- -- Bruce A. Templeton brucet@engr.sgi.com Silicon Graphics Inc. (415) 933-3872 From owner-linux@cthulhu.engr.sgi.com Fri Mar 8 19:34:02 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id TAA15968; Fri, 8 Mar 1996 19:34:02 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA25116; Fri, 8 Mar 1996 19:33:58 -0800 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id TAA25111; Fri, 8 Mar 1996 19:33:57 -0800 Received: by yon.engr.sgi.com (940816.SGI.8.6.9/940406.SGI.AUTO) for linux id TAA11611; Fri, 8 Mar 1996 19:33:56 -0800 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199603090333.TAA11611@yon.engr.sgi.com> Subject: Some material for thought To: linux@yon.engr.sgi.com Date: Fri, 8 Mar 1996 19:33:54 -0800 (PST) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 1254 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hi All, It is Friday again, I hope that no announcement on buying another high-end company is coming this Monday. I had really bad timing with the Linux mailing list creation ... Anyway, since you're so busy and quiet and since the PowerPC Linux page (http://speedy.redhat.com/ppc/) just had some really good news (Linux on PPC is now real) I thought about maintaining the one email/week traffic. In the latest reorg memo, TJ wrote (quote): "We will increase competitive pressure on other suppliers such as Sun and HP and Wintel based PC products by directly attacking their low-end workstation offerings with superior technology and better price-performance." This is revolutionary thinking at SGI. Moreover, it is a clear green light from up above to change the way we think. Free-software should be a part of that strategy. So, please take some time, and read the following: http://info.engr.sgi.com/~ariel/linux/free-software.html (the first one was written for those who are not familiar with free software, for you it may be obvious) And then, read some specifics in: http://info.engr.sgi.com/~ariel/linux/ Send me your comments. Good or Bad. [Again, please don't distribute this beyond the list yet.] -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Sat Mar 9 18:04:15 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id SAA09229; Sat, 9 Mar 1996 18:04:14 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id SAA19431; Sat, 9 Mar 1996 18:04:10 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id SAA19426; Sat, 9 Mar 1996 18:04:09 -0800 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id SAA09224; Sat, 9 Mar 1996 18:04:07 -0800 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id SAA19417; Sat, 9 Mar 1996 18:04:06 -0800 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id SAA22326; Sat, 9 Mar 1996 18:04:04 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id VAA01784; Sat, 9 Mar 1996 21:03:48 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id VAA19761; Sat, 9 Mar 1996 21:03:48 -0500 Date: Sat, 9 Mar 1996 21:03:48 -0500 Message-Id: <199603100203.VAA19761@huahaga.rutgers.edu> From: "David S. Miller" To: lmlinux@neteng.engr.sgi.com CC: torvalds@cs.helsinki.fi, adrian@remus.rutgers.edu Subject: Linux 1.3.71 lmbench on Sparc Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Oh baby... we almost have the TCP latencies in our favor against SunOS, all other categories rip SunOS to shreds on the MicroSparcI. I plan on having results on the SS5 against Solaris-2.5 (adrian, I can release 2.5 benchmarks as long as it isn't 2.5.1beta right?) soon. L M B E N C H 1 . 0 S U M M A R Y ------------------------------------ Processor, Processes - times in microseconds -------------------------------------------- Host OS Mhz Null Null Simple /bin/sh Mmap 2-proc 8-proc Syscall Process Process Process lat ctxsw ctxsw --------- ------------- ---- ------- ------- ------- ------- ---- ------ ------ trombetas Linux 1.3.71 49 13 16.2K 49.6K 78K 324 86 97 negro.rut SunOS 4.1.3_U 49 124 18.3K 63.9K 110K 470 152 262 *Local* Communication latencies in microseconds ----------------------------------------------- Host OS Pipe UDP RPC/ TCP RPC/ UDP TCP --------- ------------- ------- ------- ------- ------- ------- trombetas Linux 1.3.71 300 1034 1780 1576 2834 negro.rut SunOS 4.1.3_U 890 1375 2287 1573 2804 *Local* Communication bandwidths in megabytes/second ---------------------------------------------------- Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem reread reread (libc) (hand) read write --------- ------------- ---- ---- ------ ------ ------ ------ ---- ----- trombetas Linux 1.3.71 8 3.2 23.5 20.0 18 25 41 36 negro.rut SunOS 4.1.3_U 4 2.0 19.5 8.2 18 24 41 36 Memory latencies in nanoseconds (WARNING - may not be correct, check graphs) -------------------------------------------- Host OS Mhz L1 $ L2 $ Main mem TLB Guesses --------- ------------- --- ---- ---- -------- --- ------- trombetas Linux 1.3.71 49 20 170 180 659 No L2 cache? negro.rut SunOS 4.1.3_U 49 20 175 183 -1 No L2 cache? From owner-linux@cthulhu.engr.sgi.com Sun Mar 10 10:48:58 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id KAA01205; Sun, 10 Mar 1996 10:48:58 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id KAA24676; Sun, 10 Mar 1996 10:48:50 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id KAA24671; Sun, 10 Mar 1996 10:48:44 -0800 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id KAA01201; Sun, 10 Mar 1996 10:48:43 -0800 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id WAA28992; Sat, 9 Mar 1996 22:09:31 -0800 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id WAA28536; Sat, 9 Mar 1996 22:09:30 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id BAA06806; Sun, 10 Mar 1996 01:09:29 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id BAA00381; Sun, 10 Mar 1996 01:09:24 -0500 Date: Sun, 10 Mar 1996 01:09:24 -0500 Message-Id: <199603100609.BAA00381@huahaga.rutgers.edu> From: "David S. Miller" To: adrian@remus.rutgers.edu CC: lmlinux@neteng.engr.sgi.com Subject: [tridge@cs.anu.edu.au: Linux on the AP+ - progress!] Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Is this fucking cool or what? Adrian, and the lmlinux people, please keep this to yourself as I don't know if he is allowed to publicize his work or not. Thanks. ;-) ------- Start of forwarded message ------- Date: Sun, 10 Mar 1996 17:00:15 +1100 From: Andrew Tridgell To: davem@caip.rutgers.edu Subject: Linux on the AP+ - progress! Reply-to: Andrew.Tridgell@anu.edu.au David, I've managed to get Linux on our AP1000+ booting up to the stage where it detects a Viking MMU and dies. The main problem was that the machine has no prom at all, so all the calls to the prom routines needed amputation to get it to work. Instead of a prom the hardware has a mechanism for loading a image from the front end at 0xF0000000 and launching it. I wrote a small boot loader that runs at this address then pulls a vmlinux from the front end then jumps to it. I finally got this working today. I've also written an ap_printk() routine that uses lda/sta to write to the front end, and wired both prom_printf() and printk() to that. I'll let you know as I make more progress, meanwhile here are the first signs of life from Linux/AP+: @load aout vmlinux 488k load finished @jumping to 0xf0004000 @Hello from Linux! @got to line 0198 @got to line 0206 @ARCH: @SUN4M @Uh oh, IDPROM had bogus id_machtype value <0> @Ethernet address: 0:0:0:0:0:0 @Loading srmmu MMU routines @Viking MMU detected. The '@' symbols and from my monitor program - they helped debugging the protocol. Cheers, Andrew PS: In case you can't remember a AP1000+ is a SuperSparc based distributed memory multicomputer made by Fujitsu. Ours has 16 cpus each with 16MB of ram. We will soon be upgrading it to 32 cpus with 64MB of ram in each and 128GB of disk. ------- End of forwarded message ------- From owner-linux@cthulhu.engr.sgi.com Thu Mar 14 02:23:50 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id CAA18142; Thu, 14 Mar 1996 02:23:49 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id CAA16030; Thu, 14 Mar 1996 02:23:45 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id CAA16025; Thu, 14 Mar 1996 02:23:43 -0800 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id CAA18137; Thu, 14 Mar 1996 02:23:43 -0800 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id CAA16020; Thu, 14 Mar 1996 02:23:42 -0800 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id CAA03175; Thu, 14 Mar 1996 02:23:41 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id FAA11619; Thu, 14 Mar 1996 05:21:17 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id FAA08455; Thu, 14 Mar 1996 05:21:16 -0500 Date: Thu, 14 Mar 1996 05:21:16 -0500 Message-Id: <199603141021.FAA08455@huahaga.rutgers.edu> From: "David S. Miller" To: torvalds@cs.helsinki.fi CC: lmlinux@neteng.engr.sgi.com Subject: Oh baby... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk We now officially slaughter SunOS ;-) Now on to Solaris, that piece of trash... L M B E N C H 1 . 0 S U M M A R Y ------------------------------------ Processor, Processes - times in microseconds -------------------------------------------- Host OS Mhz Null Null Simple /bin/sh Mmap 2-proc 8-proc Syscall Process Process Process lat ctxsw ctxsw --------- ------------- ---- ------- ------- ------- ------- ---- ------ ------ trombetas Linux 1.3.71 49 13 16.2K 49.6K 78K 324 86 97 trombetas Linux 1.3.71 50 13 16.8K 51.1K 80K 456 89 98 trombetas Linux 1.3.73 50 15 16.7K 50.6K 79K 332 87 101 negro.rut SunOS 4.1.3_U 49 124 18.3K 63.9K 110K 470 152 262 *Local* Communication latencies in microseconds ----------------------------------------------- Host OS Pipe UDP RPC/ TCP RPC/ UDP TCP --------- ------------- ------- ------- ------- ------- ------- trombetas Linux 1.3.71 300 1034 1780 1576 2834 trombetas Linux 1.3.71 285 1042 1800 1592 2788 trombetas Linux 1.3.73 295 1042 1802 1378 2632 negro.rut SunOS 4.1.3_U 890 1375 2287 1573 2804 *Local* Communication bandwidths in megabytes/second ---------------------------------------------------- Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem reread reread (libc) (hand) read write --------- ------------- ---- ---- ------ ------ ------ ------ ---- ----- trombetas Linux 1.3.71 8 3.2 23.5 20.0 18 25 41 36 trombetas Linux 1.3.71 8 3.5 22.2 18.2 18 24 41 36 trombetas Linux 1.3.73 8 3.9 23.5 20.0 18 25 41 36 negro.rut SunOS 4.1.3_U 4 2.0 19.5 8.2 18 24 41 36 Memory latencies in nanoseconds (WARNING - may not be correct, check graphs) -------------------------------------------- Host OS Mhz L1 $ L2 $ Main mem TLB Guesses --------- ------------- --- ---- ---- -------- --- ------- trombetas Linux 1.3.71 49 20 170 180 -1 No L2 cache? trombetas Linux 1.3.71 50 20 170 180 -1 No L2 cache? trombetas Linux 1.3.73 50 19 169 179 659 No L2 cache? negro.rut SunOS 4.1.3_U 49 20 175 183 -1 No L2 cache? From owner-linux@cthulhu.engr.sgi.com Fri Mar 15 10:45:18 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id KAA00576; Fri, 15 Mar 1996 10:45:18 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id KAA19267; Fri, 15 Mar 1996 10:45:12 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id KAA19253; Fri, 15 Mar 1996 10:45:11 -0800 Received: from deliverator.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id KAA00510; Fri, 15 Mar 1996 10:45:10 -0800 Received: from caipfs.rutgers.edu by deliverator.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) for id KAA15118; Fri, 15 Mar 1996 10:45:07 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id NAA26274; Fri, 15 Mar 1996 13:45:05 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id NAA24026; Fri, 15 Mar 1996 13:45:03 -0500 Date: Fri, 15 Mar 1996 13:45:03 -0500 Message-Id: <199603151845.NAA24026@huahaga.rutgers.edu> From: "David S. Miller" To: torvalds@cs.helsinki.fi CC: lmlinux@neteng.engr.sgi.com, adrian@remus.rutgers.edu Subject: wait Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Until you guys see the numbers coming up... Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Fri Mar 15 14:25:53 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id OAA26981; Fri, 15 Mar 1996 14:25:53 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id OAA25927; Fri, 15 Mar 1996 14:25:49 -0800 Received: from ares.esd.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id OAA25917; Fri, 15 Mar 1996 14:25:48 -0800 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) for <@ares.esd.sgi.com:linux@engr.sgi.com> id OAA04322; Fri, 15 Mar 1996 14:25:48 -0800 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id OAA24786; Fri, 15 Mar 1996 14:25:47 -0800 Date: Fri, 15 Mar 1996 14:25:47 -0800 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199603152225.OAA24786@fir.esd.sgi.com> To: linux@cthulhu.engr.sgi.com Subject: XFree86 source online? Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Is the XFree86 source online at SGI somewhere? I want to look at some of the code for PC graphics cards. From owner-linux@cthulhu.engr.sgi.com Fri Mar 15 20:45:24 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id UAA26538; Fri, 15 Mar 1996 20:45:24 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id UAA17908; Fri, 15 Mar 1996 20:45:20 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id UAA17901; Fri, 15 Mar 1996 20:45:19 -0800 Received: from localhost by neteng.engr.sgi.com via SMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id UAA26528; Fri, 15 Mar 1996 20:45:18 -0800 Message-Id: <199603160445.UAA26528@neteng.engr.sgi.com> To: linux@neteng.engr.sgi.com Subject: He he he Date: Fri, 15 Mar 1996 20:45:18 -0800 From: Larry McVoy Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I like news like this. By the way, we are really really close to signing David as a summer intern here. He's certainl'y a handful (the only person that I know that swears more than I do, and if you've hung out in B9, you know that's saying a lot :-) We're working on ways to channel all that energy and I think we have a plan. As soon as it is official, I'll post the details here. I think Ariel wants to have a Linux on SGI kickoff meeting soon - I hope folks are hip to that. ------- Forwarded Message Date: Fri, 15 Mar 1996 21:52:22 -0500 From: "David S. Miller" To: lm Subject: The Ultra 176MHZ I'm not impressed with it's performance at all. Ho hum... maybe that will change when I get Linux running on it, perhaps Solaris is the problem here. Later, David S. Miller davem@caip.rutgers.edu ------- End of Forwarded Message From owner-linux@cthulhu.engr.sgi.com Fri Mar 15 22:29:07 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id WAA26736; Fri, 15 Mar 1996 22:29:06 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id WAA24314; Fri, 15 Mar 1996 22:29:01 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id WAA24309; Fri, 15 Mar 1996 22:29:00 -0800 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id WAA26727; Fri, 15 Mar 1996 22:28:58 -0800 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id WAA24300; Fri, 15 Mar 1996 22:28:58 -0800 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id WAA19239; Fri, 15 Mar 1996 22:28:55 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id BAA15720; Sat, 16 Mar 1996 01:28:35 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id BAA05973; Sat, 16 Mar 1996 01:28:35 -0500 Date: Sat, 16 Mar 1996 01:28:35 -0500 Message-Id: <199603160628.BAA05973@huahaga.rutgers.edu> From: "David S. Miller" To: sparclinux@vger.rutgers.edu CC: tridge@cs.anu.edu.au, lmlinux@neteng.engr.sgi.com, apod@caip.rutgers.edu, kish@caip.rutgers.edu, rukshin@caip.rutgers.edu, hedrick@remus.rutgers.edu, fil@klinzhai.rutgers.edu, john@paul.rutgers.edu Subject: YEAH!!! Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk This is so cool, I cannot believe it! I was so elated when I logged into this thing I had to share it with everyone ;-) GO ANDY GO! Linux/AP+ (hibana) hibana login: davem Password: Linux hibana 1.3.71 #294 Sat Mar 16 10:57:57 EST 1996 sparc hibana:~$ cat /proc/cpuinfo cpu : Texas Instruments, Inc. - SuperSparc 50 fpu : SuperSparc on-chip FPU promlib : Version 0 Revision 0 wp : yes type : sun4m Elf Support : no BogoMips : 63.89 MMU type : TI Viking/MXCC invall : 4 invmm : 1156 invrnge : 7773 invpg : 9935 contexts : 65536 hibana:~$ ps -auxwww USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND davem 251 0.6 3.1 572 436 p2 S 17:21 0:00 -bash davem 260 0.0 1.0 228 148 p2 R 17:24 0:00 ps -auxwww root 1 0.0 1.0 188 148 ? S 16:31 0:01 init [2] root 2 0.0 0.0 0 0 ? SW 16:31 0:00 (kflushd) root 3 0.0 0.0 0 0 ? SW< 16:31 0:00 (kswapd) root 13 0.0 2.0 604 280 ? S 16:31 0:00 /usr/sbin/inetd root 22 0.4 1.9 592 272 ? S 16:31 0:15 in.telnetd root 35 0.0 0.7 168 108 1 S 16:31 0:00 /sbin/getty 9600 tty1 root 105 0.0 1.8 608 256 ? S 16:44 0:00 portmap root 223 0.1 1.9 592 268 ? S 17:18 0:00 in.telnetd root 227 0.2 3.3 568 452 p1 S 17:18 0:00 -sh root 235 0.0 3.3 568 452 p1 T 17:18 0:00 -sh root 250 0.4 1.9 592 272 ? S 17:21 0:00 in.telnetd tridge 25 0.0 3.3 572 460 p0 S 16:31 0:02 -bash tridge 224 0.1 3.1 564 428 p1 S 17:18 0:00 -bash hibana:~$ cat /proc/meminfo total: used: free: shared: buffers: cached: Mem: 13967360 7041024 6926336 2998272 4096 5001216 Swap: 0 0 0 MemTotal: 13640 kB MemFree: 6764 kB MemShared: 2928 kB Buffers: 4 kB Cached: 4884 kB SwapTotal: 0 kB SwapFree: 0 kB hibana:~$ Something to tell your grandkids about man. Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Sat Mar 16 03:59:14 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id DAA27247; Sat, 16 Mar 1996 03:59:14 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id DAA17604; Sat, 16 Mar 1996 03:59:10 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id DAA17599; Sat, 16 Mar 1996 03:59:09 -0800 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id DAA27241; Sat, 16 Mar 1996 03:59:08 -0800 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id DAA17593; Sat, 16 Mar 1996 03:59:07 -0800 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id DAA26770; Sat, 16 Mar 1996 03:59:06 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id GAA27166; Sat, 16 Mar 1996 06:59:05 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id GAA10448; Sat, 16 Mar 1996 06:59:04 -0500 Date: Sat, 16 Mar 1996 06:59:04 -0500 Message-Id: <199603161159.GAA10448@huahaga.rutgers.edu> From: "David S. Miller" To: torvalds@cs.helsinki.fi CC: lmlinux@neteng.engr.sgi.com, adrian@remus.rutgers.edu Subject: you want numbers? I got numbers... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk WHeee... L M B E N C H 1 . 0 S U M M A R Y ------------------------------------ Processor, Processes - times in microseconds -------------------------------------------- Host OS Mhz Null Null Simple /bin/sh Mmap 2-proc 8-proc Syscall Process Process Process lat ctxsw ctxsw --------- ------------- ---- ------- ------- ------- ------- ---- ------ ------ trombetas Linux 1.3.74 50 13 11.4K 45.0K 64K 326 82 93 trombetas Linux 1.3.74 50 13 8.7K 39.1K 53K 334 80 95 negro.rut SunOS 4.1.3_U 49 124 18.3K 63.9K 110K 470 152 262 madeira.r SunOS 5.5.1 13 40 35.7K 155.1K 298K 600 176 212 *Local* Communication latencies in microseconds ----------------------------------------------- Host OS Pipe UDP RPC/ TCP RPC/ UDP TCP --------- ------------- ------- ------- ------- ------- ------- trombetas Linux 1.3.74 295 1012 1774 1370 2614 trombetas Linux 1.3.74 285 1004 1776 1406 2614 negro.rut SunOS 4.1.3_U 890 1375 2287 1573 2804 madeira.r SunOS 5.5.1 557 1601 2065 1379 2508 *Local* Communication bandwidths in megabytes/second ---------------------------------------------------- Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem reread reread (libc) (hand) read write --------- ------------- ---- ---- ------ ------ ------ ------ ---- ----- trombetas Linux 1.3.74 8 3.9 23.5 21.1 18 25 41 36 trombetas Linux 1.3.74 9 3.8 25.0 21.1 18 25 41 36 negro.rut SunOS 4.1.3_U 4 2.0 19.5 8.2 18 24 41 36 madeira.r SunOS 5.5.1 8 6.9 13.9 19.5 18 18 40 36 Memory latencies in nanoseconds (WARNING - may not be correct, check graphs) -------------------------------------------- Host OS Mhz L1 $ L2 $ Main mem TLB Guesses --------- ------------- --- ---- ---- -------- --- ------- trombetas Linux 1.3.74 50 20 170 180 -1 No L2 cache? trombetas Linux 1.3.74 50 19 169 179 659 No L2 cache? negro.rut SunOS 4.1.3_U 49 20 175 183 -1 No L2 cache? madeira.r SunOS 5.5.1 12 - - - - Bad mhz? From owner-linux@cthulhu.engr.sgi.com Sun Mar 17 05:01:12 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id FAA02528; Sun, 17 Mar 1996 05:01:11 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id FAA12187; Sun, 17 Mar 1996 05:01:06 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id FAA12182; Sun, 17 Mar 1996 05:01:05 -0800 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id FAA02522; Sun, 17 Mar 1996 05:01:04 -0800 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id FAA12177; Sun, 17 Mar 1996 05:01:03 -0800 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id FAA04168; Sun, 17 Mar 1996 05:00:59 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id IAA28359; Sun, 17 Mar 1996 08:00:55 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id IAA22870; Sun, 17 Mar 1996 08:00:54 -0500 Date: Sun, 17 Mar 1996 08:00:54 -0500 Message-Id: <199603171300.IAA22870@huahaga.rutgers.edu> From: "David S. Miller" To: linux-kernel@vger.rutgers.edu CC: sparclinux@vger.rutgers.edu, lmlinux@neteng.engr.sgi.com Subject: whee... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk "No worries." -Andrew Tridgell All on the same exact hardware folks. L M B E N C H 1 . 0 S U M M A R Y ------------------------------------ Processor, Processes - times in microseconds -------------------------------------------- Host OS Mhz Null Null Simple /bin/sh Mmap 2-proc 8-proc Syscall Process Process Process lat ctxsw ctxsw --------- ------------- ---- ------- ------- ------- ------- ---- ------ ------ trombetas Linux 1.3.74 50 13 8.7K 39.1K 53K 334 80 95 negro.rut SunOS 4.1.3_U 49 124 18.3K 63.9K 110K 470 152 262 geneva.ru SunOS 5.5 50 31 33.7K 148.2K 274K 596 174 205 *Local* Communication latencies in microseconds ----------------------------------------------- Host OS Pipe UDP RPC/ TCP RPC/ UDP TCP --------- ------------- ------- ------- ------- ------- ------- trombetas Linux 1.3.74 285 1004 1776 1406 2614 negro.rut SunOS 4.1.3_U 890 1375 2287 1573 2804 geneva.ru SunOS 5.5 530 1563 2080 1354 2398 *Local* Communication bandwidths in megabytes/second ---------------------------------------------------- Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem reread reread (libc) (hand) read write --------- ------------- ---- ---- ------ ------ ------ ------ ---- ----- trombetas Linux 1.3.74 9 3.8 25.0 21.1 18 25 41 36 negro.rut SunOS 4.1.3_U 4 2.0 19.5 8.2 18 24 41 36 geneva.ru SunOS 5.5 8 7.0 12.6 19.5 18 18 40 36 Memory latencies in nanoseconds (WARNING - may not be correct, check graphs) -------------------------------------------- Host OS Mhz L1 $ L2 $ Main mem TLB Guesses --------- ------------- --- ---- ---- -------- --- ------- trombetas Linux 1.3.74 50 19 169 179 659 No L2 cache? negro.rut SunOS 4.1.3_U 49 20 175 183 -1 No L2 cache? geneva.ru SunOS 5.5 49 - - - - Bad mhz? From owner-linux@cthulhu.engr.sgi.com Sun Mar 17 13:07:58 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id NAA04515; Sun, 17 Mar 1996 13:07:58 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id NAA16971; Sun, 17 Mar 1996 13:07:54 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id NAA16964; Sun, 17 Mar 1996 13:07:53 -0800 Received: from deliverator.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id NAA04510; Sun, 17 Mar 1996 13:07:52 -0800 Received: from wauug.erols.com by deliverator.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) for id NAA16809; Sun, 17 Mar 1996 13:07:51 -0800 Received: (from niemi@localhost) by wauug.erols.com (8.7.4/8.7.3) id QAA06947; Sun, 17 Mar 1996 16:07:49 -0500 Date: Sun, 17 Mar 1996 16:07:49 -0500 (EST) From: "David C. Niemi" To: "David S. Miller" cc: lmlinux@neteng.engr.sgi.com Subject: Re: whee... In-Reply-To: <199603171300.IAA22870@huahaga.rutgers.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Sun, 17 Mar 1996, David S. Miller wrote: > > "No worries." -Andrew Tridgell > > All on the same exact hardware folks. > > > L M B E N C H 1 . 0 S U M M A R Y > ------------------------------------ Interesting results. Looks like a little more work is needed on TCP before Total Domination. Would you mind trying out the "fixed" Byte UNIX benchmarks? They are on wauug.erols.com in /pub/bench/unixbench-4.0-DELTA.tgz niemi@wauug.erols.com David.Niemi@mail.li.org 703-810-5538 Reston, VA USA A bear won't treat you so! You're satisfied to know When he chews you up he still respects you. -- Al Stewart From owner-linux@cthulhu.engr.sgi.com Mon Mar 18 03:14:40 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id DAA16828; Mon, 18 Mar 1996 03:14:39 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id DAA21641; Mon, 18 Mar 1996 03:14:35 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id DAA21632; Mon, 18 Mar 1996 03:14:34 -0800 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id DAA16823; Mon, 18 Mar 1996 03:14:33 -0800 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id DAA21622; Mon, 18 Mar 1996 03:14:32 -0800 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id DAA11636; Mon, 18 Mar 1996 03:14:31 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id GAA10267; Mon, 18 Mar 1996 06:14:30 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id GAA03222; Mon, 18 Mar 1996 06:14:29 -0500 Date: Mon, 18 Mar 1996 06:14:29 -0500 Message-Id: <199603181114.GAA03222@huahaga.rutgers.edu> From: "David S. Miller" To: torvalds@cs.helsinki.fi CC: lmlinux@neteng.engr.sgi.com Subject: 1.3.75 is a little better... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk 0.2MB improvement in TCP bandwidth... L M B E N C H 1 . 0 S U M M A R Y ------------------------------------ Processor, Processes - times in microseconds -------------------------------------------- Host OS Mhz Null Null Simple /bin/sh Mmap 2-proc 8-proc Syscall Process Process Process lat ctxsw ctxsw --------- ------------- ---- ------- ------- ------- ------- ---- ------ ------ trombetas Linux 1.3.74 50 15 9.2K 40.2K 54K 342 89 99 trombetas Linux 1.3.75 50 13 8.6K 34.0K 57K 338 81 105 negro.rut SunOS 4.1.3_U 49 124 18.3K 63.9K 110K 470 152 262 geneva.ru SunOS 5.5 50 31 33.7K 148.2K 274K 596 174 205 *Local* Communication latencies in microseconds ----------------------------------------------- Host OS Pipe UDP RPC/ TCP RPC/ UDP TCP --------- ------------- ------- ------- ------- ------- ------- trombetas Linux 1.3.74 285 1026 1754 1384 2582 trombetas Linux 1.3.75 295 1040 1798 1380 2606 negro.rut SunOS 4.1.3_U 890 1375 2287 1573 2804 geneva.ru SunOS 5.5 530 1563 2080 1354 2398 *Local* Communication bandwidths in megabytes/second ---------------------------------------------------- Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem reread reread (libc) (hand) read write --------- ------------- ---- ---- ------ ------ ------ ------ ---- ----- trombetas Linux 1.3.74 8 3.8 23.5 21.1 18 24 41 36 trombetas Linux 1.3.75 8 4.0 25.0 20.0 18 25 41 36 negro.rut SunOS 4.1.3_U 4 2.0 19.5 8.2 18 24 41 36 geneva.ru SunOS 5.5 8 7.0 12.6 19.5 18 18 40 36 Memory latencies in nanoseconds (WARNING - may not be correct, check graphs) -------------------------------------------- Host OS Mhz L1 $ L2 $ Main mem TLB Guesses --------- ------------- --- ---- ---- -------- --- ------- trombetas Linux 1.3.74 50 20 170 180 -1 No L2 cache? trombetas Linux 1.3.75 50 20 170 180 659 No L2 cache? negro.rut SunOS 4.1.3_U 49 20 175 183 -1 No L2 cache? geneva.ru SunOS 5.5 49 - - - - Bad mhz? From owner-linux@cthulhu.engr.sgi.com Mon Mar 18 06:08:15 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id GAA17082; Mon, 18 Mar 1996 06:08:15 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id GAA02804; Mon, 18 Mar 1996 06:08:10 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id GAA02799; Mon, 18 Mar 1996 06:08:09 -0800 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id GAA17076; Mon, 18 Mar 1996 06:08:08 -0800 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id GAA02793; Mon, 18 Mar 1996 06:08:07 -0800 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id GAA19354; Mon, 18 Mar 1996 06:08:05 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id JAA18628; Mon, 18 Mar 1996 09:08:03 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id JAA03959; Mon, 18 Mar 1996 09:08:02 -0500 Date: Mon, 18 Mar 1996 09:08:02 -0500 Message-Id: <199603181408.JAA03959@huahaga.rutgers.edu> From: "David S. Miller" To: torvalds@cs.helsinki.fi CC: lmlinux@neteng.engr.sgi.com, adrian@remus.rutgers.edu Subject: ccpenguin Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Not too bad at all. Pretty spiffy machine I guess. Although no match for Linus's ev5 running Linux. But when I get the port done on this thing I'll have comparable numbers ;-) Remember, no forwarding of this stuff. L M B E N C H 1 . 0 S U M M A R Y ------------------------------------ Processor, Processes - times in microseconds -------------------------------------------- Host OS Mhz Null Null Simple /bin/sh Mmap 2-proc 8-proc Syscall Process Process Process lat ctxsw ctxsw --------- ------------- ---- ------- ------- ------- ------- ---- ------ ------ ccpenguin SunOS 5.5.1 167 5 3.4K 19.5K 37K 184 13 19 *Local* Communication latencies in microseconds ----------------------------------------------- Host OS Pipe UDP RPC/ TCP RPC/ UDP TCP --------- ------------- ------- ------- ------- ------- ------- ccpenguin SunOS 5.5.1 54 197 273 163 330 *Local* Communication bandwidths in megabytes/second ---------------------------------------------------- Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem reread reread (libc) (hand) read write --------- ------------- ---- ---- ------ ------ ------ ------ ---- ----- ccpenguin SunOS 5.5.1 61 50.8 138.6 96.1 171 66 115 156 Memory latencies in nanoseconds (WARNING - may not be correct, check graphs) -------------------------------------------- Host OS Mhz L1 $ L2 $ Main mem TLB Guesses --------- ------------- --- ---- ---- -------- --- ------- ccpenguin SunOS 5.5.1 167 6 41 265 492 From owner-linux@cthulhu.engr.sgi.com Tue Mar 19 14:34:20 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id OAA20552; Tue, 19 Mar 1996 14:34:20 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id OAA24122; Tue, 19 Mar 1996 14:34:15 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id OAA24117; Tue, 19 Mar 1996 14:34:14 -0800 Received: from deliverator.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id OAA20513; Tue, 19 Mar 1996 14:34:13 -0800 Received: from caipfs.rutgers.edu by deliverator.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) for id OAA23098; Tue, 19 Mar 1996 14:12:16 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id QAA01124; Tue, 19 Mar 1996 16:22:28 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id QAA02688; Tue, 19 Mar 1996 16:22:27 -0500 Date: Tue, 19 Mar 1996 16:22:27 -0500 Message-Id: <199603192122.QAA02688@huahaga.rutgers.edu> From: "David S. Miller" To: torvalds@cs.helsinki.fi CC: lmlinux@neteng.engr.sgi.com Subject: holy shit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I just found a major bug which could have been massively affecting performance on the sun4m. New bench numbers soon hopefully. Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Tue Mar 26 19:00:25 1996 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id TAA12772; Tue, 26 Mar 1996 19:00:25 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id SAA28611; Tue, 26 Mar 1996 18:59:52 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id SAA28606; Tue, 26 Mar 1996 18:59:50 -0800 Received: from cthulhu.engr.sgi.com by neteng.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id SAA12736; Tue, 26 Mar 1996 18:59:49 -0800 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id SAA28599; Tue, 26 Mar 1996 18:59:48 -0800 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id SAA11135; Tue, 26 Mar 1996 18:59:33 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id VAA10508; Tue, 26 Mar 1996 21:58:47 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id VAA03837; Tue, 26 Mar 1996 21:58:46 -0500 Date: Tue, 26 Mar 1996 21:58:46 -0500 Message-Id: <199603270258.VAA03837@huahaga.rutgers.edu> From: "David S. Miller" To: lmlinux@neteng.engr.sgi.com CC: torvalds@cs.helsinki.fi, user@host.rutgers.edu, adrian@remus.rutgers.edu Subject: it keeps going and going and... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I should yank this 'davem' guys account, he's such a fucking abusive user. Grrr... ? uname -a Linux trombetas 1.3.77 #2 Tue Mar 26 19:47:52 EST 1996 sparc ? uptime 2:56am up 1:55, 3 users, load average: 28.65, 28.21, 24.86 ? ps -auxwww USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND davem 38 0.0 0.0 584 0 p0 SW 01:01 0:00 (bash) davem 1067 0.0 0.5 588 116 p1 S 01:39 0:00 -bash davem 1107 5.5 1.0 312 228 p1 R 01:39 4:01 top davem 1117 0.0 1.8 592 412 p2 S 01:40 0:01 -bash davem 1142 0.0 1.0 596 236 p3 S 01:40 0:00 -bash davem 1147 0.0 0.4 588 96 p4 S 01:40 0:00 -bash davem 1148 0.0 0.5 588 120 p6 S 01:40 0:00 -bash davem 1149 0.0 0.3 588 88 p7 S 01:40 0:00 -bash davem 1150 0.0 0.5 588 132 p5 S 01:40 0:00 -bash davem 1152 0.0 0.3 588 84 p8 S 01:40 0:00 -bash davem 1229 5.1 0.7 416 176 p7 R 01:40 3:42 find . davem 1230 5.1 0.7 416 176 p5 R 01:40 3:42 find . davem 1231 5.1 0.7 416 176 p8 R 01:40 3:41 find . davem 1232 5.1 0.7 416 176 p6 S 01:40 3:41 find . davem 1233 5.0 11.1 4452 2492 p4 R 01:40 3:37 emacs19 -i davem 1242 0.0 0.2 572 64 p9 S 01:43 0:00 /bin/bash -i davem 1261 3.4 3.1 1872 704 p9 R 01:44 2:22 xgas davem 1262 2.6 3.1 1872 708 p9 S 01:44 1:48 xgas davem 1263 0.3 3.0 1872 692 p9 S 01:44 0:12 xgas davem 1264 0.5 3.2 1872 716 p9 S 01:44 0:23 xgas davem 1269 0.0 0.2 148 64 p3 S 01:46 0:00 ./crashme +2000.80 666 100 1:10:30 2 davem 1286 5.0 0.2 152 64 p3 R 01:46 3:19 ./crashme +2000.80 681 100 16 2 subprocess davem 1422 4.6 0.2 156 64 p3 R 01:54 2:41 ./crashme +2000.80 782 100 117 2 subprocess davem 1484 4.3 0.2 156 56 p3 R 01:59 2:20 ./crashme +2000.80 839 100 174 2 subprocess davem 1489 4.3 0.2 156 56 p3 R 01:59 2:19 ./crashme +2000.80 844 100 179 2 subprocess davem 1505 4.3 0.2 156 52 p3 R 02:01 2:14 ./crashme +2000.80 860 100 195 2 subprocess davem 1516 4.3 0.2 152 56 p3 R 02:02 2:11 ./crashme +2000.80 871 100 206 2 subprocess davem 1525 4.2 0.2 156 52 p3 R 02:02 2:08 ./crashme +2000.80 880 100 215 2 subprocess davem 1652 4.0 0.3 152 68 p3 R 02:12 1:38 ./crashme +2000.80 999 100 334 2 subprocess davem 1767 3.8 0.3 156 68 p3 R 02:21 1:12 ./crashme +2000.80 1102 100 437 2 subprocess davem 1769 3.8 0.2 148 56 p3 R 02:21 1:11 ./crashme +2000.80 1104 100 439 2 subprocess davem 1885 3.5 0.2 152 64 p3 R 02:29 0:49 ./crashme +2000.80 1200 100 535 2 subprocess davem 1886 3.5 0.3 148 68 p3 R 02:29 0:49 ./crashme +2000.80 1201 100 536 2 subprocess davem 1901 3.5 0.2 152 52 p3 R 02:30 0:47 ./crashme +2000.80 1212 100 547 2 subprocess davem 1929 3.4 0.5 160 112 p3 R 02:32 0:41 ./crashme +2000.80 1240 100 575 2 subprocess davem 1981 3.3 0.5 160 116 p3 R 02:36 0:32 ./crashme +2000.80 1288 100 623 2 subprocess davem 2007 3.3 0.3 152 72 p3 R 02:38 0:28 ./crashme +2000.80 1310 100 645 2 subprocess davem 2021 3.3 0.3 148 72 p3 R 02:39 0:26 ./crashme +2000.80 1324 100 659 2 subprocess davem 2027 3.3 0.3 156 76 p3 R 02:40 0:24 ./crashme +2000.80 1330 100 665 2 subprocess davem 2076 3.3 0.3 148 72 p3 R 02:44 0:17 ./crashme +2000.80 1376 100 711 2 subprocess davem 2132 3.3 0.3 156 80 p3 R 02:47 0:09 ./crashme +2000.80 1421 100 756 2 subprocess davem 2155 3.4 0.3 148 72 p3 R 02:49 0:06 ./crashme +2000.80 1440 100 775 2 subprocess davem 2200 0.0 0.8 272 196 p2 R 02:52 0:00 ps -auxwww root 1 0.0 0.0 188 0 ? SW 01:01 0:04 (init) root 2 0.0 0.0 0 0 ? SW 01:01 0:01 (kflushd) root 3 0.0 0.0 0 0 ? SW< 01:01 0:01 (kswapd) root 7 0.0 0.1 116 28 ? S 01:01 0:01 update (bdfluHOME=/ root 23 0.0 0.1 628 24 ? S 01:01 0:00 (inetd) root 25 0.0 0.0 636 12 ? S 01:01 0:00 (portmap) root 36 0.1 0.2 668 48 ? S 01:01 0:07 /usr/etc/in.telnetd root 39 0.0 0.0 152 0 1 SW 01:02 0:00 (getty) root 40 0.0 0.0 152 0 2 SW 01:02 0:00 (getty) root 41 0.0 0.0 152 0 3 SW 01:02 0:00 (getty) root 42 0.0 0.0 152 0 4 SW 01:02 0:00 (getty) root 43 0.0 0.0 152 0 5 SW 01:02 0:00 (getty) root 44 0.0 0.0 152 0 6 SW 01:02 0:00 (getty) root 68 0.0 0.0 900 0 p0 SW 01:02 0:02 (bash) root 120 0.0 0.0 584 0 p0 SW 01:04 0:00 (bash) root 134 0.0 0.0 584 0 p0 SW 01:04 0:00 (bash) root 148 0.0 0.0 584 0 p0 SW 01:04 0:00 (bash) root 162 0.0 0.0 584 0 p0 SW 01:04 0:00 (bash) root 176 0.0 0.0 584 0 p0 SW 01:04 0:00 (bash) root 190 0.0 0.0 584 0 p0 SW 01:04 0:00 (bash) root 205 0.0 0.0 584 0 p0 SW 01:05 0:00 (bash) root 219 0.0 0.0 584 0 p0 SW 01:05 0:00 (bash) root 233 0.0 0.0 584 0 p0 SW 01:05 0:00 (bash) root 247 0.0 0.0 584 0 p0 SW 01:05 0:00 (bash) root 261 0.0 0.0 584 0 p0 SW 01:05 0:00 (bash) root 275 0.0 0.0 584 0 p0 SW 01:05 0:00 (bash) root 290 0.0 0.0 584 0 p0 SW 01:05 0:00 (bash) root 304 0.0 0.0 584 0 p0 SW 01:05 0:00 (bash) root 318 0.0 0.0 584 0 p0 SW 01:05 0:00 (bash) root 332 0.0 0.0 584 0 p0 SW 01:05 0:00 (bash) root 346 0.0 0.0 584 0 p0 SW 01:05 0:00 (bash) root 360 0.0 0.0 584 0 p0 SW 01:05 0:00 (bash) root 401 0.0 0.0 584 0 p0 SW 01:06 0:00 (bash) root 415 0.0 0.0 584 0 p0 SW 01:06 0:00 (bash) root 429 0.0 0.0 584 0 p0 SW 01:06 0:00 (bash) root 443 0.0 0.0 584 0 p0 SW 01:06 0:00 (bash) root 457 0.0 0.0 584 0 p0 SW 01:06 0:00 (bash) root 471 0.0 0.0 584 0 p0 SW 01:06 0:00 (bash) root 485 0.0 0.0 584 0 p0 SW 01:06 0:00 (bash) root 501 0.0 0.0 108 0 p0 SW 01:07 0:00 (sh) root 502 0.0 0.0 108 0 p0 SW 01:07 0:00 (sh) root 503 0.0 0.0 112 0 p0 SW 01:07 0:00 (sh) root 504 0.0 0.0 584 0 p0 SW 01:07 0:00 (bash) root 518 0.0 0.0 584 0 p0 SW 01:07 0:00 (bash) root 532 0.0 0.0 584 0 p0 SW 01:07 0:00 (bash) root 546 0.0 0.0 584 0 p0 SW 01:07 0:00 (bash) root 560 0.0 0.0 584 0 p0 SW 01:07 0:00 (bash) root 574 0.0 0.0 592 0 p0 SW 01:07 0:00 (bash) root 721 0.0 0.5 888 116 p0 S 01:12 0:01 (make) root 757 0.0 0.9 552 204 p0 S 01:15 0:00 /bin/bash -c set -e; for i in kernel drivers mm fs net ipc lib arch/sparc/kernel arch/sparc/lib arch/sparc/mm arch/sparc/prom; do make -C $i; done root 1064 0.2 3.8 1976 856 ? S 01:39 0:09 xterm -T trombetas root 1085 0.0 0.5 604 124 p1 T 01:39 0:00 /bin/bash root 1116 0.0 0.8 668 180 ? S 01:40 0:01 /usr/etc/in.telnetd root 1138 0.5 3.7 1976 848 p2 S 01:40 0:23 xterm root 1139 4.0 2.9 1960 668 p2 S 01:40 2:55 xterm root 1140 4.0 2.9 1960 652 p2 S 01:40 2:54 xterm root 1141 0.0 2.8 1960 644 p2 S 01:40 0:00 xterm root 1143 4.0 2.9 1960 656 p2 S 01:40 2:56 xterm root 1144 4.0 2.9 1960 648 p2 S 01:40 2:55 xterm root 1293 0.0 1.0 588 228 p3 S 01:46 0:00 /bin/bash root 1481 0.0 0.6 612 148 p3 S 01:59 0:00 (tail) root 2102 0.2 2.5 888 560 p0 S 02:46 0:01 make -C fs root 2112 0.0 0.4 112 100 p0 S 02:46 0:00 /bin/sh -c set -e; for i in ext2 proc nfs; do make -C $i; done root 2113 0.2 2.4 868 544 p0 S 02:46 0:01 make -C ext2 root 2123 0.3 2.4 876 548 p0 S 02:47 0:01 make all_targets root 2173 0.1 1.1 660 268 p0 S 02:50 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -g -pipe -c -o balloc.o balloc.c root 2174 1.1 3.8 1332 856 p0 S 02:51 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 2175 2.9 10.9 3396 2452 p0 R 02:51 0:03 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase balloc.c -g -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 2176 0.2 3.0 1204 680 p0 S 02:51 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o balloc.o ? top 2:53am up 1:51, 3 users, load average: 28.51, 27.67, 23.85 112 processes: 83 sleeping, 28 running, 0 zombie, 1 stopped CPU states: 43.7% user, 54.4% system, 95.8% nice, 4.2% idle Mem: 22344K av, 21976K used, 368K free, 12056K shrd, 5308K buf 328K ca Swap: 65516K av, 6648K used, 58868K free PID USER PRI NI SIZE RES SHRD STAT %CPU %MEM TIME COMMAND 1767 davem 16 15 156 56 36 R 3.2 0.2 1:13 ./crashme +2000.80 1 1652 davem 17 15 152 60 40 R 3.1 0.2 1:39 ./crashme +2000.80 9 1107 davem 15 15 312 228 104 R 3.1 1.0 4:02 top 1886 davem 13 15 148 64 44 R 3.1 0.2 0:50 ./crashme +2000.80 1 1286 davem 19 15 152 64 44 R 3.1 0.2 3:20 ./crashme +2000.80 6 1233 davem 16 15 4452 2456 1308 R 3.0 10.9 3:38 emacs19 -i 1229 davem 18 15 416 176 80 R 2.9 0.7 3:43 find . 1422 davem 12 15 156 56 36 R 2.9 0.2 2:42 ./crashme +2000.80 7 1505 davem 11 15 156 52 32 R 2.9 0.2 2:15 ./crashme +2000.80 8 1516 davem 11 15 152 52 32 R 2.9 0.2 2:12 ./crashme +2000.80 8 1981 davem 10 15 160 112 76 R 2.9 0.5 0:33 ./crashme +2000.80 1 2076 davem 19 15 148 68 44 R 2.9 0.3 0:18 ./crashme +2000.80 1 1769 davem 20 15 148 56 36 R 2.9 0.2 1:12 ./crashme +2000.80 1 1929 davem 17 15 160 108 76 R 2.9 0.4 0:42 ./crashme +2000.80 1 2132 davem 17 15 156 76 44 R 2.9 0.3 0:10 ./crashme +2000.80 1 2027 davem 15 15 156 68 40 R 2.9 0.3 0:26 ./crashme +2000.80 1 2155 davem 14 15 148 64 40 R 2.9 0.2 0:08 ./crashme +2000.80 1 From owner-linux@cthulhu.engr.sgi.com Mon Apr 1 04:44:20 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA27456; Mon, 1 Apr 1996 04:44:20 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id EAA27470; Mon, 1 Apr 1996 04:43:00 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id EAA27464; Mon, 1 Apr 1996 04:42:45 -0800 Received: from deliverator.sgi.com (deliverator.sgi.com [150.166.91.37]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA26890 for ; Mon, 1 Apr 1996 04:42:26 -0800 Received: from caipfs.rutgers.edu by deliverator.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) id EAA20331; Mon, 1 Apr 1996 04:42:23 -0800 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id HAA07688; Mon, 1 Apr 1996 07:42:15 -0500 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id HAA00427; Mon, 1 Apr 1996 07:42:15 -0500 Date: Mon, 1 Apr 1996 07:42:15 -0500 Message-Id: <199604011242.HAA00427@huahaga.rutgers.edu> From: "David S. Miller" To: sparclinux@vger.rutgers.edu CC: linux-kernel@vger.rutgers.edu, linux-smp@vger.rutgers.edu, lmlinux@neteng.engr.sgi.com, user@host.rutgers.edu Subject: SYMMMMETRRRRIC MULTI PENGUINNNNNNN!!!!!! Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk (yeah, it runs shell and basic programs, I can telnet out etc. but it hard-locks now and then, working on it...) Any questions? And remember kids, Linux is just a "toy operating system." PROMLIB: Sun Boot Prom Version 3 Revision 2 ARCH: SUN4M TYPE: Sun4m SparcStation10 Ethernet address: 8:0:20:12:53:32 Found 4 CPU prom device tree node(s). IOMMU: impl 0 vers 1 page table at f03c0000 of size 65536 bytes sbus0: Clock 20.0 MHz dma0: Revision 2 dma1: Revision 2 cgsix0 at 0x20000000 Console: 16 point font, 864 scans Console: colour SUN 128x54, 1 virtual console (max 63) Calibrating delay loop.. ok - 115.51 BogoMIPS Memory: 175720k available (948k kernel code, 2988k data) Swansea University Computer Society NET3.033 for Linux 1.3.50 NET3: Unix domain sockets 0.12 for Linux NET3.033. Swansea University Computer Society TCP/IP for NET3.033 IP Protocols: ICMP, UDP, TCP Linux version 1.3.77 (davem@huahaga.rutgers.edu) (gcc version 2.6.3) #15 Mon Apr 1 07:02:51 EST 1996 Entering SparclinuxMultiPenguin(SMP) Mode... Starting CPU 1 at f002a9b8 Calibrating delay loop.. ok - 115.92 BogoMIPS Starting CPU 2 at f002a9d0 Calibrating delay loop.. ok - 104.86 BogoMIPS Starting CPU 3 at f002a9e8 Calibrating delay loop.. ok - 104.86 BogoMIPS Total of 4 Penguins activated (441.14 PenguinMIPS). Sparc Zilog8530 serial driver version 1.00 tty00 at 0xffede004 (irq = 44) is a Zilog8530 tty01 at 0xffede000 (irq = 44) is a Zilog8530 tty02 at 0xffedb004 (irq = 44) is a Zilog8530 tty03 at 0xffedb000 (irq = 44) is a Zilog8530 Sun TYPE 4 keyboard detected without keyclick Sun Mouse-Systems mouse driver version 1.00 esp0: IRQ 36 SCSI ID 7 Clock 20 MHz Period 99 NCR53C9x(esp236) detected scsi0 : Sparc ESP236 scsi : 1 host. Started kswapd v 1.5 Vendor: SEAGATE Model: ST32430N SUN2.1G Rev: 0444 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sda at scsi0, channel 0, id 3, lun 0 scsi : detected 1 SCSI disk total. SCSI Hardware sector size is 512 bytes on device sda sunlance.c:v1.5 21/Mar/96 Miguel de Icaza (miguel@nuclecu.unam.mx) eth0: LANCE 08:00:20:12:53:32 Partition check: sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 Sending BOOTP and RARP requests.....OK Root-NFS: Got RARP answer from 128.6.155.101, my address is 128.6.155.53 Root-NFS: Got file handle for /caip/u119/davem/SparcLinux/machines/jenolan via RPC VFS: Mounted root (nfs filesystem). # mount -n -t proc none /proc # cat /proc/cpuinfo cpu : ROSS HyperSparc RT625 fpu : ROSS HyperSparc combined IU/FPU promlib : Version 3 Revision 2 type : sun4m Elf Support : yes Cpu0Bogo : 115.50 Cpu1Bogo : 115.91 Cpu2Bogo : 104.85 Cpu3Bogo : 104.85 MMU type : ROSS HyperSparc invall : 4020 invmm : 0 invrnge : 0 invpg : 0 contexts : 4096 big_chunks : 0 little_chunks : 0 CPU0 CPU1 CPU2 CPU3 State: online online online akp Lock: 2 2 2 2 klock: ff block: 0 alock: 0 From owner-linux@cthulhu.engr.sgi.com Mon Apr 1 18:08:55 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA12235; Mon, 1 Apr 1996 18:08:54 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id SAA09424; Mon, 1 Apr 1996 18:08:50 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id SAA09419; Mon, 1 Apr 1996 18:08:47 -0800 Received: from deliverator.sgi.com (deliverator.sgi.com [150.166.91.37]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA12221 for ; Mon, 1 Apr 1996 18:08:45 -0800 Received: from mike.netrom.com by deliverator.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) for id SAA10818; Mon, 1 Apr 1996 18:08:36 -0800 Received: from mike.netrom.com (john@mike.netrom.com [204.141.216.12]) by mike.netrom.com (8.6.12/8.6.11) with SMTP id VAA05521; Mon, 1 Apr 1996 21:01:45 -0500 Date: Mon, 1 Apr 1996 21:01:44 -0500 (EST) From: John Vozza To: "David S. Miller" cc: sparclinux@vger.rutgers.edu, linux-kernel@vger.rutgers.edu, linux-smp@vger.rutgers.edu, lmlinux@neteng.engr.sgi.com, user@host.rutgers.edu Subject: Re: SYMMMMETRRRRIC MULTI PENGUINNNNNNN!!!!!! In-Reply-To: <199604011242.HAA00427@huahaga.rutgers.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Can you say jealous!!!! Just had to reply... plz no flames! Sure beats my 486dx100 =( On Mon, 1 Apr 1996, David S. Miller wrote: > > (yeah, it runs shell and basic programs, I can telnet out etc. > but it hard-locks now and then, working on it...) > > Any questions? And remember kids, Linux is just a "toy operating > system." > > PROMLIB: Sun Boot Prom Version 3 Revision 2 > ARCH: SUN4M > TYPE: Sun4m SparcStation10 > Ethernet address: 8:0:20:12:53:32 > Found 4 CPU prom device tree node(s). > IOMMU: impl 0 vers 1 page table at f03c0000 of size 65536 bytes > sbus0: Clock 20.0 MHz > dma0: Revision 2 > dma1: Revision 2 > cgsix0 at 0x20000000 > Console: 16 point font, 864 scans > Console: colour SUN 128x54, 1 virtual console (max 63) > Calibrating delay loop.. ok - 115.51 BogoMIPS > Memory: 175720k available (948k kernel code, 2988k data) > Swansea University Computer Society NET3.033 for Linux 1.3.50 > NET3: Unix domain sockets 0.12 for Linux NET3.033. > Swansea University Computer Society TCP/IP for NET3.033 > IP Protocols: ICMP, UDP, TCP > Linux version 1.3.77 (davem@huahaga.rutgers.edu) (gcc version 2.6.3) #15 Mon Apr 1 07:02:51 EST 1996 > Entering SparclinuxMultiPenguin(SMP) Mode... > Starting CPU 1 at f002a9b8 > Calibrating delay loop.. ok - 115.92 BogoMIPS > Starting CPU 2 at f002a9d0 > Calibrating delay loop.. ok - 104.86 BogoMIPS > Starting CPU 3 at f002a9e8 > Calibrating delay loop.. ok - 104.86 BogoMIPS > Total of 4 Penguins activated (441.14 PenguinMIPS). > Sparc Zilog8530 serial driver version 1.00 > tty00 at 0xffede004 (irq = 44) is a Zilog8530 > tty01 at 0xffede000 (irq = 44) is a Zilog8530 > tty02 at 0xffedb004 (irq = 44) is a Zilog8530 > tty03 at 0xffedb000 (irq = 44) is a Zilog8530 > Sun TYPE 4 keyboard detected without keyclick > Sun Mouse-Systems mouse driver version 1.00 > esp0: IRQ 36 SCSI ID 7 Clock 20 MHz Period 99 NCR53C9x(esp236) detected > scsi0 : Sparc ESP236 > scsi : 1 host. > Started kswapd v 1.5 > Vendor: SEAGATE Model: ST32430N SUN2.1G Rev: 0444 > Type: Direct-Access ANSI SCSI revision: 02 > Detected scsi disk sda at scsi0, channel 0, id 3, lun 0 > scsi : detected 1 SCSI disk total. > SCSI Hardware sector size is 512 bytes on device sda > sunlance.c:v1.5 21/Mar/96 Miguel de Icaza (miguel@nuclecu.unam.mx) > eth0: LANCE 08:00:20:12:53:32 > Partition check: > sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 > Sending BOOTP and RARP requests.....OK > Root-NFS: Got RARP answer from 128.6.155.101, my address is 128.6.155.53 > Root-NFS: Got file handle for /caip/u119/davem/SparcLinux/machines/jenolan via RPC > VFS: Mounted root (nfs filesystem). > # mount -n -t proc none /proc > # cat /proc/cpuinfo > cpu : ROSS HyperSparc RT625 > fpu : ROSS HyperSparc combined IU/FPU > promlib : Version 3 Revision 2 > type : sun4m > Elf Support : yes > Cpu0Bogo : 115.50 > Cpu1Bogo : 115.91 > Cpu2Bogo : 104.85 > Cpu3Bogo : 104.85 > MMU type : ROSS HyperSparc > invall : 4020 > invmm : 0 > invrnge : 0 > invpg : 0 > contexts : 4096 > big_chunks : 0 > little_chunks : 0 > CPU0 CPU1 CPU2 CPU3 > State: online online online akp > Lock: 2 2 2 2 > > klock: ff > block: 0 > alock: 0 > From owner-linux@cthulhu.engr.sgi.com Sat Apr 6 21:36:38 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id VAA24789; Sat, 6 Apr 1996 21:36:38 -0800 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id VAA22757; Sat, 6 Apr 1996 21:36:29 -0800 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id VAA22752; Sat, 6 Apr 1996 21:36:27 -0800 Received: from deliverator.sgi.com (deliverator.sgi.com [150.166.91.37]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id VAA24779 for ; Sat, 6 Apr 1996 21:36:26 -0800 Received: from caipfs.rutgers.edu by deliverator.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) id VAA14783; Sat, 6 Apr 1996 21:36:23 -0800 Received: from caip.rutgers.edu (caip.rutgers.edu [128.6.19.83]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id AAA22276; Sun, 7 Apr 1996 00:36:21 -0500 Received: (davem@localhost) by caip.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id AAA13292; Sun, 7 Apr 1996 00:36:21 -0500 Date: Sun, 7 Apr 1996 00:36:21 -0500 Message-Id: <199604070536.AAA13292@caip.rutgers.edu> From: "David S. Miller" To: sparclinux@vger.rutgers.edu CC: lmlinux@neteng.engr.sgi.com, user@host.rutgers.edu Subject: ho hum... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Can your multi-national, client server, multi-threaded, customer ready bloat OS with enhanced interoperability do this? ? ps -auxwww | grep crashme davem 5869 0.0 0.0 148 68 p4 S 05:02 0:00 ./crashme +2000.80 666 100 1:10:30 2 davem 5885 10.0 0.0 152 76 p4 R 05:02 2:47 ./crashme +2000.80 681 100 16 2 subprocess davem 5888 0.0 0.0 148 68 p4 S 05:02 0:00 ./crashme +2000 666 100 1:10:30 2 davem 5915 9.6 0.1 348 268 p4 R 05:03 2:39 ./crashme +2000 686 100 21 2 subprocess davem 5997 7.8 0.0 232 152 p4 R 05:06 1:55 ./crashme +2000 721 100 56 2 subprocess davem 6041 7.0 0.1 348 268 p4 R 05:07 1:36 ./crashme +2000 741 100 76 2 subprocess davem 6062 6.3 0.1 348 268 p4 R 05:08 1:25 ./crashme +2000 750 100 85 2 subprocess davem 6082 6.0 0.0 176 96 p4 R 05:09 1:17 ./crashme +2000 759 100 94 2 subprocess davem 6116 5.4 0.1 256 176 p4 R 05:10 1:05 ./crashme +2000 775 100 110 2 subprocess davem 6130 5.1 0.0 160 84 p4 R 05:11 1:00 ./crashme +2000.80 782 100 117 2 subprocess davem 6137 5.1 0.1 252 176 p4 R 05:11 0:59 ./crashme +2000 784 100 119 2 subprocess davem 6140 5.2 0.1 284 204 p4 R 05:11 1:00 ./crashme +2000 785 100 120 2 subprocess davem 6161 5.0 0.0 196 116 p4 R 05:12 0:56 ./crashme +2000 792 100 127 2 subprocess davem 6276 4.5 0.0 220 144 p4 R 05:15 0:41 ./crashme +2000 833 100 168 2 subprocess davem 6288 4.5 0.0 156 80 p4 R 05:15 0:40 ./crashme +2000.80 839 100 174 2 subprocess davem 6298 4.3 0.0 156 80 p4 R 05:16 0:37 ./crashme +2000.80 844 100 179 2 subprocess davem 6343 4.2 0.0 160 84 p4 R 05:17 0:32 ./crashme +2000.80 860 100 195 2 subprocess davem 6370 4.1 0.0 152 76 p4 R 05:18 0:29 ./crashme +2000.80 871 100 206 2 subprocess davem 6372 4.1 0.1 312 236 p4 R 05:18 0:30 ./crashme +2000 871 100 206 2 subprocess davem 6389 4.0 0.0 160 84 p4 R 05:19 0:27 ./crashme +2000.80 880 100 215 2 subprocess davem 6406 4.0 0.1 256 176 p4 R 05:19 0:26 ./crashme +2000 887 100 222 2 subprocess davem 6481 3.8 0.1 2248 260 p4 R 05:22 0:18 ./crashme +2000 920 100 255 2 subprocess davem 6487 3.8 0.0 228 152 p4 R 05:22 0:17 ./crashme +2000 923 100 258 2 subprocess davem 6519 3.7 0.0 208 128 p4 R 05:24 0:14 ./crashme +2000 939 100 274 2 subprocess davem 6520 3.7 0.0 156 76 p4 R 05:24 0:14 ./crashme +2000.80 940 100 275 2 subprocess davem 6525 3.7 0.1 348 268 p4 R 05:24 0:13 ./crashme +2000 942 100 277 2 subprocess davem 6633 4.1 0.0 232 152 p4 R 05:28 0:05 ./crashme +2000 992 100 327 2 subprocess davem 6646 4.3 0.0 156 76 p4 R 05:29 0:03 ./crashme +2000.80 999 100 334 2 subprocess davem 6661 5.0 0.1 348 268 p4 R 05:29 0:02 ./crashme +2000 1006 100 341 2 subprocess davem 6679 18.8 0.1 332 256 p4 R 05:30 0:01 ./crashme +2000 1015 100 350 2 subprocess davem 6684 0.0 0.1 604 200 p4 S 05:30 0:00 grep crashme ? uname -a Linux huahaga 1.3.83 #5 Sat Apr 6 21:46:09 EST 1996 sparc ? cat /proc/meminfo Mem: 179937280 175955968 3981312 11505664 66658304 93188096 Swap: 67088384 16384 67072000 MemTotal: 175720 kB MemFree: 3888 kB MemShared: 11236 kB Buffers: 65096 kB Cached: 91004 kB SwapTotal: 65516 kB SwapFree: 65500 kB cpuinfo ? cat /proc/cpuinfo cpu : ROSS HyperSparc RT625 fpu : ROSS HyperSparc combined IU/FPU promlib : Version 3 Revision 2 type : sun4m Elf Support : yes BogoMips : 115.91 MMU type : ROSS HyperSparc invall : 197856 invmm : 17135 invrnge : 338517 invpg : 12818739 contexts : 4096 big_chunks : 0 little_chunks : 0 ? uptime 5:34am up 1:54, 3 users, load average: 30.60, 27.64, 19.27 ? I didn't think so... but I get a few of these every once in a while: <4>WARNING: FPU exception from kernel mode. at pc=f00116cc <4> \|/ ____ \|/ <4> "@'/ ,. \`@" <4> /_| \__/ |_\ <4> \__U_/ <4>crashme(6723): Too many Penguin-FPU traps from kernel mode <4>PSR: 1e8010c2 PC: f00116d0 NPC: f00116d4 Y: 9e63031f <4>%g0: f0bc8000 %g1: ffffffef %g2: 00000020 %g3: 000221c4 <4>%g4: f0bc8000 %g5: 00000000 %g6: 00000000 %g7: 00001100 <4>%o0: f0c0f460 %o1: f0c0f560 %o2: f0c0f568 %o3: f0c0f564 <4>%o4: f00fec00 %o5: 0000000f %sp: f0daff08 %ret_pc: f0012a90 <4>Instruction DUMP: It doesn't stop the machine, it's just annoying. But I'll fix that. Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon Apr 15 17:02:18 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA19263; Mon, 15 Apr 1996 17:02:18 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id RAA29502; Mon, 15 Apr 1996 17:02:13 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id RAA29493; Mon, 15 Apr 1996 17:02:12 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA19258 for ; Mon, 15 Apr 1996 17:02:11 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id RAA29487; Mon, 15 Apr 1996 17:02:10 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id RAA07450; Mon, 15 Apr 1996 17:02:09 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id UAA01922; Mon, 15 Apr 1996 20:02:04 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id UAA19157; Mon, 15 Apr 1996 20:02:04 -0400 Date: Mon, 15 Apr 1996 20:02:04 -0400 Message-Id: <199604160002.UAA19157@huahaga.rutgers.edu> From: "David S. Miller" To: lmlinux@neteng.engr.sgi.com CC: torvalds@cs.helsinki.fi Subject: HyperSparc UP numbers Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk The MMap lat. looks bogus but the rest is ok. Larry, if you make another set of results publicly available on your web page for the next release like you do now I'd like this to be in there if thats ok. L M B E N C H 1 . 0 S U M M A R Y ------------------------------------ Processor, Processes - times in microseconds -------------------------------------------- Host OS Mhz Null Null Simple /bin/sh Mmap 2-proc 8-proc Syscall Process Process Process lat ctxsw ctxsw --------- ------------- ---- ------- ------- ------- ------- ---- ------ ------ huahaga Linux 1.3.83 118 3 12.8K 36.4K 52K 1060 25 43 *Local* Communication latencies in microseconds ----------------------------------------------- Host OS Pipe UDP RPC/ TCP RPC/ UDP TCP --------- ------------- ------- ------- ------- ------- ------- huahaga Linux 1.3.83 75 188 628 404 916 *Local* Communication bandwidths in megabytes/second ---------------------------------------------------- Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem reread reread (libc) (hand) read write --------- ------------- ---- ---- ------ ------ ------ ------ ---- ----- huahaga Linux 1.3.83 54 9.7 36.4 30.8 21 22 49 37 Memory latencies in nanoseconds (WARNING - may not be correct, check graphs) -------------------------------------------- Host OS Mhz L1 $ L2 $ Main mem TLB Guesses --------- ------------- --- ---- ---- -------- --- ------- huahaga Linux 1.3.83 118 11 11 511 0 No L1 cache? From owner-linux@cthulhu.engr.sgi.com Wed Apr 17 15:05:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA02166; Wed, 17 Apr 1996 15:05:17 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id PAA23029; Wed, 17 Apr 1996 15:05:13 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id PAA23020; Wed, 17 Apr 1996 15:05:11 -0700 Received: (from lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA02162 for lmlinux@neteng; Wed, 17 Apr 1996 15:05:11 -0700 Date: Wed, 17 Apr 1996 15:05:11 -0700 From: lm@neteng.engr.sgi.com (Larry McVoy) Message-Id: <199604172205.PAA02162@neteng.engr.sgi.com> To: lmlinux@neteng.engr.sgi.com Subject: (fwd) USELINUX: Linux Applications Development and Deployment Conference Newsgroups: comp.os.research Reply-To: lm@gate1-neteng.engr.sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Path: fido.asd.sgi.com!sgigate.sgi.com!news.msfc.nasa.gov!newsfeed.internetmci.com!newsxfer2.itd.umich.edu!agate!darkstar.UCSC.EDU!osr From: toni@usenix.org (Toni Veglia) Newsgroups: comp.os.research Subject: USELINUX: Linux Applications Development and Deployment Conference Date: 17 Apr 1996 04:07:09 GMT Organization: USENIX Association Lines: 236 Approved: comp-os-research@ftp.cse.ucsc.edu Message-ID: <4l1qpd$ivd@darkstar.UCSC.EDU> NNTP-Posting-Host: ftp.cse.ucsc.edu Originator: osr@cse.ucsc.edu USELINUX: Linux Applications Development and Deployment Conference Co-located with the USENIX Annual Technical Conference Co-sponsored by Linux International and the USENIX Association January 6-10, 1997 - Anaheim Marriott Hotel, Anaheim, California Tutorials: January 6-7, 1997 Technical Sessions: January 8-9, 1997 Business Sessions: January 10, 1997 Keynote: Wednesday, January 8, 1997 Birds-of-a-Feather Sessions: January 7-9, 1997 Vendor Exhibits: January 8-9, 1997 Reception: January 8, 1997 Conference Chair Michael K. Johnson, Linux Journal TECHNICAL TRACK COMMITTEE: Michael K. Johnson, Chair, Linux Journal Mark Bolzern, WorkGroup Solutions Alan Cox, 3Com Remote Access Products Jon `maddog' Hall, Esq., Digital Equipment Corporation Lorrie LeJeune, O'Reilly and Associates Dr. Tom Miller, North Carolina State University Erik Troan, Red Hat Software Dr. Greg Wettstein, Roger Maris Cancer Center BUSINESS TRACK COMMITTEE: Jon `maddog' Hall, Esq., Chair, Digital Equipment Corporation Jonathan Eunice, President, Founder, Research Director of lluminata, Inc. Michael K. Johnson, Editor, Linux Journal Lorrie LeJeune, Product Manager of Internet and Linux, O'Reilly and Assoc. Bryan Sparks, President , Caldera, Inc. Paul Winbauer, Director of Technical Programs, Avnet Computing Bob Young, President, Red Hat Software, Inc. Suggestions for Topics: June 1, 1996 Submissions Due : Date: July 1, 1996 Materials Due Date: November 13, 1996 OVERVIEW: The Linux Applications Development and Deployment Conference (USELINUX) is aimed at three primary audiences: application developers porting or developing Linux applications, systems administrators charged with maintaining Linux systems, and business people who wish to bring Linux applications to market. Two technical tracks on January 8th and 9th will include separate components for developers and systems administrators. A business track devoted to explaining the dynamics of the Linux marketplace and how to partake of it will take place on January 10. In addition to the three days of presentations and discussions, there will be two days of tutorials, Birds-of-a-Feather sessions, and Vendor Exhibits. TUTORIALS--Monday and Tuesday, January 6-7, 1997 We are actively seeking proposals for half or full day tutorials on practical, technical aspects of using Linux. If you would like to present a tutorial, please contact the USENIX tutorial co-ordinator, Daniel V. Klein. Phone: 412.421.0285 Fax: 412.421.2332 Email: TECHNICAL TRACK TOPICS - Wednesday and Thursday, January 8-9, 1997 The technical track will have three components: - an application developers component focusing on topics helpful in porting and developing Linux applications. These include things like APIs, including both Linux's levels of compliance with industry standard APIs and Linux-specific APIs, and capabilities that give extra functionality and/or convenience. - a system administrators component to help sysadmins apply their skills to Linux administration, and also demonstrate some of the unique and useful features that can make their lives easier. - a component for enthusiasts involved in developing the Linux operating system and environment. BUSINESS TRACK TOPICS - Friday, January 10, 1997 The business track program will focus on obstacles and challenges in integrating Linux into a business. The target audience are software application developers, hardware vendors, service providers, large in-house application developers, and others who would like to know how to make their business more successful using Linux. This track will concentrate on business issues such as: --The Linux Market: Who, What, Where, When and Why? --Application Portfolios: What is available, what can be done? --Marketing to the Linux Marketplace --Channels: Retail, Resellers, Distributors, Integrators, OEMs, Service --Licenses and Licensing: I don't want to give away my application!!! In addition to the meetings, there will be a compendium of information on CD-ROM for conference attendees. This will include copies of the slides, pointers to resources, white papers, lists of current resellers, user groups, etc. HOW TO SUBMIT A PROPOSAL Suggestions for additional topics and areas where the topics can be expanded are welcome by June 1, 1996. The program committee will then prioritize the topics and create the final list of topics by July 1st. The program committee will solicit volunteers to work on the program, and will balance volunteers with program needs by that time. An expanded electronic version of this announcement with greater detail, as well as the Call for Papers for the USENIX Annual Technical Conference, is available at the USENIX Web site: http://www.usenix.org. Proposals for invited talks and panels should be received by July 1, 1996. We welcome submissions of a full paper or an extended abstract. Panel proposals should contain a list of names of potential panelists. Please send submissions to the conference program chairs via one of the following methods. All submissions will be acknowledged. Please send comments, suggestions, and volunteering of time for a particular area of expertise (including a small bio of your experience) to the conference program chair via one of the following methods. Email is greatly preferred. PREFERRED METHOD If you are submitting an idea for the technical track, send email to: . For the business program, send your ideas via email to with the subject line: MADDOG, ANOTHER GREAT IDEA FOR THE *FABULOUS* USELINUX BUSINESS TRACK ALTERNATE METHOD: Via postal address or fax to: Michael Johnson or Jon "maddog" Hall, Esq. USENIX Association 2560 Ninth Street, Suite 215 Berkeley CA 94710 Fax: 510-548-5738 VENDOR EXHIBITS Vendors will demonstrate their products in a relaxed environment where attendees can discuss product features and services. Vendors are invited to participate in the Vendor Exhibits. This is an excellent opportunity to receive feedback from our technically astute audience. If your company would like to display its products or services, please contact Cynthia Deno: Phone: 408-335-9445 Email: BIRDS-OF-A-FEATHER SESSIONS (BOFs) BOFs are very informal, attendee-organized sessions held in the evenings by attendees interested in a particular topic. They may be scheduled on-site or in advance by contacting the USENIX Conference Office. Send email to or phone 714-588-8649. ABOUT THE USENIX ASSOCIATION USENIX is the UNIX and Advanced Computing Systems Technical and Professional Association. Since 1975 the USENIX Association has brought together the community of engineers, system administrators, scientists, and technicians working on the cutting edge of the computing world. The USENIX Conferences have become the essential meeting grounds for the presentation and discussion of the most advanced information on new developments in all aspects of advanced computing systems. The USENIX Association and its members are dedicated to: --problem-solving with a practical bias, --fostering innovation and research that works, --communicating rapidly the results of both research and innovation, --providing a neutral forum for the exercise of critical thought and the airing of technical issues. SAGE, a Special Technical Group within the USENIX Association, is dedicated to the recognition and advancement of system administration as a profession. To join SAGE, you must be a member of USENIX. ABOUT LINUX INTERNATIONAL Linux International (LI) is a new organization dedicated to promoting the development and use of the Linux operating system worldwide. LI promotes Linux in various ways: * LI has established a "Development Grant Fund" which is used to help Linux developers afford hardware and software that they need to continue development. The money in the fund is primarily given by Linux users eager to contribute to Linux development. * LI facilitates Linux activities at conferences and trade shows. * LI's Vendor Assistance Program offers vendors various kinds of assistance in porting their products to Linux. * LI's Linux Promotion Project disseminates promotional materials, including press releases, all over the world. What's the point of a world-class operating system if people don't know it exists? See the LI home page at http://www.li.org/linux-int/" or send email to for more information. REGISTRATION INFORMATION The complete program will be available in September 1996. To receive a registration package, please contact: USENIX Conference Office 22672 Lambert Street, Suite 215 Lake Forest, CA 92630 Phone: 714.588.5738 Fax: 714.588.9706 URL: http://www.usenix.org Email: conference@usenix.org Or you can send email to our mailserver at . Your message should contain the line: "send linux conferences" and the program will be sent to you. -- --- Larry McVoy lm@sgi.com http://reality.sgi.com/lm (415) 933-1804 Copyright 1996, all rights reserved. Microsoft Network is prohibited from redistributing this work in any form, in whole or in part without license. License to distribute this work is available to Microsoft at $500. Transmission without permission constitutes an agreement to these terms. From owner-linux@cthulhu.engr.sgi.com Thu Apr 18 00:29:12 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA06240; Thu, 18 Apr 1996 00:29:12 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id AAA15418; Thu, 18 Apr 1996 00:29:07 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id AAA15413; Thu, 18 Apr 1996 00:29:05 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA06237 for ; Thu, 18 Apr 1996 00:29:04 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id AAA15405; Thu, 18 Apr 1996 00:29:03 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id AAA13189; Thu, 18 Apr 1996 00:29:02 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id DAA19030; Thu, 18 Apr 1996 03:28:57 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id DAA00404; Thu, 18 Apr 1996 03:28:57 -0400 Date: Thu, 18 Apr 1996 03:28:57 -0400 Message-Id: <199604180728.DAA00404@huahaga.rutgers.edu> From: "David S. Miller" To: sparclinux@vger.rutgers.edu CC: lmlinux@neteng.engr.sgi.com, alan@cymru.net Subject: SMP wheee... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk SparcLinuxMP just built itself on two processors without a hitch over nfsroot! YIEEE!!! Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Thu Apr 18 03:03:45 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA06462; Thu, 18 Apr 1996 03:03:45 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id DAA26426; Thu, 18 Apr 1996 03:03:40 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id DAA26410; Thu, 18 Apr 1996 03:03:37 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA06459 for ; Thu, 18 Apr 1996 03:03:36 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id DAA26404; Thu, 18 Apr 1996 03:03:35 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id DAA22557; Thu, 18 Apr 1996 03:03:32 -0700 Received: from caip.rutgers.edu (caip.rutgers.edu [128.6.19.83]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id GAA24871; Thu, 18 Apr 1996 06:03:26 -0400 Received: (davem@localhost) by caip.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id GAA20599; Thu, 18 Apr 1996 06:03:26 -0400 Date: Thu, 18 Apr 1996 06:03:26 -0400 Message-Id: <199604181003.GAA20599@caip.rutgers.edu> From: "David S. Miller" To: sparclinux@vger.rutgers.edu CC: linux-smp@vger.rutgers.edu, linux-kernel@vger.rutgers.edu, lmlinux@neteng.engr.sgi.com, user@host.rutgers.edu Subject: SMP, yeah it works dude... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk make -j vmlinux in 3 minutes 45 seconds, second time was a little faster because it was all in the cache... and... of course ? ps -auxwww USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND davem 41 0.0 0.2 588 436 1 S 08:52 0:01 -bash davem 1689 0.0 0.0 112 100 1 S 09:08 0:00 sh /usr/local/X11R5/bin/startx davem 1690 0.0 0.2 1140 452 1 S 09:08 0:00 xinit /usr/home/davem/.xinitrc -- davem 1691 1.7 0.8 3760 1476 1 S 09:08 0:56 X :0 davem 1692 0.1 0.4 1292 736 1 S 09:08 0:03 fvwm davem 1714 0.0 0.2 1092 520 1 S 09:08 0:00 /usr/local/X11R5/lib/X11/fvwm/FvwmPager 7 4 /usr/home/davem/.fvwmrc 0 8 0 3 davem 2061 0.0 0.2 596 464 p3 S 09:11 0:01 -bash davem 4336 0.0 0.2 600 468 p0 S 09:50 0:00 -bash davem 4361 0.1 0.0 148 68 p0 S 09:53 0:00 ./crashme +2000 666 100 1:10:30 2 davem 4383 74.4 0.1 348 268 p0 R 09:53 6:12 ./crashme +2000 686 100 21 2 subprocess davem 4430 59.8 0.0 228 148 p0 R 09:56 3:15 ./crashme +2000 721 100 56 2 subprocess davem 4468 43.6 0.0 252 172 p0 R 09:58 1:39 ./crashme +2000 741 100 76 2 subprocess davem 4478 38.1 0.1 344 264 p0 R 09:59 1:09 ./crashme +2000 750 100 85 2 subprocess davem 4488 34.8 0.0 176 96 p0 R 09:59 0:47 ./crashme +2000 759 100 94 2 subprocess davem 4507 31.6 0.0 252 172 p0 R 10:01 0:17 ./crashme +2000 775 100 110 2 subprocess davem 4515 0.2 0.2 696 392 p3 S 10:01 0:00 telnet caip davem 4520 2.0 0.2 588 436 p1 S 10:02 0:00 -bash davem 4526 29.3 0.1 252 176 p0 R 10:02 0:02 ./crashme +2000 784 100 119 2 subprocess davem 4537 0.0 0.0 232 156 p1 R 10:02 0:00 ps -auxwww root 1 0.3 0.0 188 144 ? S 08:51 0:14 init [2] root 2 0.0 0.0 0 0 ? SW 08:51 0:00 (kflushd) root 3 0.0 0.0 0 0 ? SW< 08:51 0:00 (kswapd) root 4 0.0 0.0 0 0 ? SW 08:52 0:00 (nfsiod) root 5 0.0 0.0 0 0 ? SW 08:52 0:00 (nfsiod) root 6 0.0 0.0 0 0 ? SW 08:52 0:00 (nfsiod) root 7 0.0 0.0 0 0 ? SW 08:52 0:00 (nfsiod) root 11 0.2 0.0 116 44 ? S 08:52 0:09 update (bdfluHOME=/ root 27 0.0 0.1 628 268 ? S 08:52 0:00 /usr/etc/inetd root 29 0.0 0.1 636 248 ? S 08:52 0:00 /usr/etc/portmap root 42 0.0 0.0 152 100 2 S 08:52 0:00 /sbin/getty 9600 tty2 root 43 0.0 0.0 152 100 3 S 08:52 0:00 /sbin/getty 9600 tty3 root 44 0.0 0.0 152 100 4 S 08:52 0:00 /sbin/getty 9600 tty4 root 45 0.0 0.0 152 100 5 S 08:52 0:00 /sbin/getty 9600 tty5 root 46 0.0 0.0 152 100 6 S 08:52 0:00 /sbin/getty 9600 tty6 root 2060 0.0 0.6 1996 1220 1 S 09:11 0:01 xterm root 4335 0.0 0.6 1980 1180 1 S 09:50 0:00 xterm root 4519 2.4 0.6 1980 1180 1 S 10:02 0:00 xterm ? uname -a Linux huahaga 1.3.90 #10 Thu Apr 18 04:44:32 EDT 1996 sparc ? cat /proc/cpuinfo cpu : ROSS HyperSparc RT625 fpu : ROSS HyperSparc combined IU/FPU promlib : Version 3 Revision 2 type : sun4m Elf Support : yes Cpu0Bogo : 116.73 Cpu1Bogo : 116.73 Cpu2Bogo : 0.00 Cpu3Bogo : 0.00 MMU type : ROSS HyperSparc invall : 102 invmm : 10509 invrnge : 155469 invpg : 2305064 contexts : 4096 big_chunks : 0 little_chunks : 0 CPU0 CPU1 CPU2 CPU3 State: online akp offline offline Lock: 00000002 00000002 00000000 00000000 klock: ff block: 0 alock: 0 ? uptime 10:04am up 1:12, 2 users, load average: 7.39, 5.20, 3.63 ? It keeps going and going and going.... Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Thu Apr 18 03:23:32 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA06499; Thu, 18 Apr 1996 03:23:32 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id DAA27721; Thu, 18 Apr 1996 03:23:26 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id DAA27716; Thu, 18 Apr 1996 03:23:25 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA06496 for ; Thu, 18 Apr 1996 03:23:24 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id DAA27711; Thu, 18 Apr 1996 03:23:23 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id DAA23687; Thu, 18 Apr 1996 03:23:21 -0700 Received: from caip.rutgers.edu (caip.rutgers.edu [128.6.19.83]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id GAA25790; Thu, 18 Apr 1996 06:23:18 -0400 Received: (davem@localhost) by caip.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id GAA21132; Thu, 18 Apr 1996 06:23:17 -0400 Date: Thu, 18 Apr 1996 06:23:17 -0400 Message-Id: <199604181023.GAA21132@caip.rutgers.edu> From: "David S. Miller" To: sparclinux@vger.rutgers.edu CC: linux-smp@vger.rutgers.edu, lmlinux@neteng.engr.sgi.com Subject: this is sooo much fun... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND davem 41 0.0 0.2 588 436 1 S 08:52 0:01 -bash davem 1689 0.0 0.0 112 100 1 S 09:08 0:00 sh /usr/local/X11R5/bin/startx davem 1690 0.0 0.2 1140 452 1 S 09:08 0:00 xinit /usr/home/davem/.xinitrc -- davem 1691 1.6 0.8 3796 1516 1 S 09:08 1:19 X :0 davem 1692 0.0 0.4 1296 744 1 S 09:08 0:04 fvwm davem 1714 0.0 0.2 1092 520 1 S 09:08 0:00 /usr/local/X11R5/lib/X11/fvwm/FvwmPager 7 4 /usr/home/davem/.fvwmrc 0 8 0 3 davem 2061 0.0 0.2 596 464 p3 S 09:11 0:01 -bash davem 4336 0.0 0.2 600 468 p0 S 09:50 0:00 -bash davem 4361 0.0 0.0 148 68 p0 S 09:53 0:01 ./crashme +2000 666 100 1:10:30 2 davem 4383 30.6 0.1 348 268 p0 R 09:53 10:36 ./crashme +2000 686 100 21 2 subprocess davem 4430 24.0 0.0 228 148 p0 R 09:56 7:38 ./crashme +2000 721 100 56 2 subprocess davem 4468 20.0 0.0 252 172 p0 R 09:58 6:01 ./crashme +2000 741 100 76 2 subprocess davem 4478 18.9 0.1 344 264 p0 R 09:59 5:32 ./crashme +2000 750 100 85 2 subprocess davem 4488 18.1 0.0 176 96 p0 R 09:59 5:09 ./crashme +2000 759 100 94 2 subprocess davem 4507 17.1 0.0 252 172 p0 R 10:01 4:38 ./crashme +2000 775 100 110 2 subprocess davem 4515 0.1 0.2 696 392 p3 S 10:01 0:02 telnet caip davem 4520 0.0 0.2 588 464 p1 S 10:02 0:00 -bash davem 4526 16.6 0.1 252 176 p0 R 10:02 4:23 ./crashme +2000 784 100 119 2 subprocess davem 4589 14.6 0.0 216 140 p0 R 10:06 3:15 ./crashme +2000 833 100 168 2 subprocess davem 4628 12.9 0.1 312 236 p0 R 10:09 2:28 ./crashme +2000 871 100 206 2 subprocess davem 4661 12.3 0.1 256 176 p0 R 10:10 2:11 ./crashme +2000 887 100 222 2 subprocess davem 4736 11.1 0.1 2260 264 p0 R 10:13 1:40 ./crashme +2000 920 100 255 2 subprocess davem 4756 11.0 0.0 228 152 p0 R 10:13 1:37 ./crashme +2000 923 100 258 2 subprocess davem 4815 0.0 0.2 592 444 p2 S 10:14 0:00 -bash davem 4830 2.1 0.6 1872 1188 p2 R 10:14 0:17 xgas davem 4845 10.6 0.0 208 128 p0 R 10:15 1:25 ./crashme +2000 939 100 274 2 subprocess davem 4851 10.5 0.1 348 268 p0 R 10:15 1:22 ./crashme +2000 942 100 277 2 subprocess davem 4852 1.4 0.2 1064 456 p2 S 10:15 0:11 xswarm davem 4896 0.1 0.2 588 448 p4 S 10:16 0:00 -bash davem 4990 9.5 0.0 228 148 p0 R 10:19 0:51 ./crashme +2000 992 100 327 2 subprocess davem 5024 9.2 0.1 348 268 p0 R 10:20 0:43 ./crashme +2000 1006 100 341 2 subprocess davem 5058 9.0 0.1 332 256 p0 R 10:21 0:37 ./crashme +2000 1015 100 350 2 subprocess davem 5143 8.4 0.0 204 124 p0 R 10:23 0:27 ./crashme +2000 1035 100 370 2 subprocess davem 5150 8.4 0.1 340 264 p0 R 10:23 0:26 ./crashme +2000 1037 100 372 2 subprocess davem 5207 0.1 0.2 584 444 p5 S 10:24 0:00 -bash davem 5226 7.2 0.1 320 272 p5 R 10:24 0:16 top davem 5297 7.1 0.0 192 116 p0 R 10:26 0:09 ./crashme +2000 1072 100 407 2 subprocess davem 5473 0.0 0.0 248 172 p4 R 10:28 0:00 ps -auxwww davem 5475 99.9 0.1 264 184 p0 R 10:28 0:00 ./crashme +2000 1100 100 435 2 subprocess root 1 0.2 0.0 188 144 ? S 08:51 0:14 init [2] root 2 0.0 0.0 0 0 ? SW 08:51 0:00 (kflushd) root 3 0.0 0.0 0 0 ? SW< 08:51 0:00 (kswapd) root 4 0.0 0.0 0 0 ? SW 08:52 0:00 (nfsiod) root 5 0.0 0.0 0 0 ? SW 08:52 0:00 (nfsiod) root 6 0.0 0.0 0 0 ? SW 08:52 0:00 (nfsiod) root 7 0.0 0.0 0 0 ? SW 08:52 0:00 (nfsiod) root 11 0.1 0.0 116 44 ? S 08:52 0:10 update (bdfluHOME=/ root 27 0.0 0.1 628 268 ? S 08:52 0:00 /usr/etc/inetd root 29 0.0 0.1 636 248 ? S 08:52 0:00 /usr/etc/portmap root 42 0.0 0.0 152 100 2 S 08:52 0:00 /sbin/getty 9600 tty2 root 43 0.0 0.0 152 100 3 S 08:52 0:00 /sbin/getty 9600 tty3 root 44 0.0 0.0 152 100 4 S 08:52 0:00 /sbin/getty 9600 tty4 root 45 0.0 0.0 152 100 5 S 08:52 0:00 /sbin/getty 9600 tty5 root 46 0.0 0.0 152 100 6 S 08:52 0:00 /sbin/getty 9600 tty6 root 2060 0.0 0.6 1996 1220 1 S 09:11 0:03 xterm root 4335 0.0 0.6 1980 1180 1 S 09:50 0:00 xterm root 4519 0.0 0.6 1980 1204 1 S 10:02 0:01 xterm root 4644 0.0 0.2 592 460 p1 S 10:10 0:00 /bin/bash root 4814 0.0 0.6 1960 1164 1 S 10:14 0:00 xterm root 4894 0.1 0.6 1960 1164 1 S 10:16 0:01 xterm root 5205 0.3 0.2 668 364 ? S 10:24 0:00 /usr/etc/in.telnetd root 5272 0.1 0.2 596 444 p4 T 10:25 0:00 /bin/bash root 5341 1.6 0.3 912 580 p1 S 10:27 0:01 make -j root 5349 0.0 0.1 556 304 p1 S 10:27 0:00 /bin/bash -c set -e; for i in kernel drivers mm fs net ipc lib arch/sparc/kernel arch/sparc/lib arch/sparc/mm arch/sparc/prom; do make -C $i; done root 5351 0.4 0.3 864 540 p1 S 10:27 0:00 make -C kernel root 5365 1.9 0.3 964 636 p1 S 10:27 0:01 make all_targets root 5376 0.3 0.1 660 268 p1 S 10:27 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o init/main.o init/main.c root 5381 0.2 0.1 660 268 p1 S 10:27 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -fno-omit-frame-pointer -c sched.c root 5382 5.1 2.0 4112 3664 p1 R 10:27 0:02 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase main.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5383 0.1 0.3 1132 552 p1 S 10:27 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o init/main.o root 5392 1.3 0.4 1288 856 p1 S 10:27 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5393 5.2 2.0 4128 3664 p1 R 10:27 0:02 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase sched.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -fno-omit-frame-pointer -o - root 5394 0.2 0.3 1132 560 p1 S 10:27 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o sched.o root 5397 0.2 0.1 660 268 p1 S 10:27 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o sys.o sys.c root 5407 0.2 0.1 660 268 p1 S 10:27 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o exit.o exit.c root 5417 1.4 0.5 1420 896 p1 S 10:27 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5422 5.2 1.9 3920 3436 p1 R 10:27 0:02 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase sys.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5423 0.3 0.3 1132 552 p1 S 10:27 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o sys.o root 5429 5.6 1.9 3824 3372 p1 R 10:27 0:02 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase exit.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5430 0.4 0.3 1132 556 p1 S 10:27 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o exit.o root 5451 0.3 0.1 660 268 p1 S 10:27 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o fork.o fork.c root 5457 0.3 0.1 660 268 p1 S 10:27 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o sysctl.o sysctl.c root 5459 5.6 2.0 4168 3668 p1 R 10:27 0:02 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase fork.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5461 0.1 0.3 1132 548 p1 S 10:27 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o fork.o root 5462 1.6 0.4 1356 876 p1 S 10:27 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5463 5.3 1.9 3912 3432 p1 R 10:27 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase sysctl.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5464 0.3 0.3 1132 548 p1 S 10:27 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o sysctl.o From owner-linux@cthulhu.engr.sgi.com Thu Apr 18 03:26:48 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA06508; Thu, 18 Apr 1996 03:26:48 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id DAA27931; Thu, 18 Apr 1996 03:26:43 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id DAA27926; Thu, 18 Apr 1996 03:26:42 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA06505 for ; Thu, 18 Apr 1996 03:26:41 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id DAA27923; Thu, 18 Apr 1996 03:26:41 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id DAA23921; Thu, 18 Apr 1996 03:26:39 -0700 Received: from caip.rutgers.edu (caip.rutgers.edu [128.6.19.83]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id GAA25952; Thu, 18 Apr 1996 06:26:38 -0400 Received: (davem@localhost) by caip.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id GAA21229; Thu, 18 Apr 1996 06:26:37 -0400 Date: Thu, 18 Apr 1996 06:26:37 -0400 Message-Id: <199604181026.GAA21229@caip.rutgers.edu> From: "David S. Miller" To: sparclinux@vger.rutgers.edu CC: lmlinux@neteng.engr.sgi.com Subject: you guys really have to try this sometime... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk YOWW! Am I MULTI-PENGUIN yet!!!??? USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND davem 41 0.0 0.2 588 436 1 S 08:52 0:01 -bash davem 1689 0.0 0.0 112 100 1 S 09:08 0:00 sh /usr/local/X11R5/bin/startx davem 1690 0.0 0.2 1140 452 1 S 09:08 0:00 xinit /usr/home/davem/.xinitrc -- davem 1691 1.6 0.8 3796 1516 1 S 09:08 1:23 X :0 davem 1692 0.0 0.4 1296 744 1 S 09:08 0:04 fvwm davem 1714 0.0 0.2 1092 520 1 S 09:08 0:00 /usr/local/X11R5/lib/X11/fvwm/FvwmPager 7 4 /usr/home/davem/.fvwmrc 0 8 0 3 davem 2061 0.0 0.2 596 464 p3 S 09:11 0:01 -bash davem 4336 0.0 0.2 600 468 p0 S 09:50 0:00 -bash davem 4361 0.0 0.0 148 68 p0 S 09:53 0:02 ./crashme +2000 666 100 1:10:30 2 davem 4383 29.0 0.1 348 268 p0 R 09:53 10:49 ./crashme +2000 686 100 21 2 subprocess davem 4430 22.7 0.0 228 148 p0 R 09:56 7:51 ./crashme +2000 721 100 56 2 subprocess davem 4468 19.0 0.0 252 172 p0 R 09:58 6:14 ./crashme +2000 741 100 76 2 subprocess davem 4478 18.0 0.1 344 264 p0 R 09:59 5:45 ./crashme +2000 750 100 85 2 subprocess davem 4488 17.2 0.0 176 96 p0 R 09:59 5:22 ./crashme +2000 759 100 94 2 subprocess davem 4507 16.2 0.0 252 172 p0 R 10:01 4:52 ./crashme +2000 775 100 110 2 subprocess davem 4515 0.1 0.2 696 392 p3 S 10:01 0:02 telnet caip davem 4520 0.0 0.2 588 464 p1 S 10:02 0:00 -bash davem 4526 15.7 0.1 252 176 p0 R 10:02 4:36 ./crashme +2000 784 100 119 2 subprocess davem 4589 13.8 0.0 216 140 p0 R 10:06 3:28 ./crashme +2000 833 100 168 2 subprocess davem 4628 12.3 0.1 312 236 p0 R 10:09 2:41 ./crashme +2000 871 100 206 2 subprocess davem 4661 11.7 0.1 256 176 p0 R 10:10 2:24 ./crashme +2000 887 100 222 2 subprocess davem 4736 10.6 0.1 2260 264 p0 R 10:13 1:52 ./crashme +2000 920 100 255 2 subprocess davem 4756 10.5 0.0 228 152 p0 R 10:13 1:50 ./crashme +2000 923 100 258 2 subprocess davem 4815 0.0 0.2 592 444 p2 S 10:14 0:00 -bash davem 4830 2.2 0.6 1872 1188 p2 S 10:14 0:22 xgas davem 4845 10.1 0.0 208 128 p0 R 10:15 1:38 ./crashme +2000 939 100 274 2 subprocess davem 4851 10.0 0.1 348 268 p0 R 10:15 1:35 ./crashme +2000 942 100 277 2 subprocess davem 4852 1.4 0.2 1064 456 p2 R 10:15 0:13 xswarm davem 4896 0.1 0.2 592 452 p4 S 10:16 0:00 -bash davem 4990 9.1 0.0 228 148 p0 R 10:19 1:04 ./crashme +2000 992 100 327 2 subprocess davem 5024 8.8 0.1 348 268 p0 R 10:20 0:55 ./crashme +2000 1006 100 341 2 subprocess davem 5058 8.6 0.1 332 256 p0 R 10:21 0:50 ./crashme +2000 1015 100 350 2 subprocess davem 5143 8.2 0.0 204 124 p0 R 10:23 0:40 ./crashme +2000 1035 100 370 2 subprocess davem 5150 8.2 0.1 340 264 p0 R 10:23 0:39 ./crashme +2000 1037 100 372 2 subprocess davem 5207 0.0 0.2 584 444 p5 S 10:24 0:00 -bash davem 5226 7.4 0.1 320 272 p5 R 10:24 0:28 top davem 5297 7.6 0.0 192 116 p0 R 10:26 0:22 ./crashme +2000 1072 100 407 2 subprocess davem 5612 0.0 0.1 252 176 p4 R 10:31 0:01 ps -auxwww root 1 0.2 0.0 188 144 ? S 08:51 0:14 init [2] root 2 0.0 0.0 0 0 ? SW 08:51 0:00 (kflushd) root 3 0.0 0.0 0 0 ? SW< 08:51 0:00 (kswapd) root 4 0.0 0.0 0 0 ? SW 08:52 0:00 (nfsiod) root 5 0.0 0.0 0 0 ? SW 08:52 0:00 (nfsiod) root 6 0.0 0.0 0 0 ? SW 08:52 0:00 (nfsiod) root 7 0.0 0.0 0 0 ? SW 08:52 0:00 (nfsiod) root 11 0.1 0.0 116 44 ? S 08:52 0:10 update (bdfluHOME=/ root 27 0.0 0.1 628 268 ? S 08:52 0:00 /usr/etc/inetd root 29 0.0 0.1 636 248 ? S 08:52 0:00 /usr/etc/portmap root 42 0.0 0.0 152 100 2 S 08:52 0:00 /sbin/getty 9600 tty2 root 43 0.0 0.0 152 100 3 S 08:52 0:00 /sbin/getty 9600 tty3 root 44 0.0 0.0 152 100 4 S 08:52 0:00 /sbin/getty 9600 tty4 root 45 0.0 0.0 152 100 5 S 08:52 0:00 /sbin/getty 9600 tty5 root 46 0.0 0.0 152 100 6 S 08:52 0:00 /sbin/getty 9600 tty6 root 2060 0.0 0.6 1996 1220 1 S 09:11 0:04 xterm root 4335 0.0 0.6 1980 1180 1 S 09:50 0:00 xterm root 4519 0.0 0.6 1980 1204 1 S 10:02 0:01 xterm root 4644 0.0 0.2 592 460 p1 S 10:10 0:00 /bin/bash root 4814 0.0 0.6 1960 1164 1 S 10:14 0:00 xterm root 4894 0.1 0.6 1960 1164 1 S 10:16 0:01 xterm root 5205 0.3 0.2 668 364 ? S 10:24 0:01 /usr/etc/in.telnetd root 5272 0.1 0.2 604 448 p4 T 10:25 0:00 /bin/bash root 5341 0.5 0.3 912 580 p1 S 10:27 0:01 make -j root 5349 0.0 0.1 556 304 p1 S 10:27 0:00 /bin/bash -c set -e; for i in kernel drivers mm fs net ipc lib arch/sparc/kernel arch/sparc/lib arch/sparc/mm arch/sparc/prom; do make -C $i; done root 5488 0.2 0.2 844 520 p1 S 10:29 0:00 make -C drivers root 5491 0.0 0.0 116 104 p1 S 10:29 0:00 /bin/sh -c set -e; for i in block char net sbus scsi; do make -C $i; done root 5529 1.0 0.3 900 572 p1 S 10:30 0:00 make -C char root 5532 4.5 0.3 996 668 p1 S 10:30 0:01 make all_targets root 5537 0.6 0.1 660 268 p1 S 10:30 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o n_tty.o n_tty.c root 5538 0.6 0.1 660 268 p1 S 10:30 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o sparc/keyboard.o sparc/keyboard.c root 5539 0.5 0.1 660 268 p1 S 10:30 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o tty_ioctl.o tty_ioctl.c root 5540 0.5 0.1 660 268 p1 S 10:30 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o pty.o pty.c root 5541 2.6 0.4 1184 796 p1 S 10:30 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5542 0.8 0.1 660 268 p1 S 10:30 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o vt.o vt.c root 5543 3.0 0.4 1260 836 p1 S 10:30 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5544 9.8 2.0 3988 3528 p1 R 10:30 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase keyboard.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5546 10.0 1.8 3780 3272 p1 R 10:30 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase n_tty.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5547 0.5 0.3 1132 548 p1 S 10:30 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o n_tty.o root 5548 3.2 0.4 1220 800 p1 S 10:30 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5549 10.0 1.9 3788 3340 p1 R 10:30 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase tty_ioctl.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5550 0.5 0.3 1132 552 p1 S 10:30 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o tty_ioctl.o root 5552 9.7 1.8 3752 3292 p1 R 10:30 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase pty.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5553 0.5 0.3 1132 548 p1 S 10:30 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o pty.o root 5555 0.6 0.3 1132 548 p1 S 10:30 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o sparc/keyboard.o root 5556 0.9 0.1 660 268 p1 S 10:30 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o vc_screen.o vc_screen.c root 5557 0.9 0.1 660 268 p1 S 10:30 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o random.o random.c root 5559 3.3 0.4 1236 840 p1 S 10:30 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5560 10.6 1.9 3928 3456 p1 R 10:30 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase vt.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5561 0.6 0.3 1132 548 p1 S 10:30 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o vt.o root 5563 12.8 1.7 3508 3016 p1 R 10:30 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase vc_screen.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5564 0.8 0.3 1132 548 p1 S 10:30 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o vc_screen.o root 5565 3.7 0.4 1184 780 p1 S 10:30 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5566 11.2 1.8 3800 3296 p1 R 10:30 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase random.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5567 0.8 0.3 1132 548 p1 S 10:30 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o random.o root 5569 1.2 0.1 660 268 p1 S 10:30 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o consolemap.o consolemap.c root 5570 1.1 0.1 660 268 p1 S 10:30 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o selection.o selection.c root 5571 0.8 0.1 660 268 p1 S 10:30 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o sparc/serial.o sparc/serial.c root 5572 1.4 0.1 660 268 p1 S 10:30 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o sunmouse.o sunmouse.c root 5574 1.0 0.1 660 268 p1 S 10:31 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o suncons.o suncons.c root 5579 15.0 1.8 3752 3232 p1 R 10:31 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase selection.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5580 0.9 0.3 1132 548 p1 S 10:31 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o selection.o root 5581 4.9 0.4 1280 824 p1 S 10:31 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5582 16.0 1.8 3676 3188 p1 R 10:31 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase consolemap.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5583 1.0 0.3 1132 560 p1 S 10:31 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o consolemap.o root 5584 5.3 0.4 1256 872 p1 S 10:31 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5585 16.0 1.9 3952 3484 p1 R 10:31 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase serial.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5586 0.9 0.3 1132 548 p1 S 10:31 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o sparc/serial.o root 5588 18.0 1.8 3740 3220 p1 R 10:31 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase sunmouse.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5589 0.9 0.3 1132 548 p1 S 10:31 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o sunmouse.o root 5590 2.0 0.1 660 268 p1 S 10:31 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o misc.o misc.c root 5591 1.5 0.1 660 268 p1 S 10:31 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o tty_io.o tty_io.c root 5592 1.7 0.1 660 268 p1 S 10:31 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o console.o console.c root 5593 1.1 0.1 660 268 p1 S 10:31 0:00 gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o mem.o mem.c root 5594 8.4 0.6 1728 1108 p1 S 10:31 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5596 21.3 1.9 4136 3340 p1 R 10:31 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase suncons.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5597 0.7 0.3 1132 548 p1 S 10:31 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o suncons.o root 5598 6.7 0.4 1308 848 p1 S 10:31 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5599 21.6 1.9 3928 3436 p1 R 10:31 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase mem.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5600 0.8 0.3 1132 548 p1 S 10:31 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o mem.o root 5602 8.7 0.5 1472 944 p1 S 10:31 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5603 26.1 1.9 3936 3444 p1 R 10:31 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase tty_io.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5604 1.0 0.3 1132 548 p1 S 10:31 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o tty_io.o root 5605 8.4 0.5 1600 1032 p1 S 10:31 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cpp -lang-c -I/usr/src/linux/include -undef -D__GNUC__=2 -D__GNUC_MINOR__=6 -Dsparc -Dsun -Dunix -D__GCC_NEW_VARARGS__ -D__sparc__ -D__sun__ -D__unix__ -D__GCC_NEW_VARARGS__ -D__sparc -D__sun -D__unix root 5606 27.1 2.0 4116 3620 p1 R 10:31 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase console.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 5607 1.2 0.3 1132 548 p1 S 10:31 0:00 /usr/local/gnu/sparc-sun-sunos4.1.4/bin/as - -o console.o From owner-linux@cthulhu.engr.sgi.com Fri Apr 19 11:47:59 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA27236; Fri, 19 Apr 1996 11:47:58 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id LAA20845; Fri, 19 Apr 1996 11:47:49 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id LAA20838; Fri, 19 Apr 1996 11:47:47 -0700 Received: by yon.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux id LAA23886; Fri, 19 Apr 1996 11:47:45 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199604191847.LAA23886@yon.engr.sgi.com> Subject: Linux/MIPS port resources To: linux@yon.engr.sgi.com Date: Fri, 19 Apr 1996 11:47:45 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1016 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I was thinking about what should we do to make David Miller come up to speed as fast as possible when he comes for the summer. After all, he may not be familiar with MIPS assembly, IRIX etc. So I set up a *preliminary* Web page with a list of resources for the Linux/MIPS port. Most of the pointers are from Bill Earl, thanks Bill. Please send me suggestions for improvement, what's missing, etc. This is just a quick first shot so you get the idea. The 6.2 freeware gcc is not yet configured to work with GNU-as (so it uses stabs and supports debugging) and our linker. I'll be working on this next week. We also need to make sure that all the equipment, the office, etc. is ready when David lands here. I assume someone is taking care of all this (?). And that someone with intimate knowledge of our low level stuff is really available to assist him on call. I'll leave it to Larry or Greg to announce the details on David Miller's accepting SGI's offer. p l e a s e :-) 6 weeks to go... -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Fri Apr 19 14:52:46 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA00061; Fri, 19 Apr 1996 14:52:45 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id OAA16120; Fri, 19 Apr 1996 14:52:30 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id OAA16115; Fri, 19 Apr 1996 14:52:29 -0700 Received: (from lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id OAA29927 for linux; Fri, 19 Apr 1996 14:52:28 -0700 Date: Fri, 19 Apr 1996 14:52:28 -0700 From: lm@neteng.engr.sgi.com (Larry McVoy) Message-Id: <199604192152.OAA29927@neteng.engr.sgi.com> To: linux@neteng.engr.sgi.com Subject: Good news Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hi- as some of you know, we've been negociating to get David Miller, the Sparc/Linux guy, to come out and work on a MIPS/Linux port. He has accepted, he starts on May 25th, and will be here until August 25th. We had to do a lot of work with the laywers, but we have agreement that all of the work that he does here will be a) owned by SGI (we paid for it), and b) distributed under the terms of the GPL. No exceptions. SGI owns the code so we can choose to use anything that turns out to be interesting inside IRIX without the constraints of the GPL (you may or may not be aware that the owner of the code can choose to distribute the code under multiple copyrights - so we can use stuff in IRIX without "polluting" the IRIX kernel with the GPL). I'd like to thank everyone that has been pulling for this, and especially Greg Chesson who did the hard work of getting the contract hammered out to the satisfaction of SGI & David. We are currently in the process of figuring out what code we can use to help with the port; there may be parts of the setup OS that are both appropriate and useful. Ariel and others are working to get a development machine set up in the engr domain. It will be linux.engr.sgi.com, and should be up and running on Monday or Tuesday. I'll keep you posted on new news as it happens. --lm --- Larry McVoy lm@sgi.com http://reality.sgi.com/lm (415) 933-1804 Copyright 1996, all rights reserved. Microsoft Network is prohibited from redistributing this work in any form, in whole or in part without license. License to distribute this work is available to Microsoft at $500. Transmission without permission constitutes an agreement to these terms. From owner-linux@cthulhu.engr.sgi.com Fri Apr 19 17:22:44 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA08180; Fri, 19 Apr 1996 17:22:44 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id RAA15342; Fri, 19 Apr 1996 17:22:38 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id RAA15337; Fri, 19 Apr 1996 17:22:37 -0700 Received: by yon.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux id RAA24414; Fri, 19 Apr 1996 17:22:35 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199604200022.RAA24414@yon.engr.sgi.com> Subject: MIPS port kickoff meeting To: linux@yon.engr.sgi.com Date: Fri, 19 Apr 1996 17:22:35 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1599 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hi LinuxMIPSies, This is becoming real. Please mark your calendars. We have Jamaica in B10U, which holds 12 people, from 4-5pm on Wednesday April 24th. I know it may conflict with someone's schedule but p l e a s e try your best to show up. THE MEETING HAS ONE MAIN GOAL: To ensure that when David Miller lands at SGI he wastes zero time on ramping up. We can do a lot until he comes. The idea Jim Barton, Larry and I had is: 1) Office + two Indys (connected via a serial line to support gdb remote protocol) already waiting, phone, email etc. 2) Development tools installed 3) The latest linux sources on the machine. After trying to compile them and see how smoothly this goes. 4) This may require the most work: A 99% stripped down IRIX or set-top box thing that is basically only the device drivers to boot and do: "hello console" "hello network" "hello disk" "hello keyboard" "hello console graphics" Given all this, David can boot Linux in a few days I guess :-) Agenda: 1) Quick round table: introduce everyone 2) Sort out some details: Are we going for a 64-bit kernel? What MIPS instruction set should we support [e.g. 3K is important for the embedded market] What dev tools should we use? elf/coff stabs/dwarf gcc/cc etc. etc. 4) Suggest more ways to accelerate David Miller's ramp up 5) List action items 6) Get volunteers for help on the above Lastly, since David's Acceptance is final. I think it is time to put David himself on this mailing list too, he certainly has some ideas on how to help us help him. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Sat Apr 20 01:17:11 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id BAA06189; Sat, 20 Apr 1996 01:17:10 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id BAA21621; Sat, 20 Apr 1996 01:17:05 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id BAA21616; Sat, 20 Apr 1996 01:17:03 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id BAA06171 for ; Sat, 20 Apr 1996 01:17:01 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id BAA21608; Sat, 20 Apr 1996 01:17:00 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id BAA20612; Sat, 20 Apr 1996 01:16:59 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id EAA18291; Sat, 20 Apr 1996 04:16:32 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id EAA04303; Sat, 20 Apr 1996 04:16:31 -0400 Date: Sat, 20 Apr 1996 04:16:31 -0400 Message-Id: <199604200816.EAA04303@huahaga.rutgers.edu> From: "David S. Miller" To: lm@gate1-neteng.engr.sgi.com CC: torvalds@cs.helsinki.fi, humor@fidelio.rutgers.edu, user@host.rutgers.edu, lmlinux@neteng.engr.sgi.com, adrian@remus.rutgers.edu Subject: SparcLinux humorous comments.. Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Check it out: /* There was a great cache from TI * with comfort as much as vi, * 4 pages to flush, * 4 pages, no rush, * since anything else makes him die. */ ;-) Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon Apr 22 18:03:13 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA12880; Mon, 22 Apr 1996 18:03:13 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id SAA26604; Mon, 22 Apr 1996 18:03:07 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id SAA26582; Mon, 22 Apr 1996 18:03:05 -0700 Received: by yon.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux id SAA28441; Mon, 22 Apr 1996 18:03:04 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199604230103.SAA28441@yon.engr.sgi.com> Subject: David Miller is on the list To: linux@yon.engr.sgi.com Date: Mon, 22 Apr 1996 18:03:04 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 304 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Just so you all know. David Miller is now on the linux@engr.sgi.com mailing list on majordomo@engr. Welcome David! If you want to see some history, I believe Larry has been archiving these emails somewhere. I hope this works fine with external addresses. If not, please let me know. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Mon Apr 22 18:05:02 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA12889; Mon, 22 Apr 1996 18:05:02 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id SAA26849; Mon, 22 Apr 1996 18:04:57 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id SAA26835; Mon, 22 Apr 1996 18:04:54 -0700 Received: from cthulhu.engr.sgi.com by yon.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id SAA28466; Mon, 22 Apr 1996 18:04:48 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id SAA26821; Mon, 22 Apr 1996 18:04:48 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id SAA08539; Mon, 22 Apr 1996 18:04:46 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id VAA01711; Mon, 22 Apr 1996 21:04:45 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id VAA01747; Mon, 22 Apr 1996 21:04:45 -0400 Date: Mon, 22 Apr 1996 21:04:45 -0400 Message-Id: <199604230104.VAA01747@huahaga.rutgers.edu> From: "David S. Miller" To: ariel@cthulhu.engr.sgi.com CC: linux@yon.engr.sgi.com In-reply-to: <199604230103.SAA28441@yon.engr.sgi.com> (ariel@yon.engr.sgi.com) Subject: Re: David Miller is on the list Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: ariel@yon.engr.sgi.com (Ariel Faigon) Date: Mon, 22 Apr 1996 18:03:04 -0700 (PDT) Welcome David! If you want to see some history, I believe Larry has been archiving these emails somewhere. Howdy... I hope this works fine with external addresses. If not, please let me know. Read ya loud and clear, as you can see ;) Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon Apr 22 18:40:15 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA13038; Mon, 22 Apr 1996 18:40:14 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id SAA02431; Mon, 22 Apr 1996 18:40:08 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id SAA02421; Mon, 22 Apr 1996 18:40:06 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id SAA12769; Mon, 22 Apr 1996 18:40:04 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id VAA02115; Mon, 22 Apr 1996 21:40:02 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id VAA03615; Mon, 22 Apr 1996 21:40:01 -0400 Date: Mon, 22 Apr 1996 21:40:01 -0400 Message-Id: <199604230140.VAA03615@huahaga.rutgers.edu> From: "David S. Miller" To: ariel@cthulhu.engr.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <199604230116.SAA28514@yon.engr.sgi.com> (ariel@yon.engr.sgi.com) Subject: Re: David Miller is on the list Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: ariel@yon.engr.sgi.com (Ariel Faigon) Date: Mon, 22 Apr 1996 18:16:30 -0700 (PDT) Great, now you can tell the list what do you need :-) Oh boy. Seriously, we've been thinking about how we could make you most productive and not waste your time when you arrive here. Here's a recent posting of mine, so you get the idea just in case Simon or Bob or Larry didn't tell you about all this yet... Feel free to bombard us with requests/questions. There are about 20 people on the linux list at SGI (you can query majordomo@engr.sgi.com for the details) Already did that an hour ago ;) (note: I looked back over this mail after composing it and I want to warn people who are not familiar with me yet that I am very sarcastic and am full of ridicule even when discussing important topics. Please don't take it that I lack tact or am not being serious, because that simply isn't the case.) Here is what I need: The following utilities I need for development. 1) CVS/RCS, latest on prep.ai.mit.edu is fine 2) Emacs-19.31 (rms should release within 2 weeks) 3) All GNU smidgen-type utilies as the default binaries (this include fileutils/sh-utils/sharutils/diffutils/ findutils/...) Actually, Let me just stop short and say, if there is a source tarball for it on prep.ai.mit.edu:/pub/gnu I would like the latest installed on the machine I develop on. 4) xfishtank (don't laugh) 5) fvwm 6) teco (Must support full teco command set as described in original DEC manuals! TECO is _the_ renaissance editor!) The following would be nice, but if it will give people bladder problems to do these then don't go out of your way: 1) MIPS 4[40]00 manual is some online format (not postscript, something I can cut and paste out of an emacs buffer etc. so maybe info or pure ascii text would be fine, I could care less about the formatting, I just want the words there) 2) Docs on the ethernet/scsi interfaces and I/O bus architecture for the first machine I will be getting this to work on, again text/info format would be nice. Of course I will probably just stuff in the ready drivers you might be getting to me into Linux but I want to write my own from scratch in the near future after that. 3) I know as much as a bum on the street about SGI machines and the various lines, a nice "roadmap to sgi workstations and servers, plus the hardware gook thats inside" type thing would be very useful to me. I will feel more comfortable if: 1) I became very familiar with who the heavy low level MIPS assembly level hackers are who I will be dealing with while I am there. Please tell me who they are, introduce, make us say hello to each other, you get the idea. 2) I know the policy on loud music in the office I'll be in ;-) I've thought it over and to me the best plan for things this summer to me is: a) R4400 32-bit "proof of concept, yeah we can pull it off" port happens first, side effect is that I become intimate enough with the chip that I can do things more efficiently. b) From here we look into the 64-bit stuff and whether that is is even desirable on 64-bit. (this would be my first 64-bit port outside of my initial UltraSparc hacks) c) Also think about the work needed to turn that code into r3000 friendly code. Should not be too much as I've done the "write it on recent architecture design then backport it to older design which had some limitations" already and this didn't end up being so bad. Expect more as I think it up... this should keep you guys busy for now. (Any dead-head tape traders at SGI engineering? Just wondering, may want to start talking to them now ;-) Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon Apr 22 19:15:40 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA13094; Mon, 22 Apr 1996 19:15:40 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA06483; Mon, 22 Apr 1996 19:15:34 -0700 Received: from soyuz.wellington.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id TAA06467; Mon, 22 Apr 1996 19:15:28 -0700 Received: from windy.wellington.sgi.com by soyuz.wellington.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/940406.SGI) for id OAA14551; Tue, 23 Apr 1996 14:15:25 +1200 Received: (alambie@localhost) by windy.wellington.sgi.com (950413.SGI.8.6.12/8.6.9) id OAA21562 for linux@cthulhu.engr.sgi.com; Tue, 23 Apr 1996 14:15:24 +1200 From: "Alistair Lambie" Message-Id: <9604231415.ZM21560@windy.wellington.sgi.com> Date: Tue, 23 Apr 1996 14:15:23 +0000 In-Reply-To: ariel@yon.engr.sgi.com (Ariel Faigon) "MIPS port kickoff meeting" (Apr 19, 5:22pm) References: <199604200022.RAA24414@yon.engr.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: linux@cthulhu.engr.sgi.com Subject: Re: MIPS port kickoff meeting Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Apr 19, 5:22pm, Ariel Faigon wrote: > Subject: MIPS port kickoff meeting > Hi LinuxMIPSies, > > This is becoming real. Please mark your calendars. > > We have Jamaica in B10U, which holds 12 people, from 4-5pm > on Wednesday April 24th. > > I know it may conflict with someone's schedule but p l e a s e > try your best to show up. > Umm...could be a problem. It's a holiday here in New Zealand, otherwise :-) > > Agenda: > 1) Quick round table: introduce everyone > 2) Sort out some details: > Are we going for a 64-bit kernel? > What MIPS instruction set should we support > [e.g. 3K is important for the embedded market] > What dev tools should we use? > elf/coff stabs/dwarf gcc/cc etc. etc. My 2c worth: 1. We should definitely do 32bit, probably 64bit as well. There is a big base of R3k machines out there that are going to start getting left behind soon. 2. We need to go for lowest common denominator (MIPS I) and then add conditionals (in the low level bits) later. The c code can of course be compiled as the user wants it. 3. We need to support machines that don't have a graphics head (servers). This requires serial drivers. 4. We should really tie this project in with what is happening at http://lena.fnet.fr/. Their goal has been to get Linux on ARCS systems running little endian, but there is a need for a MIPS port for MIPS (the company) R3k machines which needs to be big endian. 5. Should we use the 'milo' bootloader? 6. > 4) Suggest more ways to accelerate David Miller's ramp up > 5) List action items > 6) Get volunteers for help on the above > Probably not much I can do from here. Maybe some Beta testing a bit further down the track (test for bit inversion in the southern hemisphere :-) ). I still have an interest in getting Linux on to the old MIPS boxes, so maybe with a few quick hacks after David has worked his magic I can get this to happen. I suspect that this would also help CSD out as I know they still get support calls from people who have these machines and are falling all over the place with the development environment (svr3, bsd43, svr4). Often they are little more than people playing and having a Linux offering may be the best way to get them out of our hair. Also, RISC/os is getting a bit long in the tooth now and there are still some nasty little bugs in it, often comms related which more often than not is what the person wanted it for! One thing that would be nice is for someone to minute the meeting to the list so that those of us who can't attend can see what's happening. I guess it is also a good way of documenting the progress as things move along! Cheers, Alistair -- Alistair Lambie alambie@wellington.sgi.com Silicon Graphics New Zealand SGI Voicemail: 56791 Level 5, Walsh Wrightson Tower, Ph: +64-4-802 1455 94-96 Dixon St, Wellington, NZ Fax: +64-4-802 1459 From owner-linux@cthulhu.engr.sgi.com Mon Apr 22 19:16:38 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA13099; Mon, 22 Apr 1996 19:16:38 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA06594; Mon, 22 Apr 1996 19:16:33 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id TAA06589; Mon, 22 Apr 1996 19:16:32 -0700 Received: by yon.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux id TAA28613; Mon, 22 Apr 1996 19:16:30 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199604230216.TAA28613@yon.engr.sgi.com> Subject: Re: David Miller is on the list To: linux@yon.engr.sgi.com Date: Mon, 22 Apr 1996 19:16:30 -0700 (PDT) In-Reply-To: <199604230140.VAA03615@huahaga.rutgers.edu> from "David S. Miller" at Apr 22, 96 09:40:01 pm Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 4846 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > >(note: I looked back over this mail after composing it and I want to > warn people who are not familiar with me yet that I am very > sarcastic and am full of ridicule even when discussing > important topics. Please don't take it that I lack tact > or am not being serious, because that simply isn't the case.) > Feel free to express yourself, my english (colloquial and otherwsie) is bad anyway, and I guess the others don't care :-) >Here is what I need: > > The following utilities I need for development. > 1) CVS/RCS, latest on prep.ai.mit.edu is fine > RCS comes default with IRIX today. But I know it is not the latest. OK, and I'll add cvs. > 2) Emacs-19.31 (rms should release within 2 weeks) > 3) All GNU smidgen-type utilies as the default binaries > (this include fileutils/sh-utils/sharutils/diffutils/ > findutils/...) > Actually, Let me just stop short and say, if there is a > source tarball for it on prep.ai.mit.edu:/pub/gnu I would > like the latest installed on the machine I develop on. > Many of these are in our freeware project. Ready to install with the click of a mouse. (Yes, one of the cool things about SGI is a joe-user software installer infinitely better than RPM/glint.) (yon) 84 /var/tmp> which find /usr/freeware/bin/find (yon) 85 /var/tmp> which tar /usr/freeware/bin/tar (yon) 86 /var/tmp> which grep /usr/freeware/bin/grep (yon) 87 /var/tmp> which chmod /usr/freeware/bin/chmod I'll add the missing ones. That's easy. BTW, we called it '/usr/freeware' rather than '/usr/gnu' because many packages are from other sources and because some of our customers asked us to stay away from their /usr/local. > 4) xfishtank (don't laugh) > Bingo. Larry runs this too. You weird people. Is this a conspiracy? :-) > 5) fvwm > > 6) teco (Must support full teco command set as described > in original DEC manuals! TECO is _the_ renaissance editor!) > I'll try to build these too. > The following would be nice, but if it will give people > bladder problems to do these then don't go out of your > way: > 1) MIPS 4[40]00 manual is some online format (not postscript, > something I can cut and paste out of an emacs buffer etc. > so maybe info or pure ascii text would be fine, I could > care less about the formatting, I just want the words > there) For MIPS ABI stuff: try the following web site, http://www.mipsabi.org/ Especially: http://www.mipsabi.org/Tech/Technical.html Tell us what's missing there. As for the MIPS programmer's Assembly manual. There is an excellent one internally on the Web... I'll try to get you a copy soon. > 2) Docs on the ethernet/scsi interfaces and I/O bus > architecture for the first machine I will be getting > this to work on, again text/info format would be nice. > Of course I will probably just stuff in the ready > drivers you might be getting to me into Linux but I want > to write my own from scratch in the near future after > that. > 3) I know as much as a bum on the street about SGI machines > and the various lines, a nice "roadmap to sgi workstations > and servers, plus the hardware gook thats inside" type > thing would be very useful to me. > I'll leave these to some other folks on the list. > I will feel more comfortable if: > 1) I became very familiar with who the heavy low level MIPS > assembly level hackers are who I will be dealing with while > I am there. Please tell me who they are, introduce, make > us say hello to each other, you get the idea. > I believe the most knowledgable low-level gurus on the list are Bill Earl and Jim Barton, I'm sure there are more, I just don't know everyone on the list personally ... > 2) I know the policy on loud music in the office I'll be in > ;-) > I'm trying to get you an office right by mine :-) >I've thought it over and to me the best plan for things this summer to >me is: > a) R4400 32-bit "proof of concept, yeah we can pull it off" > port happens first, side effect is that I become intimate > enough with the chip that I can do things more efficiently. > b) From here we look into the 64-bit stuff and whether that is > is even desirable on 64-bit. (this would be my first > 64-bit port outside of my initial UltraSparc hacks) > c) Also think about the work needed to turn that code into > r3000 friendly code. Should not be too much as I've done > the "write it on recent architecture design then backport > it to older design which had some limitations" already and > this didn't end up being so bad. > Cool. >Expect more as I think it up... this should keep you guys busy for >now. > >(Any dead-head tape traders at SGI engineering? Just wondering, may > want to start talking to them now ;-) > You'll find lots of them here ;-) -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Mon Apr 22 19:28:14 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA13122; Mon, 22 Apr 1996 19:28:14 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA07444; Mon, 22 Apr 1996 19:28:07 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id TAA07437; Mon, 22 Apr 1996 19:28:06 -0700 Received: from cthulhu.engr.sgi.com by yon.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id TAA28647; Mon, 22 Apr 1996 19:28:00 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id TAA07428; Mon, 22 Apr 1996 19:27:59 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id TAA17146; Mon, 22 Apr 1996 19:27:58 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id WAA02819; Mon, 22 Apr 1996 22:27:57 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id WAA05238; Mon, 22 Apr 1996 22:27:56 -0400 Date: Mon, 22 Apr 1996 22:27:56 -0400 Message-Id: <199604230227.WAA05238@huahaga.rutgers.edu> From: "David S. Miller" To: ariel@cthulhu.engr.sgi.com CC: linux@yon.engr.sgi.com In-reply-to: <199604230216.TAA28613@yon.engr.sgi.com> (ariel@yon.engr.sgi.com) Subject: Re: David Miller is on the list Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: ariel@yon.engr.sgi.com (Ariel Faigon) Date: Mon, 22 Apr 1996 19:16:30 -0700 (PDT) > >(note: I looked back over this mail after composing it and I want to > warn people who are not familiar with me yet that I am very > sarcastic and am full of ridicule even when discussing > important topics. Please don't take it that I lack tact > or am not being serious, because that simply isn't the case.) > Feel free to express yourself, my english (colloquial and otherwsie) is bad anyway, and I guess the others don't care :-) Cool, I feel much more comfortable now ;) > 4) xfishtank (don't laugh) > Bingo. Larry runs this too. You weird people. Is this a conspiracy? :-) Nope, not a conspiracy. Grab a copy of: caip.rutgers.edu:/pub/davem/penguin.gif Then run 'xfishtank -p penguin.gif' after hacking endlessly on down and dirty kernel code for 20 hours straight with no sleep and direct intraveinus coffee keeping you going, and tell me that isn't the damn most funniest thing you've ever seen in your life. (note said description is the state I am in right now, whee... oh yeah, and the penguin picture was found in Linus's home directory on linux.cs.helsinki.fi one late night I was hacking on there :) For MIPS ABI stuff: try the following web site, http://www.mipsabi.org/ Especially: http://www.mipsabi.org/Tech/Technical.html Tell us what's missing there. As for the MIPS programmer's Assembly manual. There is an excellent one internally on the Web... I'll try to get you a copy soon. Noted, I'll check some of that out. Thanks. >(Any dead-head tape traders at SGI engineering? Just wondering, may > want to start talking to them now ;-) > You'll find lots of them here ;-) Oh, yummy, heaven on earth. Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon Apr 22 19:38:02 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA13178; Mon, 22 Apr 1996 19:38:02 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA07855; Mon, 22 Apr 1996 19:36:28 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id TAA07848; Mon, 22 Apr 1996 19:36:26 -0700 Received: from neteng.engr.sgi.com by yon.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id TAA28667; Mon, 22 Apr 1996 19:36:15 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id TAA13171; Mon, 22 Apr 1996 19:35:59 -0700 Message-Id: <199604230235.TAA13171@neteng.engr.sgi.com> To: "David S. Miller" From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: David Miller is on the list Date: Mon, 22 Apr 1996 19:35:59 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : > 4) xfishtank (don't laugh) : > : Bingo. Larry runs this too. You weird people. Is this a conspiracy? :-) : : Nope, not a conspiracy. Grab a copy of: : : caip.rutgers.edu:/pub/davem/penguin.gif : : Then run 'xfishtank -p penguin.gif' after hacking endlessly on down Nah, try this: xearth & xfishtank -d Fish in spaaaaaaaaaaaaaaace! From owner-linux@cthulhu.engr.sgi.com Mon Apr 22 19:50:49 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA13205; Mon, 22 Apr 1996 19:50:49 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA09154; Mon, 22 Apr 1996 19:50:21 -0700 Received: from sgihub.corp.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id TAA09139; Mon, 22 Apr 1996 19:50:20 -0700 Received: from yon.engr.sgi.com by sgihub.corp.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/911001.SGI) for id TAA23191; Mon, 22 Apr 1996 19:45:04 -0700 Received: from cthulhu.engr.sgi.com by yon.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id TAA28688; Mon, 22 Apr 1996 19:44:55 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id TAA08459; Mon, 22 Apr 1996 19:44:37 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id TAA17951; Mon, 22 Apr 1996 19:44:35 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id WAA03061; Mon, 22 Apr 1996 22:44:15 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id WAA06042; Mon, 22 Apr 1996 22:44:15 -0400 Date: Mon, 22 Apr 1996 22:44:15 -0400 Message-Id: <199604230244.WAA06042@huahaga.rutgers.edu> From: "David S. Miller" To: lm@gate1-neteng.engr.sgi.com CC: ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com In-reply-to: <199604230235.TAA13171@neteng.engr.sgi.com> (lm@gate1-neteng.engr.sgi.com) Subject: Re: David Miller is on the list Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Actually, here's an important issue. I get to name my machines right? Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon Apr 22 19:55:55 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA13297; Mon, 22 Apr 1996 19:55:55 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA09497; Mon, 22 Apr 1996 19:55:51 -0700 Received: from circle-slide.indianapolis.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id TAA09490; Mon, 22 Apr 1996 19:55:49 -0700 Received: by circle-slide.indianapolis.sgi.com (950413.SGI.8.6.12/930416.SGI) id VAA02353; Mon, 22 Apr 1996 21:55:34 -0500 From: jm@circle-slide.indianapolis.sgi.com (jon madison) Message-Id: <199604230255.VAA02353@circle-slide.indianapolis.sgi.com> Subject: Re: David Miller is on the list To: ariel@cthulhu.engr.sgi.com Date: Mon, 22 Apr 1996 21:55:33 -0500 (EST) Cc: linux@cthulhu.engr.sgi.com In-Reply-To: <199604230216.TAA28613@yon.engr.sgi.com> from "Ariel Faigon" at Apr 22, 96 07:16:30 pm X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 349 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ariel Faigon quoted, a little while back, #> 5) fvwm ariel, if you can't i'll swing it (i run bowman here...(bowman's a 'better' fvwm (looks like NeXTStep...the GoodStuff is like NeXT's dock) j. -- jon madison, silicon graphics, inc. us: mailto:jm@sgi.com me: From owner-linux@cthulhu.engr.sgi.com Mon Apr 22 20:01:41 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA13325; Mon, 22 Apr 1996 20:01:41 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id UAA09903; Mon, 22 Apr 1996 20:01:37 -0700 Received: from circle-slide.indianapolis.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id UAA09897; Mon, 22 Apr 1996 20:01:35 -0700 Received: by circle-slide.indianapolis.sgi.com (950413.SGI.8.6.12/930416.SGI) for linux@engr id WAA02391; Mon, 22 Apr 1996 22:01:26 -0500 Date: Mon, 22 Apr 1996 22:01:26 -0500 From: jm@circle-slide.indianapolis.sgi.com (jon madison) Message-Id: <199604230301.WAA02391@circle-slide.indianapolis.sgi.com> To: linux@cthulhu.engr.sgi.com Subject: which fvwm? Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk david, which version of fvwm...1.xx or the 2's? thx, j. jon madison, silicon graphics, inc. us: mailto:jm@sgi.com me: From owner-linux@cthulhu.engr.sgi.com Mon Apr 22 20:03:45 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA13331; Mon, 22 Apr 1996 20:03:44 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA08482; Mon, 22 Apr 1996 19:44:45 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id TAA08474; Mon, 22 Apr 1996 19:44:44 -0700 Received: from deliverator.sgi.com by yon.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id TAA28685; Mon, 22 Apr 1996 19:44:40 -0700 Received: from caipfs.rutgers.edu by deliverator.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) id TAA17718; Mon, 22 Apr 1996 19:44:33 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id WAA03052; Mon, 22 Apr 1996 22:43:12 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id WAA06037; Mon, 22 Apr 1996 22:43:12 -0400 Date: Mon, 22 Apr 1996 22:43:12 -0400 Message-Id: <199604230243.WAA06037@huahaga.rutgers.edu> From: "David S. Miller" To: lm@gate1-neteng.engr.sgi.com CC: ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com In-reply-to: <199604230235.TAA13171@neteng.engr.sgi.com> (lm@gate1-neteng.engr.sgi.com) Subject: Re: David Miller is on the list Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) Date: Mon, 22 Apr 1996 19:35:59 -0700 Fish in spaaaaaaaaaaaaaaace! YESSSS!!! way cool larry Oh man, in my .xinitrc this goes... Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon Apr 22 20:26:32 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA13387; Mon, 22 Apr 1996 20:26:32 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id UAA12319; Mon, 22 Apr 1996 20:26:23 -0700 Received: from deliverator.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id UAA12296; Mon, 22 Apr 1996 20:26:21 -0700 Received: from caipfs.rutgers.edu by deliverator.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/951211.SGI.AUTO) id UAA20071; Mon, 22 Apr 1996 20:26:06 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id XAA03486; Mon, 22 Apr 1996 23:24:50 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id XAA06446; Mon, 22 Apr 1996 23:24:50 -0400 Date: Mon, 22 Apr 1996 23:24:50 -0400 Message-Id: <199604230324.XAA06446@huahaga.rutgers.edu> From: "David S. Miller" To: jm@circle-slide.indianapolis.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <199604230301.WAA02391@circle-slide.indianapolis.sgi.com> (jm@circle-slide.indianapolis.sgi.com) Subject: Re: which fvwm? Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Mon, 22 Apr 1996 22:01:26 -0500 From: jm@circle-slide.indianapolis.sgi.com (jon madison) david, which version of fvwm...1.xx or the 2's? 1.24l Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 09:35:33 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA09379; Tue, 23 Apr 1996 09:35:32 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id JAA07514; Tue, 23 Apr 1996 09:35:28 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id JAA07499; Tue, 23 Apr 1996 09:35:26 -0700 Received: from piecomputer.corp.sgi.com by yon.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id JAA29479; Tue, 23 Apr 1996 09:35:22 -0700 Received: by piecomputer.corp.sgi.com (950413.SGI.8.6.12/930416.SGI) id JAA11799; Tue, 23 Apr 1996 09:35:17 -0700 From: "Bob Mende Pie" Message-Id: <9604230935.ZM11797@piecomputer.corp.sgi.com> Date: Tue, 23 Apr 1996 09:35:15 -0700 In-Reply-To: lm@gate1-neteng.engr.sgi.com (Larry McVoy) "Re: David Miller is on the list" (Apr 22, 7:35pm) References: <199604230235.TAA13171@neteng.engr.sgi.com> X-URL: http://reality.sgi.com/employees/mende/ X-Mailer: Z-Mail-SGI (3.2S.2 10apr95 MediaMail) To: lm@gate1-neteng.engr.sgi.com (Larry McVoy), "David S. Miller" Subject: Re: David Miller is on the list Cc: ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Apr 22, 7:35pm, Larry McVoy wrote: > Subject: Re: David Miller is on the list > : > 4) xfishtank (don't laugh) > : > > : Bingo. Larry runs this too. You weird people. Is this a conspiracy? :-) > : > : Nope, not a conspiracy. Grab a copy of: > : > : caip.rutgers.edu:/pub/davem/penguin.gif > : > : Then run 'xfishtank -p penguin.gif' after hacking endlessly on down > > Nah, try this: > > xearth & > xfishtank -d > > Fish in spaaaaaaaaaaaaaaace! And all of the fish are bubbling the same thing ... "cpu ... more cpu ..." :-) -- /Bob... mende@sgi.com http://reality.sgi.com/mende/ From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 09:35:43 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA09397; Tue, 23 Apr 1996 09:35:43 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id JAA07561; Tue, 23 Apr 1996 09:35:37 -0700 Received: from ares.esd.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id JAA07555; Tue, 23 Apr 1996 09:35:36 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id JAA15628; Tue, 23 Apr 1996 09:35:35 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id JAA13693; Tue, 23 Apr 1996 09:35:24 -0700 Date: Tue, 23 Apr 1996 09:35:24 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199604231635.JAA13693@fir.esd.sgi.com> To: "David S. Miller" Cc: ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com Subject: Re: David Miller is on the list In-Reply-To: <199604230140.VAA03615@huahaga.rutgers.edu> References: <199604230116.SAA28514@yon.engr.sgi.com> <199604230140.VAA03615@huahaga.rutgers.edu> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > From: ariel@yon.engr.sgi.com (Ariel Faigon) > Date: Mon, 22 Apr 1996 18:16:30 -0700 (PDT) ... > 1) MIPS 4[40]00 manual is some online format (not postscript, > something I can cut and paste out of an emacs buffer etc. > so maybe info or pure ascii text would be fine, I could > care less about the formatting, I just want the words > there) The manuals are online, generally at www,mips.com. For example, http://www.mips.com/r4400/UMan/R4400_UM_cv.html is the latest R4400 manual. Our newer processors for low-end systems are the R4600 and now the R5000. Most Indy systems now ship with R5000 processors, and the Indy should be the target for the initial port, since it is in current production and widely available. The R4600 and R5000 are generally similar, except that the R4600 has 16 KB primary caches and is MIPS III, whereas the R5000 has 32 KB primary caches and is MIPS IV. Both are fairly similar to the R4000PC and R4400PC, in the sense that they do not have a secondary cache which enforces primary cache virtual index coherency. (Many Indy R4600 and R5000 systems do have secondary caches, but they do not supply virtual coherency exceptions.) The R4600 and R5000 are good targets for an initial port, because they have the fewest errata, and hence require the fewest kernel workarounds. The R4000 workarounds, in particular, are pretty messy. The R4600 and R5000 data sheets may be found via http://www.idt.com/risc/Welcome.html (under the 64-bit RISC microprocessors category). The manuals are not online on public servers, but I can track down copies. There is some more R4600 and R5000 information under http://www.qedinc.com/ There is a comparison of the R4400 and the R4600 at http://www.mips.com/r4400/Des_Com/Des_Com_cv.html The MIPS IV architecture document is http://www.mips.com/arch/MIPS4_cv.html This is of relatively minor importance for a basic port, but can be used to good effect to improve graphics and application performance. There are a few minor kernel support issues. Once the basic port is done, extending it to the other common processors, such as the R3000, R4000, R4400, and R10000, will be fairly simple. The R6000 (not common and obsolete for some years now) and the R8000 would be somewhat more work to support, since they differ more from the other processors in the kernel interface. > 2) Docs on the ethernet/scsi interfaces and I/O bus > architecture for the first machine I will be getting > this to work on, again text/info format would be nice. > Of course I will probably just stuff in the ready > drivers you might be getting to me into Linux but I want > to write my own from scratch in the near future after > that. I have the documents for the memory controller for Indy, and I think I can locate most of the others. They are only on paper, however, but I can get copies. > 3) I know as much as a bum on the street about SGI machines > and the various lines, a nice "roadmap to sgi workstations > and servers, plus the hardware gook thats inside" type > thing would be very useful to me. There are tables of the systems under http://ssales.corp.sgi.com/products/html/periodic_table.html Unfortunately, these are inside the firewall. > I will feel more comfortable if: > 1) I became very familiar with who the heavy low level MIPS > assembly level hackers are who I will be dealing with while > I am there. Please tell me who they are, introduce, make > us say hello to each other, you get the idea. I am probably the best initial contact for Indy issues, and I can introduce you to people familiar with the various drivers and so on. ... > I've thought it over and to me the best plan for things this summer to > me is: > a) R4400 32-bit "proof of concept, yeah we can pull it off" > port happens first, side effect is that I become intimate > enough with the chip that I can do things more efficiently. As I mentioned above, the R4600 and R5000 processors are a simpler initial target, and the Indy R4600 is the most common configuration. > b) From here we look into the 64-bit stuff and whether that is > is even desirable on 64-bit. (this would be my first > 64-bit port outside of my initial UltraSparc hacks) This is mainly interesting on the larger systems. 64-bit kernels do take more space and time (due to extra cache misses, if nothing else), and most applications don't need more than 32-bit addresses. The 32-bit kernel should, however, support using 64-bit arithmetic (MIPS III and IV) even in 32-bit programs, since there are substantial performance gains available for certain applications. The kernel itself can use 64-bit arithmetic to good effect as well. (This is how IRIX works.) > c) Also think about the work needed to turn that code into > r3000 friendly code. Should not be too much as I've done > the "write it on recent architecture design then backport > it to older design which had some limitations" already and > this didn't end up being so bad. The R3000 is not drastically different from the R4600. The main differences are somewhat different TLB and cache control routines, and, of course, the MIPS I instruction set. From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 09:39:44 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA09621; Tue, 23 Apr 1996 09:39:44 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id JAA08004; Tue, 23 Apr 1996 09:39:39 -0700 Received: from xtp.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id JAA07999; Tue, 23 Apr 1996 09:39:38 -0700 Received: by xtp.engr.sgi.com (940816.SGI.8.6.9/911001.SGI) id JAA27799; Tue, 23 Apr 1996 09:39:30 -0700 From: "Greg Chesson" Message-Id: <9604230939.ZM27797@xtp.engr.sgi.com> Date: Tue, 23 Apr 1996 09:39:29 -0700 In-Reply-To: "Alistair Lambie" "Re: MIPS port kickoff meeting" (Apr 23, 2:15pm) References: <199604200022.RAA24414@yon.engr.sgi.com> <9604231415.ZM21560@windy.wellington.sgi.com> X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: "Alistair Lambie" , linux@cthulhu.engr.sgi.com Subject: Re: MIPS port kickoff meeting Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk There are US Gov't customers for Linux on SGI boxes who require 64-bit OS. So, let's support tho 32-bit ARCS boxes without compromising opportunities to sell new boxes (with 64-bit Linux). g From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 09:56:58 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA09755; Tue, 23 Apr 1996 09:56:58 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id JAA12326; Tue, 23 Apr 1996 09:56:47 -0700 Received: from piecomputer.corp.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id JAA12320; Tue, 23 Apr 1996 09:56:46 -0700 Received: by piecomputer.corp.sgi.com (950413.SGI.8.6.12/930416.SGI) id JAA12075; Tue, 23 Apr 1996 09:56:43 -0700 From: "Bob Mende Pie" Message-Id: <9604230956.ZM12073@piecomputer.corp.sgi.com> Date: Tue, 23 Apr 1996 09:56:42 -0700 In-Reply-To: "David S. Miller" "Re: David Miller is on the list" (Apr 22, 9:40pm) References: <199604230140.VAA03615@huahaga.rutgers.edu> X-URL: http://reality.sgi.com/employees/mende/ X-Mailer: Z-Mail-SGI (3.2S.2 10apr95 MediaMail) To: "David S. Miller" , ariel@cthulhu.engr.sgi.com Subject: Re: David Miller is on the list Cc: linux@cthulhu.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Apr 22, 9:40pm, David S. Miller wrote: > 5) fvwm I've got 2.0.42 compiled and running ... But if dave wants to live in the dark ages of fvwm 1.x thats fine with me. > 6) teco (Must support full teco command set as described > in original DEC manuals! TECO is _the_ renaissance editor!) I've got it compiled, but beats the hell out of me if it works :-) Ill make you a deal, if I see you edit a file with it I bring you my honest to god DEC PDP-11 teco manual. -- /Bob... mende@sgi.com http://reality.sgi.com/mende/ From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 10:06:25 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA10051; Tue, 23 Apr 1996 10:06:24 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id KAA14640; Tue, 23 Apr 1996 10:06:19 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id KAA14628; Tue, 23 Apr 1996 10:06:17 -0700 Received: from patton.engr.sgi.com by yon.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id KAA29620; Tue, 23 Apr 1996 10:06:13 -0700 Received: by patton.engr.sgi.com (950413.SGI.8.6.12/911001.SGI) id KAA21770; Tue, 23 Apr 1996 10:06:11 -0700 From: "Jim Barton" Message-Id: <9604231006.ZM21768@patton.engr.sgi.com> Date: Tue, 23 Apr 1996 10:06:11 -0700 In-Reply-To: Ariel Faigon: message of Apr 22, 19:16 References: <199604230216.TAA28613@yon.engr.sgi.com> X-Mailer: Z-Mail-SGI (3.2S.2 10apr95 MediaMail) To: ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: David Miller is on the list Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk The purpose for basing the port on R3000 is *not* to support obsolete workstations and servers; our time and effort need to be directed to the future, not the past. If the guys in OZ want to port it, fine. Basing on an R3000 is important because of it's exploding use as an embedded processor; it's showing up in your laser printers, phone switches, robots, airplanes, satellite receivers, and so on. One thing Larry and I are interested in is seeing if Linux is really suitable as an embedded OS to support these (and more) applications. What you typically find is an r3k core surrounded by various application- specific peripherals, e.g, MPEG decoders, sound chips, DMA controllers, serial controllers. The OS is usually in ROM, and the device manufacturer adds special drivers to the mix. Real-time constraints come into play; in particular, it would be interesting to consider what additions to Linux make it work well for real-time applications. Posix 1003.4 is pretty heavy-weight, but perhaps we can have a light-weight implementation. In the workstation/server world, the R4000 is the processor to aim at. It is significantly different than the r3k in TLB layout, but little else in 32-bit mode, so the same code should basically work both places. I believe different binaries should be built for the r4k and r3k - certain pieces of MIPS II ISA can accelerate performance, and the compilers take advantage of that. Given that the workstation/server world is moving to 64 bit, I believe we need a 64-bit version of Linux as well. The design of the MIPS III ISA is actually pretty clean for keeping the same source between 32-bit and 64-bit kernels, as long as you are careful about your types. The r4k is also interesting because it is at the heart of the Nintendo Ultra-64 game, and the R4300i processor it uses is starting to show up in various Japanese computer products. The volumes of this device are projected in the 10s of millions of units, so it is significant. Linux in your Ultra-64 box? Hmmmm. Might actually be interesting ... So, we need to be able to build three versions from the same source. I think the R10K can be ignored for now, and it *only* runs in 64-bit kernel mode. 64-bit user mode can also be ignored for now - there are few applications for 64-bit programs except in the high-end scientific markets. The R8K is obsolete. -- jmb From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 10:23:08 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA14045; Tue, 23 Apr 1996 10:23:08 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id KAA17325; Tue, 23 Apr 1996 10:23:04 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id KAA17320; Tue, 23 Apr 1996 10:23:02 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id KAA13743; Tue, 23 Apr 1996 10:22:54 -0700 Message-Id: <199604231722.KAA13743@neteng.engr.sgi.com> To: "Greg Chesson" From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: "Alistair Lambie" , linux@cthulhu.engr.sgi.com Subject: Re: MIPS port kickoff meeting Date: Tue, 23 Apr 1996 10:22:54 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Greg said: : There are US Gov't customers for Linux on SGI boxes who require : 64-bit OS. So, let's support tho 32-bit ARCS boxes without compromising : opportunities to sell new boxes (with 64-bit Linux). We definitely want to do this. And I don't want to do anything to derail this because I want this badly. And what I'm about to say does not imply that we don't do 64bit - I want both. And it should be easy to do both. One reason for thinking small, however, is that we could finesse the whole Linux vs IRIX issue by raising awareness that Linux on MIPs could be a really nice solution for the embedded market. I personally would love to see a full page in IEEE times in which MIPS announces the availablity of embedded Linux for MIPs chips. This may be the quickest path to getting Linux embraced internally. I'm pretty sure that Cygnus would be interested in signing up for support for such a platform - that is a big part of their business. And I think that R3K is still the volume chip in the embedded market, so we want that to work. Thoughts? From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 10:25:40 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA14994; Tue, 23 Apr 1996 10:25:39 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id KAA17787; Tue, 23 Apr 1996 10:25:33 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id KAA17782; Tue, 23 Apr 1996 10:25:32 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id KAA14858; Tue, 23 Apr 1996 10:25:26 -0700 Message-Id: <199604231725.KAA14858@neteng.engr.sgi.com> To: lm@neteng.engr.sgi.com From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: "Greg Chesson" , "Alistair Lambie" , linux@cthulhu.engr.sgi.com Subject: Re: MIPS port kickoff meeting Date: Tue, 23 Apr 1996 10:25:26 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Arrg, ignore my message and read Jim's - he said it better. I gotta learn to read all my mail before firing off replies. From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 12:51:31 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id MAA28420; Tue, 23 Apr 1996 12:51:31 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id MAA11081; Tue, 23 Apr 1996 12:51:26 -0700 Received: from titian by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id MAA11070; Tue, 23 Apr 1996 12:51:25 -0700 Received: from localhost by titian via SMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id MAA01292; Tue, 23 Apr 1996 12:51:24 -0700 Message-Id: <199604231951.MAA01292@titian> To: "David S. Miller" cc: linux@cthulhu.engr.sgi.com Subject: Re: David Miller is on the list Date: Tue, 23 Apr 1996 12:51:24 -0700 From: Mike McDonald Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk A dumb question, what exactly is the purpose of porting Linux to SGI/Mips boxes? At one time, it was proposed as a way that all of the people how just got dropped from support to maintain there machine's usefull life. Now, people are talking about embedding linux in printers and Nintendo boxes! Or as an alternative to Irix on our current machines. Personally, I think the port should concentrate on R3K boxes with/without graphics. (It'd be nice if we could release the info so that X11R6 could be built on the old boxes.) The port should be a 32 bit port. (Does gcc even support 64 bit MIPS 27 ISA?) It also be nice if the R3K port would also work on the R4K machines that are fading away, ie. Indy's, Indigo2's. Mike McDonald mikemac@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 13:20:59 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA03811; Tue, 23 Apr 1996 13:20:59 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id NAA15112; Tue, 23 Apr 1996 13:20:53 -0700 Received: from ares.esd.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id NAA15105; Tue, 23 Apr 1996 13:20:52 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id NAA24196; Tue, 23 Apr 1996 13:20:51 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id NAA20245; Tue, 23 Apr 1996 13:20:50 -0700 Date: Tue, 23 Apr 1996 13:20:50 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199604232020.NAA20245@fir.esd.sgi.com> To: Mike McDonald CC: linux@cthulhu.engr.sgi.com Subject: Re: David Miller is on the list In-Reply-To: <199604231951.MAA01292@titian> References: <199604231951.MAA01292@titian> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Mike McDonald writes: > > > A dumb question, what exactly is the purpose of porting Linux to > SGI/Mips boxes? At one time, it was proposed as a way that all of the > people how just got dropped from support to maintain there machine's > usefull life. Now, people are talking about embedding linux in > printers and Nintendo boxes! Or as an alternative to Irix on our > current machines. Personally, I think the port should concentrate on > R3K boxes with/without graphics. (It'd be nice if we could release the > info so that X11R6 could be built on the old boxes.) The port should > be a 32 bit port. (Does gcc even support 64 bit MIPS 27 ISA?) It also > be nice if the R3K port would also work on the R4K machines that are > fading away, ie. Indy's, Indigo2's. Different people have different motivations, and you have heard some of them. My main interest is in two parts. First, on current-production low-end workstations, I would like to compare linux performance to IRIX performance. If linux is much better on most measures, in ways which matter to end users, then we would need to consider it as a choice for low-end systems. If it is better only in some dimensions, then we can use it as an existence proof that there are ways to improve IRIX in those dimensions. It is hard to compare software running on different hardware, but software running on identical hardware is directly comparable. Second, I believe that UNIX-based systems are gratuitously incompatible, compared to NT, and that this is an impediment to competing against NT in low-end servers and workstations. Since most efforts to standardize interfaces and administration for UNIX systems have been very slow and incomplete, due to conflicting interests of the vendors involved, I would like to try using linux as a vehicle for creating a de facto standard. Where appropriate, we should give away some enabling technology, such as Web-based administration scripts. We really compete on application performance. Trying compete in areas such as administrative commands, which are peripheral to the user's main interests, is, on balance, almost certainly counterproductive. This will be even more the case as we begin selling into larger installations (with a large number of units, not the odd one or two systems we often sell at present). linux for older boxes is a fine thing, and not unduly difficult to do, at least on the workstations, but there are a lot more R4000-and-better boxes out there now. As for embedded systems, there are actually pretty decent real time systems, some with POSIX compliance, which support MIPS processors. I doubt that the success of MIPS processors in embedded systems is much limited by software availability. From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 13:27:03 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA06606; Tue, 23 Apr 1996 13:27:03 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id NAA16317; Tue, 23 Apr 1996 13:26:58 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id NAA16308; Tue, 23 Apr 1996 13:26:56 -0700 Received: by yon.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux id NAA00059; Tue, 23 Apr 1996 13:26:54 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199604232026.NAA00059@yon.engr.sgi.com> Subject: What target (was David ...) To: linux@yon.engr.sgi.com Date: Tue, 23 Apr 1996 13:26:53 -0700 (PDT) In-Reply-To: <199604231951.MAA01292@titian> from "Mike McDonald" at Apr 23, 96 12:51:24 pm Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1313 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Mike asked (not a dumb Q, BTW): > > A dumb question, what exactly is the purpose of porting Linux to >SGI/Mips boxes? > Looks like there are many opinions. I don't care as long as we manage to do this port. Whatever we port it to (and the wider the port is) SGI is going to benefit tremendously. You may read my Linux pages (http://info.engr/~ariel/linux) to understand why my personal conviction (and others) is so strong. Some of the nice things about Linux are: 1) It can work from RAM (virtual disk), So it follows that it is easily ROMable and embeddable (much more so than IRIX) I have developed embedded apps for several years in my past and I can tell you that my life would have been infinitely easier had I been able to develop in a Linux env. Only the thought of having the same env on the host and the target is revolutionary by itself (and possible!) 2) It has a small footprint so naturally it is a good candidate for embedded market. 3) It has a common single source code for 32-bit and 64-bit machines (Alpha). So we shouldn't think of this as an "either/or" proposition. P.S. gcc doesn't have support for 64 bit MIPS 27 ISA, I guess, but nobody is stopping us from using our compilers (as well as gcc at our convenience). -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 13:54:38 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA09136; Tue, 23 Apr 1996 13:54:37 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id NAA22502; Tue, 23 Apr 1996 13:54:31 -0700 Received: from titian by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id NAA22492; Tue, 23 Apr 1996 13:54:30 -0700 Received: from localhost by titian via SMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id NAA01434; Tue, 23 Apr 1996 13:54:29 -0700 Message-Id: <199604232054.NAA01434@titian> To: ariel@cthulhu.engr.sgi.com cc: linux@cthulhu.engr.sgi.com Subject: Re: What target (was David ...) In-reply-to: Your message of "Tue, 23 Apr 1996 13:26:53 PDT." <199604232026.NAA00059@yon.engr.sgi.com> Date: Tue, 23 Apr 1996 13:54:29 -0700 From: Mike McDonald Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk >From: ariel@yon (Ariel Faigon) >Subject: What target (was David ...) >To: linux@yon >Date: Tue, 23 Apr 1996 13:26:53 -0700 (PDT) >P.S. >gcc doesn't have support for 64 bit MIPS 27 ISA, I guess, but >nobody is stopping us from using our compilers (as well as gcc >at our convenience). >-- >Peace, Ariel I strongly believe that using our compilers would be a "bad" thing for the initial port. Requiring someone to buy IDO inorder to compile a free OS seems like the "wrong" thing to me. Now, if we (SGI) decide to ship a Linux version, then yes, using our compilers is OK. Let's just make sure that the port is dependant on our compilers in any way at this point. (I doubt that's what you were suggesting. I just want to make it clear before we get started.) Mike McDonald mikemac@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 15:27:46 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA02388; Tue, 23 Apr 1996 15:27:46 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id PAA09787; Tue, 23 Apr 1996 15:27:40 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id PAA09782; Tue, 23 Apr 1996 15:27:39 -0700 Received: by yon.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) id PAA00323; Tue, 23 Apr 1996 15:27:36 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199604232227.PAA00323@yon.engr.sgi.com> Subject: Re: What target (was David ...) To: mikemac@titian.engr.sgi.com (Mike McDonald) Date: Tue, 23 Apr 1996 15:27:36 -0700 (PDT) Cc: ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com In-Reply-To: <199604232054.NAA01434@titian> from "Mike McDonald" at Apr 23, 96 01:54:29 pm Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1481 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk >Mike dijo: >>yo dijo: >> >>P.S. >>gcc doesn't have support for 64 bit MIPS 27 ISA, I guess, but >>nobody is stopping us from using our compilers (as well as gcc >>at our convenience). > > I strongly believe that using our compilers would be a "bad" thing >for the initial port. Requiring someone to buy IDO inorder to compile >a free OS seems like the "wrong" thing to me. Now, if we (SGI) decide >to ship a Linux version, then yes, using our compilers is OK. Let's >just make sure that the port is dependant on our compilers in any way >at this point. (I doubt that's what you were suggesting. I just want >to make it clear before we get started.) > > Bob and I are working separately on making our compilers (actually only the C one, not Ada :-) be bundled with Irix (and possibly licence enabled for a nominal fee, which can be done automatically without human intervention -- surprisingly this may increase revenues because the cost of handling goes to zero and the potential upside due to lowering barriers is large). I think we have a very good chance of acheiving this as soon as our upcoming big software release. Also, I agree, we should make sure that whatever we do is buildable by gcc. And we should also be paying Cygnus to do a real supported full port (including ld), but this is harder to achieve (need $$$ from management) at this point. However, after we have Linux and it takes off, everything related to free software would be possible :-) -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 15:39:46 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA03288; Tue, 23 Apr 1996 15:39:46 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id PAA12490; Tue, 23 Apr 1996 15:39:40 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id PAA12479; Tue, 23 Apr 1996 15:39:39 -0700 Received: from xtp.engr.sgi.com by yon.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id PAA00404; Tue, 23 Apr 1996 15:39:34 -0700 Received: by xtp.engr.sgi.com (940816.SGI.8.6.9/911001.SGI) id PAA29068; Tue, 23 Apr 1996 15:39:32 -0700 From: "Greg Chesson" Message-Id: <9604231539.ZM29066@xtp.engr.sgi.com> Date: Tue, 23 Apr 1996 15:39:31 -0700 In-Reply-To: ariel@yon (Ariel Faigon) "What target (was David ...)" (Apr 23, 1:26pm) References: <199604232026.NAA00059@yon.engr.sgi.com> X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: What target (was David ...) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I'm pleased that we are getting a Linux port started and that there is an incredible degree of interest and enthusiasm. This is independent of which hardware configurations will or should be supported. I see good reasons for doing all of them. I hope that the self-selected "steering committee" will generate some consensus tomorrow as to priorities. If there is no consensus, then Larry McVoy and I will make an "executive decision" based on available hardware resources and a shortest-path approach to getting a first port. greg From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 15:44:02 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA03564; Tue, 23 Apr 1996 15:44:02 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id PAA13339; Tue, 23 Apr 1996 15:43:55 -0700 Received: from xtp.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id PAA13334; Tue, 23 Apr 1996 15:43:54 -0700 Received: by xtp.engr.sgi.com (940816.SGI.8.6.9/911001.SGI) id PAA29190; Tue, 23 Apr 1996 15:43:53 -0700 From: "Greg Chesson" Message-Id: <9604231543.ZM29188@xtp.engr.sgi.com> Date: Tue, 23 Apr 1996 15:43:51 -0700 In-Reply-To: ariel@yon (Ariel Faigon) "Re: What target (was David ...)" (Apr 23, 3:27pm) References: <199604232227.PAA00323@yon.engr.sgi.com> X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: ariel@cthulhu.engr.sgi.com, mikemac@titian.engr.sgi.com (Mike McDonald) Subject: Re: What target (was David ...) Cc: linux@cthulhu.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Right. The objective with bringing David in has been to get something started.... a first port as an "enabling technology". I believe that many good things will happen as a result. greg From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 18:56:39 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA15166; Tue, 23 Apr 1996 18:56:39 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id SAA10702; Tue, 23 Apr 1996 18:56:34 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id SAA10695; Tue, 23 Apr 1996 18:56:32 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id SAA08149; Tue, 23 Apr 1996 18:56:29 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id VAA23190; Tue, 23 Apr 1996 21:56:28 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id VAA10149; Tue, 23 Apr 1996 21:56:27 -0400 Date: Tue, 23 Apr 1996 21:56:27 -0400 Message-Id: <199604240156.VAA10149@huahaga.rutgers.edu> From: "David S. Miller" To: wje@fir.esd.sgi.com CC: ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com In-reply-to: <199604231635.JAA13693@fir.esd.sgi.com> (wje@fir.esd.sgi.com) Subject: Re: David Miller is on the list Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Tue, 23 Apr 1996 09:35:24 -0700 From: wje@fir.esd.sgi.com (William J. Earl) There are tables of the systems under http://ssales.corp.sgi.com/products/html/periodic_table.html Unfortunately, these are inside the firewall. This having been noted, is my account at sgi going to be setup soon so that perhaps I could telnet in using the firewall and look at the docs mentioned from an internal machine? Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 18:58:36 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA15272; Tue, 23 Apr 1996 18:58:36 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id SAA10822; Tue, 23 Apr 1996 18:58:31 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id SAA10816; Tue, 23 Apr 1996 18:58:29 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id SAA08307; Tue, 23 Apr 1996 18:58:27 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id VAA23225; Tue, 23 Apr 1996 21:58:26 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id VAA10177; Tue, 23 Apr 1996 21:58:25 -0400 Date: Tue, 23 Apr 1996 21:58:25 -0400 Message-Id: <199604240158.VAA10177@huahaga.rutgers.edu> From: "David S. Miller" To: mende@piecomputer.corp.sgi.com CC: ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com In-reply-to: <9604230956.ZM12073@piecomputer.corp.sgi.com> (mende@piecomputer.corp.sgi.com) Subject: Re: David Miller is on the list Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: "Bob Mende Pie" Date: Tue, 23 Apr 1996 09:56:42 -0700 On Apr 22, 9:40pm, David S. Miller wrote: > 5) fvwm I've got 2.0.42 compiled and running ... But if dave wants to live in the dark ages of fvwm 1.x thats fine with me. Someone else is building 1.24l for me right now methinks... better check this out before bucking heads ;) > 6) teco (Must support full teco command set as described > in original DEC manuals! TECO is _the_ renaissance editor!) I've got it compiled, but beats the hell out of me if it works :-) Ill make you a deal, if I see you edit a file with it I bring you my honest to god DEC PDP-11 teco manual. [1 J^P$L$$ J <.-Z; .,(S,$ -D .)FX1 @F^B $K :L I $ G1 L>$$ Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 19:05:50 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA15754; Tue, 23 Apr 1996 19:05:50 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA11371; Tue, 23 Apr 1996 19:05:45 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id TAA11362; Tue, 23 Apr 1996 19:05:43 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id TAA09132; Tue, 23 Apr 1996 19:05:42 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id WAA23379; Tue, 23 Apr 1996 22:05:40 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id WAA10247; Tue, 23 Apr 1996 22:05:40 -0400 Date: Tue, 23 Apr 1996 22:05:40 -0400 Message-Id: <199604240205.WAA10247@huahaga.rutgers.edu> From: "David S. Miller" To: greg@xtp.engr.sgi.com CC: alambie@wellington.sgi.com, linux@cthulhu.engr.sgi.com In-reply-to: <9604230939.ZM27797@xtp.engr.sgi.com> (greg@xtp.engr.sgi.com) Subject: Re: MIPS port kickoff meeting Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: "Greg Chesson" Date: Tue, 23 Apr 1996 09:39:29 -0700 There are US Gov't customers for Linux on SGI boxes who require 64-bit OS. So, let's support tho 32-bit ARCS boxes without compromising opportunities to sell new boxes (with 64-bit Linux). Like I said I'll do the 32-bit port and work from there based upon how I feel after that. Remember I've got one kernel here which works on every 32-bit CPU type Sun has every put into a box with almost no performance loss. I can do it too for MIPS and I will. The goal being that some day I will be able to slap the same kernel image into an INDY as I can for an ONYX and a LEGO. And also, I will design it such that, as in the traditional Linux kernel model, you can config all this shit out and get the streamlined minimal kernel which only works with a certain configuation. (MM code, config it out because this is for an embedded system) Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 19:11:22 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA16016; Tue, 23 Apr 1996 19:11:21 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA11690; Tue, 23 Apr 1996 19:11:16 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) id TAA11684; Tue, 23 Apr 1996 19:11:14 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id TAA09708; Tue, 23 Apr 1996 19:11:13 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id WAA23504; Tue, 23 Apr 1996 22:11:12 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id WAA10272; Tue, 23 Apr 1996 22:11:11 -0400 Date: Tue, 23 Apr 1996 22:11:11 -0400 Message-Id: <199604240211.WAA10272@huahaga.rutgers.edu> From: "David S. Miller" To: ariel@cthulhu.engr.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <199604230609.XAA28946@yon.engr.sgi.com> (ariel@yon.engr.sgi.com) Subject: Re: Naming your machines Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: ariel@yon.engr.sgi.com (Ariel Faigon) Date: Mon, 22 Apr 1996 23:09:23 -0700 (PDT) >Actually, here's an important issue. I get to name my machines right? > Sure. Do you have some names to ask for? Unless they are taken (in the engr.sgi.com domain), you got them. Actually I've been thinking, it's a toss up between five sets of names right now: 1) "Jarry" and "Garcia" 2) "ccpenguin" and "feathers_mcgraw" 3) "tanya" and "stacy" 4) "filmore-east" and "filmore-west" 5) "ru-east" and "ru-west" bwahahahaha If anyone likes one in particular, say so. Hey thats it, I'll let everyone vote on the pair they like and thats the one I'll use ;-) Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 21:31:58 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id VAA23220; Tue, 23 Apr 1996 21:31:58 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id VAA20791; Tue, 23 Apr 1996 21:31:53 -0700 Received: from xtp.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id VAA20778; Tue, 23 Apr 1996 21:31:51 -0700 Received: by xtp.engr.sgi.com (940816.SGI.8.6.9/911001.SGI) id VAA00295; Tue, 23 Apr 1996 21:31:40 -0700 From: "Greg Chesson" Message-Id: <9604232131.ZM293@xtp.engr.sgi.com> Date: Tue, 23 Apr 1996 21:31:38 -0700 In-Reply-To: "David S. Miller" "Re: MIPS port kickoff meeting" (Apr 23, 10:05pm) References: <199604240205.WAA10247@huahaga.rutgers.edu> X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: "David S. Miller" Subject: Re: MIPS port kickoff meeting Cc: alambie@wellington.sgi.com, linux@cthulhu.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk agreed. we should begin with the version of Linux that is the most natural port for you. The other versions can come later. Note however that Lego may prefer a 64-bit kernel. g From owner-linux@cthulhu.engr.sgi.com Tue Apr 23 22:33:11 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA26251; Tue, 23 Apr 1996 22:33:11 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id WAA24028; Tue, 23 Apr 1996 22:33:00 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id WAA24022; Tue, 23 Apr 1996 22:32:59 -0700 Received: by yon.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) id WAA01149; Tue, 23 Apr 1996 22:32:55 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199604240532.WAA01149@yon.engr.sgi.com> Subject: Periodic Tables outside firewall To: davem@caip.rutgers.edu (David S. Miller) Date: Tue, 23 Apr 1996 22:32:55 -0700 (PDT) Cc: linux@yon.engr.sgi.com In-Reply-To: <199604240156.VAA10149@huahaga.rutgers.edu> from "David S. Miller" at Apr 23, 96 09:56:27 pm Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 838 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > > Date: Tue, 23 Apr 1996 09:35:24 -0700 > From: wje@fir.esd.sgi.com (William J. Earl) > > There are tables of the systems under > > http://ssales.corp.sgi.com/products/html/periodic_table.html > > Unfortunately, these are inside the firewall. > http://www.sgi.com/Technology/index.html Is outside the firewall and has similar content (click on "Periodic Tables") I also found some MIPS Assembly guides under Silicon Surf (they actually are pointers to www.mips.com) for example: http://www.mips.com/r4400/UMan/R4000.book_5.html Includes the R4K instruction set and much more. (I believe Bill mentioned this) I tried to mirror what's in our technical library, but it turns out it is all generated from SGML by DynaWeb using gci scripts so its too hairy to deal with. Anyway, the above is just as good. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Wed Apr 24 14:05:45 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA13215; Wed, 24 Apr 1996 14:05:44 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id OAA22985; Wed, 24 Apr 1996 14:05:37 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id OAA22933; Wed, 24 Apr 1996 14:05:35 -0700 Received: by yon.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux id OAA02155; Wed, 24 Apr 1996 14:05:31 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199604242105.OAA02155@yon.engr.sgi.com> Subject: Reminder: meeting in 2 hours To: linux@yon.engr.sgi.com Date: Wed, 24 Apr 1996 14:05:31 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 133 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Just a reminder: MIPS-Linux kickoff Meeting today at 16:00 Jamaica conf. room Buliding 10 Upper See you there. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Wed Apr 24 18:17:57 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA20217; Wed, 24 Apr 1996 18:17:57 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id SAA27569; Wed, 24 Apr 1996 18:17:28 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id SAA27559; Wed, 24 Apr 1996 18:17:24 -0700 Received: by yon.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux id SAA02535; Wed, 24 Apr 1996 18:17:22 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199604250117.SAA02535@yon.engr.sgi.com> Subject: Linux allocated machines To: linux@yon.engr.sgi.com Date: Wed, 24 Apr 1996 18:17:22 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1397 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Some announcements: 1) The two Indy's allocated for David are in Jeff Thomas old office in Building 9 Upper, across from the Matisse conf room. One is 6.2 MR and one 5.3 and they're both on the network. They both have empty root passwords in order to help you be as productive as possible. (info) 522 ~> rlogin root@co-op-test.engr IRIX Release 5.3 IP22 co-op Copyright 1987-1994 Silicon Graphics, Inc. All Rights Reserved. Last login: Wed Apr 24 17:50:23 PDT 1996 by UNKNOWN@unhinged.engr.sgi.com co-op 1# (info) 523 ~> rlogin root@divot.engr IRIX Release 6.2 IP22 divot Copyright 1987-1996 Silicon Graphics, Inc. All Rights Reserved. Last login: Wed Apr 24 17:45:36 PDT 1996 by ariel@co-op.engr.sgi.com divot 1# We plan to upgrade both to 200MHz CPUs so they won't slow us down (Thanks Bill). The names are historic. We are waiting for David to come up with the names he likes best (or whatever you vote for from his list) 2) I marked the room and the machines with big signs so no one comes to take these apart. I mailed 'sa@engr' regarding these being on a loan from John Loveall to Greg Chesson. 3) I'll be flying to Israel tomorrow, but I'l try to stay in touch via email, I'll be back on May 10th. Please do lots of good things while I'm gone. A summary of today's meeting will follow. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Wed Apr 24 18:35:35 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA21250; Wed, 24 Apr 1996 18:35:35 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id SAA01105; Wed, 24 Apr 1996 18:35:29 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id SAA01099; Wed, 24 Apr 1996 18:35:27 -0700 Received: by yon.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux id SAA02579; Wed, 24 Apr 1996 18:35:24 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199604250135.SAA02579@yon.engr.sgi.com> Subject: Kickoff meeting minutes To: linux@yon.engr.sgi.com Date: Wed, 24 Apr 1996 18:35:24 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 814 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk To make a long story short. Here are our Action Items + volunteers: Skeletal Kernel / sash boot: Jim Barton, Simon Cooper, Bob Mende Sandeep Cariapa expressed his wish to learn and help here. Drivers, VM questions, low-level focal point: Bill Earl 200MHz CPU upgrades Bill Earl Graphics drivers, MIT-stuff->Newport, check other options Jim, Simon Setup, serial cable, add disk space Larry gcc, binutils, gdb Ariel Office coordination Greg <-> John Loveall Simon is going back to England for a while, but he'll be with us virtually. Some interesting developments: Alan Cox, Linus (Oops...can we really talk about this?) Request: please keep this low key. Don't talk too much with your friends about all this at this point. Boy, are we excited yet :-) -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Wed Apr 24 18:48:48 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA21388; Wed, 24 Apr 1996 18:48:48 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id SAA03063; Wed, 24 Apr 1996 18:48:43 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id SAA03052; Wed, 24 Apr 1996 18:48:41 -0700 Received: from soyuz.wellington.sgi.com by yon.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id SAA01052; Wed, 24 Apr 1996 18:48:35 -0700 Received: by soyuz.wellington.sgi.com (951211.SGI.8.6.12.PATCH1042/940406.SGI) id NAA02386; Thu, 25 Apr 1996 13:48:28 +1200 From: alambie@wellington.sgi.com (Alistair Lambie) Message-Id: <199604250148.NAA02386@soyuz.wellington.sgi.com> Subject: Re: Kickoff meeting minutes To: ariel@cthulhu.engr.sgi.com Date: Thu, 25 Apr 1996 13:48:28 +1200 (NZT) Cc: linux@yon.engr.sgi.com In-Reply-To: <199604250135.SAA02579@yon.engr.sgi.com> from "Ariel Faigon" at Apr 24, 96 06:35:24 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 249 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > Some interesting developments: Alan Cox, Linus (Oops...can we really > talk about this?) > That's evil....of course it allows the imagination to run rife!! > Boy, are we excited yet :-) You bet...even if I can't be there :-( Cheers, Alistair From owner-linux@cthulhu.engr.sgi.com Wed Apr 24 19:23:11 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA21453; Wed, 24 Apr 1996 19:23:10 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA07095; Wed, 24 Apr 1996 19:23:02 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id TAA07087; Wed, 24 Apr 1996 19:23:01 -0700 Received: from surfdog.csd.sgi.com by yon.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id TAA01082; Wed, 24 Apr 1996 19:22:46 -0700 Received: by surfdog.csd.sgi.com (940816.SGI.8.6.9/911001.SGI) for linux@yon.engr.sgi.com id TAA03886; Wed, 24 Apr 1996 19:22:45 -0700 From: "Sandeep Cariapa" Message-Id: <9604241922.ZM3884@surfdog.csd.sgi.com> Date: Wed, 24 Apr 1996 19:22:44 -0700 In-Reply-To: ariel@yon.engr.sgi.com (Ariel Faigon) "Kickoff meeting minutes" (Apr 24, 6:35pm) References: <199604250135.SAA02579@yon.engr.sgi.com> X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: linux@yon.engr.sgi.com Subject: Re: Kickoff meeting minutes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk At the meeting there was some talk about hooking up with the folks in Germany who're porting to MIPS boxes. If there is any interest, the email address is: linux@informatik.uni-koblenz.de Sandeep From owner-linux@cthulhu.engr.sgi.com Wed Apr 24 19:38:56 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA21477; Wed, 24 Apr 1996 19:38:56 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA08394; Wed, 24 Apr 1996 19:38:51 -0700 Received: from yon.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id TAA08384; Wed, 24 Apr 1996 19:38:50 -0700 Received: from soyuz.wellington.sgi.com by yon.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id TAA01096; Wed, 24 Apr 1996 19:38:46 -0700 Received: by soyuz.wellington.sgi.com (951211.SGI.8.6.12.PATCH1042/940406.SGI) id OAA02669; Thu, 25 Apr 1996 14:38:30 +1200 From: alambie@wellington.sgi.com (Alistair Lambie) Message-Id: <199604250238.OAA02669@soyuz.wellington.sgi.com> Subject: Re: Kickoff meeting minutes To: cariapa@surfdog.csd.sgi.com (Sandeep Cariapa) Date: Thu, 25 Apr 1996 14:38:29 +1200 (NZT) Cc: linux@yon.engr.sgi.com In-Reply-To: <9604241922.ZM3884@surfdog.csd.sgi.com> from "Sandeep Cariapa" at Apr 24, 96 07:22:44 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 680 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > > At the meeting there was some talk about hooking up with the folks > in Germany who're porting to MIPS boxes. If there is any interest, the > email address is: linux@informatik.uni-koblenz.de > Sandeep > Another contact is: andy@waldorf-gmbh.de He was the one driving the porting group when I was last talking with them...when asked about SGI boxes he always complained that the reason they didn't work on them was that they couldn't get the info they needed! I'm sure they would be interested in what is happening here. As far as I know they have an ARCS machine up and running, and have all the crossdev stuff done (but I guess we don't need that). Cheers, Alistair From owner-linux@cthulhu.engr.sgi.com Fri Apr 26 14:59:44 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA02510; Fri, 26 Apr 1996 14:59:44 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id OAA02310; Fri, 26 Apr 1996 14:59:36 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id OAA02303; Fri, 26 Apr 1996 14:59:34 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id OAA02500 for ; Fri, 26 Apr 1996 14:59:33 -0700 Message-Id: <199604262159.OAA02500@neteng.engr.sgi.com> To: linux@cthulhu.engr.sgi.com Subject: Linux/MIPS status on non-SGI boxes Date: Fri, 26 Apr 1996 14:59:33 -0700 From: Larry McVoy Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Looks like we may have help... ------- Forwarded Message Date: Fri, 26 Apr 1996 20:14:24 +0200 From: Ralf Baechle To: lm, davem@caip.rutgers.edu, linux-mips@fnet.fr Subject: Re: Linux/SGI coming Hi all, > So, can someone provide a quick summary of the current status? All the > usual stuff, like what compilers are used, what linker, what are you > doing for userland, etc. OK. There is a bootloader available for ARC conformant systems. This implies little endian byte order. Some time ago we redesigned the interface to pass bootinformation to the kernel. The new interface uses a tagged list and can also be used to pass big information like ramdisks or fonts from the bootloader to the kernel. Due to the byteorder Milo isn't really of interest. Furthermore the Milo distribution is crippled due to (C) problems. Since you, Larry, probably have signed an NDA with SGI ;-) you can however get the complete sources, it you wish. Otherwise the crippled distribution is available via ftp.fnet.fr. What is missing are the lowlevel interfaces between the pseudo libc implementation that Milo uses and the ARC BIOS. This was required due to M$ holding the (C) for the information Milo is based on. The crosscompiler environment is based on GCC 2.7.2 and Binutils 2.6. The required patches that fix lots of bugs and add Linux/MIPS support for a.out, ELF little/big endian byte order are available on ftp.fnet.fr. Their installation isn't easy but Dave shouldn't have to much trouble with this. There are some binary packages on ftp.fnet.fr for Linux/i386 host. I'd like to have packages for more hosts, so if someone sends me binaries we'll put the online. (I could create packages for Stun's OSes if someone wants them) The libc implementation is based on the GNU libc which is available only as ELF. My home sources are based on snapshot 960210; upgrading to the newest libc will be the next thing for me to do when I sent my kernel patches to Linus. There is an older Linux libc port available - don't use it! I changed the low level kernel interfaces for 1.3 so that they should now look much more like IRIX 5.3 / RISC/os 5.01 which breaks this old (a.out ...) port completly. The distribution is still available via ftp to help building the a.out crosscompiler. The quality of the libc port to Linux is good enough to build most user stuff. GNU libc is however very aggresive to bad code; quite some packages need to be patched to compile. I'll put patches online as soon as I can. Most of the userland stuff available via ftp is based on the GNU or Debian source distributions. The kernel itself runs pretty solid for me. It currently supports the PC versions of R4000 and R4400 CPUs but probably doesn't work for SC and MC versions. I tried to support R2000/R3000/R6000/R8000/R10000 as good as possible without having hardware, so a port shouldn't be too hard. For R4000 and better many of the lowlevel functions have been written to be SMP proof but again without SMP hardware and at this point of the project SMP is nothing really invest my time in. One of the kernel features that are still missing is the special kernel code to handle denormalized numbers - not of interest for you - FPU emulation, branch delay emulation. Also there is no support for ptrace(2), therefore no debugger. The supported machines are the Mips Magnum 4000, Olivetti M700-10 (a OEM Magnum version) and Acer Pica 61, which is a kind of a successor type for the Magnum built by Acer. All these machines have a similar DMA engine, Floppy, NCR53C94 SCSI and Sonic Ethernet onboard. This SCSI/Ethernet hardware is currently not supported. I thought it would be better to use (E)ISA hardware where drivers are very easy to port and to put my time on the other parts of the system. Paul Antoine is working on DECstation/R3000 support. > Also, the handhold on information has loosened quite a bit. If there is > specific information you are looking for, let me know. In particular, > I have access to all the chip errata, something that our internal people > use a lot. I think it would be great to have all this stuff on our ftp server as it could especially help peoples with ancient CPUs. Andy's R4000 2.2 was driving me crazy ... This should answer many of your questions but probably not all, so feel free to mail me. Ralf ------- End of Forwarded Message From owner-linux@cthulhu.engr.sgi.com Fri Apr 26 15:24:28 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA02934; Fri, 26 Apr 1996 15:24:27 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id PAA05014; Fri, 26 Apr 1996 15:24:21 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id PAA05009; Fri, 26 Apr 1996 15:24:20 -0700 Received: (from lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA02924 for linux; Fri, 26 Apr 1996 15:24:15 -0700 Date: Fri, 26 Apr 1996 15:24:15 -0700 From: lm@neteng.engr.sgi.com (Larry McVoy) Message-Id: <199604262224.PAA02924@neteng.engr.sgi.com> To: linux@neteng.engr.sgi.com Subject: machine resource? Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hi- I've been talking to one of the Linux/MIPs guys in Europe and a couple of things came up: 1. We should get a box up outside the firewall to act as a source repository. We have space (a small amount) and a drop in my lab here in B9. 2. This guy offered to get a cross development environment set up if we gave him a login on a machine. I'd like to kill two birds here and stick something like a challenge/s or an indy or whatever the new R5000 is called out there. Does anyone have access to some hardware that we could use for this? If you come up with the hardware, I'll get it installed on the net (linux.sgi.com?), and help maintain it. Any ideas? Thanks, --lm --- Larry McVoy lm@sgi.com http://reality.sgi.com/lm (415) 933-1804 Copyright 1996, all rights reserved. Microsoft Network is prohibited from redistributing this work in any form, in whole or in part without license. License to distribute this work is available to Microsoft at $500. Transmission without permission constitutes an agreement to these terms. From owner-linux@cthulhu.engr.sgi.com Fri Apr 26 17:03:21 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA04933; Fri, 26 Apr 1996 17:03:20 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id RAA15651; Fri, 26 Apr 1996 17:03:06 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id RAA15638; Fri, 26 Apr 1996 17:03:05 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA04910 for ; Fri, 26 Apr 1996 17:02:58 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id RAA15614; Fri, 26 Apr 1996 17:02:57 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id RAA14141; Fri, 26 Apr 1996 17:02:54 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id UAA21442 for ; Fri, 26 Apr 1996 20:02:52 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id UAA25342; Fri, 26 Apr 1996 20:02:52 -0400 Date: Fri, 26 Apr 1996 20:02:52 -0400 Message-Id: <199604270002.UAA25342@huahaga.rutgers.edu> From: "David S. Miller" To: lmlinux@neteng.engr.sgi.com Subject: command line typo of the day... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk ? egrep SGISEGV *.c ? whoops whoops: command not found ? egrep SIGSEGV *.c Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon Apr 29 16:28:09 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA18473; Mon, 29 Apr 1996 16:28:09 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id QAA15965; Mon, 29 Apr 1996 16:27:56 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id QAA15952; Mon, 29 Apr 1996 16:27:54 -0700 Received: (from lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA18469 for linux; Mon, 29 Apr 1996 16:27:54 -0700 Date: Mon, 29 Apr 1996 16:27:54 -0700 From: lm@neteng.engr.sgi.com (Larry McVoy) Message-Id: <199604292327.QAA18469@neteng.engr.sgi.com> To: linux@neteng.engr.sgi.com Subject: scope of this mailing list Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hi SGIers, There are people from the outside that are interested in the progress of the Linux/MIPs effort. So I'm adding them to the list if they look like reasonable sorts. For example, a guy from Red Hat, the company that produces a distribution for DEC Alphas and for Intel, is now on the list. I suspect that we might be able to work with them to get a Linux/MIPs distribution. Furthermore, givem that Linux/MIPs will run IRIX elf binaries, we might be able to merge the Freeware and Linux/MIPs efforts - they have a lot of overlap. Something to think about. --lm --- Larry McVoy lm@sgi.com http://reality.sgi.com/lm (415) 933-1804 Copyright 1996, all rights reserved. Microsoft Network is prohibited from redistributing this work in any form, in whole or in part without license. License to distribute this work is available to Microsoft at $500. Transmission without permission constitutes an agreement to these terms. From owner-linux@cthulhu.engr.sgi.com Mon Apr 29 17:07:01 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA25775; Mon, 29 Apr 1996 17:07:01 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id RAA20673; Mon, 29 Apr 1996 17:06:56 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id RAA20665; Mon, 29 Apr 1996 17:06:55 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA25770 for ; Mon, 29 Apr 1996 17:06:54 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id RAA20661; Mon, 29 Apr 1996 17:06:53 -0700 Received: from relay.redhat.com by sgi.sgi.com via SMTP (950405.SGI.8.6.12/910110.SGI) for id RAA22314; Mon, 29 Apr 1996 17:06:51 -0700 Received: (qmail-queue invoked from smtpd); 30 Apr 1996 00:08:48 -0000 Received: from redhat.com (199.183.24.1) by relay.redhat.com with SMTP; 30 Apr 1996 00:08:47 -0000 Received: (from ewt@localhost) by redhat.com (8.7.4/8.7.3) id UAA03823; Mon, 29 Apr 1996 20:06:49 -0400 Date: Mon, 29 Apr 1996 20:06:49 -0400 (EDT) From: Erik Troan To: Larry McVoy cc: linux@neteng.engr.sgi.com Subject: Re: scope of this mailing list In-Reply-To: <199604292327.QAA18469@neteng.engr.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Mon, 29 Apr 1996, Larry McVoy wrote: > to get a Linux/MIPs distribution. Furthermore, givem that Linux/MIPs > will run IRIX elf binaries, we might be able to merge the Freeware and > Linux/MIPs efforts - they have a lot of overlap. Something to think > about. This raises a good question - what is the relationship between the SGI port, a port to Digital MIPS/TurboChannel machines, and the MIPS/PC port (that works on MIPS machines with PCI/EISA buses)? Will they all be the same endian? Should binarises be comaptible? What about sources such as libc and the kernel syscall interface? Erik ------------------------------------------------------------------------------- Always hoped that I'd be an apostle. Knew that I would make it if I tried. Then when we retire we can write the gospels so they'll all talk about us when we die. - "The Last Supper" from Jesus Christ Superstar | Erik Troan = http://sunsite.unc.edu/ewt/ = ewt@sunsite.unc.edu | From owner-linux@cthulhu.engr.sgi.com Tue Apr 30 16:07:21 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA20910; Tue, 30 Apr 1996 16:07:21 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id QAA04279; Tue, 30 Apr 1996 16:07:17 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id QAA04273; Tue, 30 Apr 1996 16:07:15 -0700 Received: from iron.ingenia.com by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id QAA27631; Tue, 30 Apr 1996 16:07:13 -0700 Received: (from shaver@localhost) by iron.ingenia.com (8.6.9/8.6.9) id TAA12827 for linux@engr.sgi.com; Tue, 30 Apr 1996 19:08:31 -0400 From: Mike Shaver Message-Id: <199604302308.TAA12827@iron.ingenia.com> Subject: Let's talk platforms... To: linux@cthulhu.engr.sgi.com Date: Tue, 30 Apr 1996 19:08:30 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 905 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk We're getting a whole pile of SGI hardware in to `kick the tires' over the next 6 months, and I'm wondering which of them I should claim as my test box. I can likely choose an Indy, an Indigo, possibly one of the Webforce boxes (I assume it's similar hardware to the Indigo) and, if I beg and plead and offer beer, a Challenge-S. Has an initial port target been designated? Mike (having trouble changing the address subscribed to the list, sice majordomo@cthulhu.engr doesn't seem to want to talk to me...) -- #> Mike Shaver (shaver@ingenia.com) <# #> Technical specialist, pedant, packetsmith <# #> Ingenia Communications Corporations <# #> Research, Development, Support and Sleep Deprivation <# #> Packets crafted, bugs found, rebellions quelled <# From owner-linux@cthulhu.engr.sgi.com Tue Apr 30 16:11:30 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA21397; Tue, 30 Apr 1996 16:11:30 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id QAA04672; Tue, 30 Apr 1996 16:11:22 -0700 Received: from ares.esd.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id QAA04664; Tue, 30 Apr 1996 16:11:21 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id QAA12090; Tue, 30 Apr 1996 16:11:20 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id QAA15849; Tue, 30 Apr 1996 16:11:05 -0700 Date: Tue, 30 Apr 1996 16:11:05 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199604302311.QAA15849@fir.esd.sgi.com> To: Mike Shaver Cc: linux@cthulhu.engr.sgi.com Subject: Re: Let's talk platforms... In-Reply-To: <199604302308.TAA12827@iron.ingenia.com> References: <199604302308.TAA12827@iron.ingenia.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Mike Shaver writes: > We're getting a whole pile of SGI hardware in to `kick the tires' over > the next 6 months, and I'm wondering which of them I should claim as > my test box. > > I can likely choose an Indy, an Indigo, possibly one of the Webforce > boxes (I assume it's similar hardware to the Indigo) and, if I beg and > plead and offer beer, a Challenge-S. > > Has an initial port target been designated? ... We expect to do the initial port to an Indy with an R4600 or R5000 processor, following up with other processors and platforms. A Challenge S is essentially the same as an Indy without a graphics board. From owner-linux@cthulhu.engr.sgi.com Tue Apr 30 17:28:30 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA14940; Tue, 30 Apr 1996 17:28:30 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id RAA17798; Tue, 30 Apr 1996 17:28:25 -0700 Received: from info.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id RAA17793; Tue, 30 Apr 1996 17:28:24 -0700 Received: from circle-slide.indianapolis.sgi.com by info.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id RAA26759; Tue, 30 Apr 1996 17:28:22 -0700 Received: by circle-slide.indianapolis.sgi.com (950413.SGI.8.6.12/930416.SGI) for linux@info id TAA02672; Tue, 30 Apr 1996 19:28:03 -0500 From: jm@circle-slide.indianapolis.sgi.com (jon madison) Message-Id: <9604301928.ZM2670@circle-slide.indianapolis.sgi.com> Date: Tue, 30 Apr 1996 19:28:03 -0500 X-Face: wT@!QyzV&.Q}K8PKQ90246#h4)}^Q#u|m5{gyvLyz=XrhvSP3"77M:lY.RQJC*^K]"a]{v5jS/dP8t!$L.Q'\\u|Vx*7wGC`N!kB6iYX@d?}XQ97&OdU@LQKOrKFkGb'H&'I[jq_9Y-CsJqfd?EBS;;Js`b+n^t!UK0)h_aQb[U4,T#/t0!{C[=y]d mailto:jm@sgi.com me: From owner-linux@cthulhu.engr.sgi.com Tue Apr 30 18:31:32 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA09680; Tue, 30 Apr 1996 18:31:32 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id SAA26901; Tue, 30 Apr 1996 18:31:28 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id SAA26890; Tue, 30 Apr 1996 18:31:26 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA09668 for ; Tue, 30 Apr 1996 18:31:16 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id SAA26820; Tue, 30 Apr 1996 18:31:15 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id SAA16437; Tue, 30 Apr 1996 18:31:13 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id VAA01363 for ; Tue, 30 Apr 1996 21:31:10 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id VAA05228; Tue, 30 Apr 1996 21:31:10 -0400 Date: Tue, 30 Apr 1996 21:31:10 -0400 Message-Id: <199605010131.VAA05228@huahaga.rutgers.edu> From: "David S. Miller" To: lmlinux@neteng.engr.sgi.com Subject: whee Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Syscalls are a bit faster, just started optimizing again L M B E N C H 1 . 0 S U M M A R Y ------------------------------------ Processor, Processes - times in microseconds -------------------------------------------- Host OS Mhz Null Null Simple /bin/sh Mmap 2-proc 8-proc Syscall Process Process Process lat ctxsw ctxsw --------- ------------- ---- ------- ------- ------- ------- ---- ------ ------ trombetas Linux 1.3.90 50 17 9.3K 38.6K 58K 370 88 109 trombetas Linux 1.3.97 50 14 8.9K 38.3K 56K 354 86 101 negro.rut SunOS 4.1.3_U 49 124 18.3K 63.9K 110K 470 152 262 geneva.ru SunOS 5.5 50 31 33.7K 148.2K 274K 596 174 205 *Local* Communication latencies in microseconds ----------------------------------------------- Host OS Pipe UDP RPC/ TCP RPC/ UDP TCP --------- ------------- ------- ------- ------- ------- ------- trombetas Linux 1.3.90 285 1028 1754 1368 2610 trombetas Linux 1.3.97 300 1016 1752 1376 2598 negro.rut SunOS 4.1.3_U 890 1375 2287 1573 2804 geneva.ru SunOS 5.5 530 1563 2080 1354 2398 *Local* Communication bandwidths in megabytes/second ---------------------------------------------------- Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem reread reread (libc) (hand) read write --------- ------------- ---- ---- ------ ------ ------ ------ ---- ----- trombetas Linux 1.3.90 8 4.0 23.5 17.4 18 25 42 37 trombetas Linux 1.3.97 8 4.0 23.5 17.4 18 25 41 37 negro.rut SunOS 4.1.3_U 4 2.0 19.5 8.2 18 24 41 36 geneva.ru SunOS 5.5 8 7.0 12.6 19.5 18 18 40 36 Memory latencies in nanoseconds (WARNING - may not be correct, check graphs) -------------------------------------------- Host OS Mhz L1 $ L2 $ Main mem TLB Guesses --------- ------------- --- ---- ---- -------- --- ------- trombetas Linux 1.3.90 50 20 170 180 -1 No L2 cache? trombetas Linux 1.3.97 50 20 170 180 659 No L2 cache? negro.rut SunOS 4.1.3_U 49 20 175 183 -1 No L2 cache? geneva.ru SunOS 5.5 49 - - - - Bad mhz? From owner-linux@cthulhu.engr.sgi.com Tue Apr 30 19:33:40 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA11656; Tue, 30 Apr 1996 19:33:39 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id TAA01966; Tue, 30 Apr 1996 19:33:33 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id TAA01942; Tue, 30 Apr 1996 19:33:31 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA11650 for ; Tue, 30 Apr 1996 19:33:30 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id TAA01926; Tue, 30 Apr 1996 19:33:28 -0700 Received: from informatik.uni-koblenz.de by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id TAA22209; Tue, 30 Apr 1996 19:33:25 -0700 Received: from grass (grass.uni-koblenz.de [141.26.4.65]) by informatik.uni-koblenz.de (8.7.4/8.6.9) with SMTP id EAA26130; Wed, 1 May 1996 04:33:21 +0200 (MET DST) From: Ralf Baechle Message-Id: <199605010233.EAA26130@informatik.uni-koblenz.de> Received: by grass (5.x/KO-2.0) id AA01190; Wed, 1 May 1996 04:30:58 +0200 Subject: Re: scope of this mailing list To: ewt@redhat.com (Erik Troan) Date: Wed, 1 May 1996 04:30:58 +0200 (MET DST) Cc: linux@neteng.engr.sgi.com In-Reply-To: from "Erik Troan" at Apr 29, 96 08:06:49 pm Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hi, > > to get a Linux/MIPs distribution. Furthermore, givem that Linux/MIPs > > will run IRIX elf binaries, we might be able to merge the Freeware and > > Linux/MIPs efforts - they have a lot of overlap. Something to think > > about. > > This raises a good question - what is the relationship between the SGI port, > a port to Digital MIPS/TurboChannel machines, and the MIPS/PC port (that > works on MIPS machines with PCI/EISA buses)? Will they all be the same > endian? Should binarises be comaptible? What about sources such as libc > and the kernel syscall interface? The main issue in achieving binary compatibility accross all Linux/MIPS targets is the byte order. For some machines (Mips Magnum 4000, Olivetti M700-10, SNI RM series and others more) the byte order for the kernel is configurable. For other it is fixed. This is often the case for machines that were built with NT in mind. The MIPS architecture offers us the nice feature of switchable byteorder for usermode. Thus we have a way to run software from other systems with differing native byte order. In other words: it's technological possible but it's not implemented yet. The MIPS ABI which to support is one design goal for Linux/MIPS supports only big endian systems while current Linux/MIPS implementations are all little endian. This single fact shows Linux/MIPS doesn't currently conform to the ABI but it will be relativly easy to do so in the future. The ABI explicitly forbids direct syscalls from the usercode into the kernel. Instead every program is supposed to be linked with the shared library libc.so.1 which contains the actual interface to the kernel. Linux/MIPS currently uses the GNU libc which is far being compliant to the ABI. Nevertheless Linux/MIPS contains an (currently on partial implemented) syscall interface that provides not only the syscalls known from the Linux/i386 implementation - it also features the same syscall conventions, numbers and more as implemented in IRIX and other MIPS UNIX systems. Call it a kludge but it can make things easier. Ralf From owner-linux@cthulhu.engr.sgi.com Tue Apr 30 22:36:46 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA13818; Tue, 30 Apr 1996 22:36:45 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id WAA13641; Tue, 30 Apr 1996 22:35:11 -0700 Received: from info.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id WAA13635; Tue, 30 Apr 1996 22:35:10 -0700 Received: from divot.engr.sgi.com by info.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) for id WAA18872; Tue, 30 Apr 1996 22:35:01 -0700 Received: by divot.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux@info id WAA14594; Tue, 30 Apr 1996 22:34:56 -0700 Date: Tue, 30 Apr 1996 22:34:56 -0700 From: root@divot.engr.sgi.com (Super-User) Message-Id: <199605010534.WAA14594@divot.engr.sgi.com> To: linux@info.engr.sgi.com Subject: xfishtank Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk xfishtank on divot.engr:/usr/bin/X11/xfishtank j. From owner-linux@cthulhu.engr.sgi.com Wed May 1 06:55:08 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id GAA20596; Wed, 1 May 1996 06:55:08 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id GAA05621; Wed, 1 May 1996 06:54:50 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id GAA05615; Wed, 1 May 1996 06:54:48 -0700 Received: from iron.ingenia.com by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id GAA05978; Wed, 1 May 1996 06:54:44 -0700 Received: (from shaver@localhost) by iron.ingenia.com (8.6.9/8.6.9) id JAA17982; Wed, 1 May 1996 09:56:05 -0400 From: Mike Shaver Message-Id: <199605011356.JAA17982@iron.ingenia.com> Subject: Re: Let's talk platforms... To: wje@fir.esd.sgi.com (William J. Earl) Date: Wed, 1 May 1996 09:56:04 -0400 (EDT) Cc: linux@cthulhu.engr.sgi.com In-Reply-To: <199604302311.QAA15849@fir.esd.sgi.com> from "William J. Earl" at Apr 30, 96 04:11:05 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 765 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk William J. Earl wrote: > We expect to do the initial port to an Indy with an R4600 or > R5000 processor, following up with other processors and platforms. > A Challenge S is essentially the same as an Indy without a graphics > board. Cool. That's been passed on to the salescritter as a desirable item, because of the Linux project. We'll see how it goes. Mike -- #> Mike Shaver (shaver@ingenia.com) <# #> Technical specialist, pedant, packetsmith <# #> Ingenia Communications Corporations <# #> Research, Development, Support and Sleep Deprivation <# #> Packets crafted, bugs found, rebellions quelled <# From owner-linux@cthulhu.engr.sgi.com Wed May 1 08:45:32 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id IAA27329; Wed, 1 May 1996 08:45:32 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id IAA13207; Wed, 1 May 1996 08:45:27 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id IAA13199; Wed, 1 May 1996 08:45:26 -0700 Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id IAA27314 for ; Wed, 1 May 1996 08:45:25 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id IAA17255; Wed, 1 May 1996 08:45:24 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id IAA07701; Wed, 1 May 1996 08:44:55 -0700 Date: Wed, 1 May 1996 08:44:55 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199605011544.IAA07701@fir.esd.sgi.com> To: Ralf Baechle Cc: ewt@redhat.com (Erik Troan), linux@neteng.engr.sgi.com Subject: Re: scope of this mailing list In-Reply-To: <199605010233.EAA26130@informatik.uni-koblenz.de> References: <199605010233.EAA26130@informatik.uni-koblenz.de> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ralf Baechle writes: ... > The main issue in achieving binary compatibility accross all Linux/MIPS > targets is the byte order. For some machines (Mips Magnum 4000, Olivetti > M700-10, SNI RM series and others more) the byte order for the kernel is > configurable. For other it is fixed. This is often the case for machines > that were built with NT in mind. > > The MIPS architecture offers us the nice feature of switchable byteorder > for usermode. Thus we have a way to run software from other systems with > differing native byte order. In other words: it's technological possible > but it's not implemented yet. ... I once worked on this problem on another OS base. The basic system calls are easy. ioctls, especially for streams, were much harder. Within the limits of the published ABI, as opposed to the universe of working programs, the task is not too difficult. From owner-linux@cthulhu.engr.sgi.com Thu May 2 20:31:35 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA27055; Thu, 2 May 1996 20:31:35 -0700 Return-Path: Received: by cthulhu.engr.sgi.com (950511.SGI.8.6.12.PATCH526/911001.SGI) for linux-list id UAA05379; Thu, 2 May 1996 20:30:25 -0700 Received: from neteng.engr.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id UAA05374; Thu, 2 May 1996 20:30:24 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA27044 for ; Thu, 2 May 1996 20:30:08 -0700 Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (950511.SGI.8.6.12.PATCH526/911001.SGI) for id UAA05310; Thu, 2 May 1996 20:30:00 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id UAA02709; Thu, 2 May 1996 20:29:53 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id XAA03769 for ; Thu, 2 May 1996 23:29:45 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id XAA09463; Thu, 2 May 1996 23:29:45 -0400 Date: Thu, 2 May 1996 23:29:45 -0400 Message-Id: <199605030329.XAA09463@huahaga.rutgers.edu> From: "David S. Miller" To: lmlinux@neteng.engr.sgi.com Subject: add a 'make -j vmlinux' for flavor... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk SparcClassic, 24mb of ram, swapping ferociously... Can anyone say "quality assurance"? USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND davem 202 0.0 0.2 148 64 ? S 02:45 0:00 ./crashme +2000 666 100 1:10:30 2 davem 203 0.0 0.2 148 64 ? S 02:45 0:00 ./crashme +2000 666 100 1:10:30 2 davem 206 0.0 0.2 148 64 ? S 02:45 0:00 ./crashme +2000 666 100 1:10:30 2 davem 210 0.0 0.2 148 64 ? S 02:45 0:00 ./crashme +2000 666 100 1:10:30 2 davem 279 3.0 0.2 344 56 ? R 02:46 1:09 ./crashme +2000 686 100 21 2 subprocess davem 281 3.0 0.2 344 56 ? R 02:46 1:09 ./crashme +2000 686 100 21 2 subprocess davem 288 3.0 0.2 344 52 ? R 02:46 1:08 ./crashme +2000 686 100 21 2 subprocess davem 291 3.0 0.2 344 52 ? R 02:46 1:08 ./crashme +2000 686 100 21 2 subprocess davem 428 1.9 0.2 232 56 ? R 02:49 0:40 ./crashme +2000 721 100 56 2 subprocess davem 429 1.9 0.2 228 56 ? R 02:49 0:40 ./crashme +2000 721 100 56 2 subprocess davem 430 1.9 0.2 232 56 ? R 02:49 0:40 ./crashme +2000 721 100 56 2 subprocess davem 431 1.9 0.2 232 56 ? R 02:49 0:40 ./crashme +2000 721 100 56 2 subprocess davem 508 1.6 0.2 256 52 ? R 02:50 0:32 ./crashme +2000 741 100 76 2 subprocess davem 509 1.6 0.2 252 52 ? R 02:50 0:32 ./crashme +2000 741 100 76 2 subprocess davem 510 1.6 0.2 252 52 ? R 02:50 0:32 ./crashme +2000 741 100 76 2 subprocess davem 511 1.6 0.2 256 52 ? R 02:50 0:32 ./crashme +2000 741 100 76 2 subprocess davem 544 1.5 0.2 348 52 ? R 02:51 0:30 ./crashme +2000 750 100 85 2 subprocess davem 545 1.5 0.2 348 52 ? R 02:51 0:30 ./crashme +2000 750 100 85 2 subprocess davem 546 1.5 0.2 348 52 ? R 02:51 0:30 ./crashme +2000 750 100 85 2 subprocess davem 547 1.5 0.2 344 52 ? R 02:51 0:30 ./crashme +2000 750 100 85 2 subprocess davem 580 1.4 0.2 172 52 ? R 02:52 0:28 ./crashme +2000 759 100 94 2 subprocess davem 581 1.4 0.2 176 52 ? R 02:52 0:28 ./crashme +2000 759 100 94 2 subprocess davem 582 1.4 0.2 176 52 ? R 02:52 0:28 ./crashme +2000 759 100 94 2 subprocess davem 583 1.4 0.2 172 52 ? R 02:52 0:28 ./crashme +2000 759 100 94 2 subprocess davem 644 1.3 0.2 256 52 ? R 02:53 0:24 ./crashme +2000 775 100 110 2 subprocess davem 645 1.3 0.2 256 52 ? R 02:53 0:24 ./crashme +2000 775 100 110 2 subprocess davem 646 1.3 0.2 256 52 ? R 02:53 0:24 ./crashme +2000 775 100 110 2 subprocess davem 647 1.3 0.2 256 52 ? R 02:53 0:24 ./crashme +2000 775 100 110 2 subprocess davem 680 1.3 0.2 252 52 ? R 02:54 0:23 ./crashme +2000 784 100 119 2 subprocess davem 681 1.3 0.2 252 52 ? R 02:54 0:23 ./crashme +2000 784 100 119 2 subprocess davem 682 1.3 0.2 252 52 ? R 02:54 0:23 ./crashme +2000 784 100 119 2 subprocess davem 683 1.3 0.2 252 52 ? R 02:54 0:23 ./crashme +2000 784 100 119 2 subprocess davem 684 1.3 0.2 284 52 ? R 02:54 0:23 ./crashme +2000 785 100 120 2 subprocess davem 685 1.3 0.2 284 52 ? R 02:54 0:23 ./crashme +2000 785 100 120 2 subprocess davem 686 1.3 0.2 284 52 ? R 02:54 0:23 ./crashme +2000 785 100 120 2 subprocess davem 687 1.3 0.2 284 52 ? R 02:54 0:23 ./crashme +2000 785 100 120 2 subprocess davem 712 1.3 0.2 192 52 ? R 02:55 0:22 ./crashme +2000 792 100 127 2 subprocess davem 713 1.3 0.2 196 52 ? R 02:55 0:22 ./crashme +2000 792 100 127 2 subprocess davem 714 1.3 0.2 192 52 ? R 02:55 0:22 ./crashme +2000 792 100 127 2 subprocess davem 716 1.3 0.2 192 52 ? R 02:55 0:22 ./crashme +2000 792 100 127 2 subprocess davem 821 1.2 0.2 348 52 ? R 02:57 0:19 ./crashme +2000 819 100 154 2 subprocess davem 822 1.2 0.2 348 52 ? R 02:57 0:19 ./crashme +2000 819 100 154 2 subprocess davem 876 1.2 0.2 220 56 ? R 02:59 0:18 ./crashme +2000 833 100 168 2 subprocess davem 877 1.2 0.2 220 56 ? R 02:59 0:18 ./crashme +2000 833 100 168 2 subprocess davem 878 1.2 0.2 220 56 ? R 02:59 0:18 ./crashme +2000 833 100 168 2 subprocess davem 880 1.2 0.2 216 56 ? R 02:59 0:18 ./crashme +2000 833 100 168 2 subprocess davem 1029 1.1 0.2 308 52 ? R 03:02 0:15 ./crashme +2000 871 100 206 2 subprocess davem 1030 1.1 0.2 316 52 ? R 03:02 0:15 ./crashme +2000 871 100 206 2 subprocess davem 1092 1.1 0.2 256 52 ? R 03:03 0:13 ./crashme +2000 887 100 222 2 subprocess davem 1094 1.1 0.2 256 52 ? R 03:03 0:13 ./crashme +2000 887 100 222 2 subprocess davem 1095 1.1 0.2 256 52 ? R 03:03 0:13 ./crashme +2000 887 100 222 2 subprocess davem 1096 1.1 0.2 256 52 ? R 03:03 0:13 ./crashme +2000 887 100 222 2 subprocess davem 1104 1.1 0.2 348 52 ? R 03:04 0:13 ./crashme +2000 889 100 224 2 subprocess davem 1131 1.1 0.1 344 36 ? R 03:04 0:13 ./crashme +2000 896 100 231 2 subprocess davem 1239 1.1 0.1 228 40 ? R 03:07 0:11 ./crashme +2000 923 100 258 2 subprocess davem 1240 1.1 0.2 224 52 ? R 03:07 0:11 ./crashme +2000 923 100 258 2 subprocess davem 1300 1.1 0.1 208 36 ? R 03:09 0:10 ./crashme +2000 939 100 274 2 subprocess davem 1302 1.1 0.1 204 36 ? R 03:09 0:10 ./crashme +2000 939 100 274 2 subprocess davem 1303 1.1 0.2 208 52 ? R 03:09 0:10 ./crashme +2000 939 100 274 2 subprocess davem 1306 1.1 0.2 204 52 ? R 03:09 0:10 ./crashme +2000 939 100 274 2 subprocess davem 1312 1.1 0.1 348 44 ? R 03:09 0:10 ./crashme +2000 942 100 277 2 subprocess davem 1316 1.1 0.2 348 52 ? R 03:09 0:10 ./crashme +2000 942 100 277 2 subprocess davem 1406 1.1 0.2 240 52 ? R 03:11 0:08 ./crashme +2000 965 100 300 2 subprocess davem 1450 1.1 0.1 344 40 ? R 03:12 0:07 ./crashme +2000 975 100 310 2 subprocess davem 1487 1.1 0.1 348 40 ? R 03:13 0:07 ./crashme +2000 985 100 320 2 subprocess davem 1513 1.1 0.1 228 40 ? R 03:13 0:06 ./crashme +2000 992 100 327 2 subprocess davem 1514 1.1 0.1 232 40 ? R 03:13 0:06 ./crashme +2000 992 100 327 2 subprocess davem 1568 1.1 0.2 348 52 ? R 03:15 0:06 ./crashme +2000 1006 100 341 2 subprocess davem 1571 1.1 0.2 348 52 ? R 03:15 0:06 ./crashme +2000 1006 100 341 2 subprocess davem 1597 1.1 0.2 328 52 ? R 03:15 0:05 ./crashme +2000 1012 100 347 2 subprocess davem 1608 1.1 0.2 332 52 ? R 03:15 0:05 ./crashme +2000 1015 100 350 2 subprocess davem 1649 1.0 0.2 3960 52 ? R 03:16 0:04 ./crashme +2000 1026 100 361 2 subprocess davem 1683 1.1 0.2 204 56 ? R 03:17 0:04 ./crashme +2000 1035 100 370 2 subprocess davem 1685 1.2 0.2 200 52 ? R 03:17 0:04 ./crashme +2000 1035 100 370 2 subprocess davem 1687 1.1 0.2 200 52 ? R 03:17 0:04 ./crashme +2000 1035 100 370 2 subprocess davem 1690 1.1 0.2 204 64 ? R 03:17 0:04 ./crashme +2000 1035 100 370 2 subprocess davem 1816 0.2 1.5 584 344 p0 S 03:20 0:00 -bash davem 1834 1.2 0.1 192 44 ? R 03:20 0:02 ./crashme +2000 1072 100 407 2 subprocess davem 1835 1.1 0.2 192 52 ? R 03:20 0:02 ./crashme +2000 1072 100 407 2 subprocess davem 1838 1.3 0.2 192 52 ? R 03:20 0:02 ./crashme +2000 1072 100 407 2 subprocess davem 1840 1.1 0.3 192 68 ? R 03:20 0:02 ./crashme +2000 1072 100 407 2 subprocess davem 1844 1.3 0.3 344 72 ? R 03:20 0:02 ./crashme +2000 1073 100 408 2 subprocess davem 1858 1.2 0.2 256 60 ? R 03:21 0:02 ./crashme +2000 1077 100 412 2 subprocess davem 1917 1.7 0.7 348 176 ? R 03:22 0:01 ./crashme +2000 1089 100 424 2 subprocess davem 1958 1.9 1.0 312 240 p0 R 03:22 0:01 ps -auxwww davem 1977 24.1 1.0 344 240 ? R 03:23 0:01 ./crashme +2000 1103 100 438 2 subprocess davem 2023 99.9 1.0 312 228 ? R 03:24 0:00 ./crashme +2000 1115 100 450 2 subprocess davem 2028 99.9 1.0 2248 224 ? R 03:24 0:00 ./crashme +2000 1117 100 452 2 subprocess davem 2039 99.9 0.6 220 140 ? R 03:25 0:00 ./crashme +2000 1119 100 454 2 subprocess davem 2040 99.9 1.0 308 228 ? R 03:25 0:00 ./crashme +2000 1120 100 455 2 subprocess davem 2041 99.9 1.0 320 240 ? R 03:25 0:00 ./crashme +2000 1120 100 455 2 subprocess davem 2042 99.9 1.1 332 248 ? R 03:25 0:00 ./crashme +2000 1119 100 454 2 subprocess davem 2043 99.9 0.7 240 156 ? R 03:25 0:00 ./crashme +2000 1120 100 455 2 subprocess davem 2046 99.9 0.9 296 216 ? R 03:25 0:00 ./crashme +2000 1120 100 455 2 subprocess davem 2049 99.9 1.0 308 224 ? R 03:25 0:00 ./crashme +2000 1122 100 457 2 subprocess davem 2051 99.9 0.9 300 220 ? R 03:25 0:00 ./crashme +2000 1122 100 457 2 subprocess davem 2053 99.9 1.0 308 224 ? R 03:25 0:00 ./crashme +2000 1123 100 458 2 subprocess davem 2055 99.9 1.0 308 232 ? R 03:25 0:00 ./crashme +2000 1123 100 458 2 subprocess davem 2058 99.9 0.9 304 220 ? R 03:25 0:00 ./crashme +2000 1123 100 458 2 subprocess davem 2061 99.9 1.0 304 224 ? R 03:25 0:00 ./crashme +2000 1125 100 460 2 subprocess davem 2063 0.0 0.2 148 60 ? R 03:25 0:00 ./crashme +2000 666 100 1:10:30 2 davem 2064 0.0 0.2 148 56 ? R 03:25 0:00 ./crashme +2000 666 100 1:10:30 2 davem 2065 0.0 0.2 148 56 ? R 03:25 0:00 ./crashme +2000 1125 100 460 2 subprocess davem 2066 99.9 0.6 220 144 ? R 03:25 0:00 ./crashme +2000 1126 100 461 2 subprocess davem 2067 99.9 0.6 224 144 ? R 03:25 0:00 ./crashme +2000 1126 100 461 2 subprocess davem 2068 99.9 0.6 224 144 ? R 03:25 0:00 ./crashme +2000 1127 100 462 2 subprocess davem 2069 99.9 0.6 224 144 ? R 03:25 0:00 ./crashme +2000 1127 100 462 2 subprocess davem 2070 99.9 0.6 220 140 ? R 03:25 0:00 ./crashme +2000 1126 100 461 2 subprocess davem 2071 99.9 0.6 220 144 ? R 03:25 0:00 ./crashme +2000 1127 100 462 2 subprocess davem 2074 99.9 0.6 216 140 ? R 03:25 0:00 ./crashme +2000 1127 100 462 2 subprocess davem 2086 0.0 0.2 148 64 ? R 03:26 0:00 ./crashme +2000 666 100 1:10:30 2 davem 2087 0.0 0.2 148 64 ? R 03:26 0:00 ./crashme +2000 666 100 1:10:30 2 davem 2088 0.0 0.2 148 64 ? R 03:26 0:00 ./crashme +2000 666 100 1:10:30 2 davem 2089 0.0 0.2 148 64 ? R 03:26 0:00 ./crashme +2000 666 100 1:10:30 2 davem 2090 0.0 0.2 148 64 ? R 03:26 0:00 ./crashme +2000 666 100 1:10:30 2 root 1 0.0 0.0 188 0 ? SW 02:43 0:00 (init) root 2 0.0 0.0 0 0 ? SW 02:43 0:00 (kflushd) root 3 0.0 0.0 0 0 ? SW< 02:43 0:01 (kswapd) root 4 0.0 0.0 0 0 ? SW 02:43 0:00 (nfsiod) root 5 0.0 0.0 0 0 ? SW 02:43 0:00 (nfsiod) root 6 0.0 0.0 0 0 ? SW 02:43 0:00 (nfsiod) root 7 0.0 0.0 0 0 ? SW 02:43 0:00 (nfsiod) root 11 0.0 0.1 116 28 ? S 02:43 0:00 update (bdfluHOME=/ root 27 0.0 0.0 628 4 ? S 02:44 0:00 (inetd) root 29 0.0 0.0 636 0 ? SW 02:44 0:00 (portmap) root 32 0.0 0.3 272 72 ? S 02:44 0:00 /usr/sbin/syslogd root 34 0.0 0.0 308 0 ? SW 02:44 0:00 (klogd) root 47 0.0 0.0 152 0 1 SW 02:44 0:00 (getty) root 48 0.0 0.0 152 0 2 SW 02:44 0:00 (getty) root 49 0.0 0.0 152 0 3 SW 02:44 0:00 (getty) root 50 0.0 0.0 152 0 4 SW 02:44 0:00 (getty) root 51 0.0 0.0 152 0 5 SW 02:44 0:00 (getty) root 52 0.0 0.0 152 0 6 SW 02:44 0:00 (getty) root 84 0.0 0.0 540 0 ? SWN 02:44 0:00 (punish.sh) root 99 0.0 0.0 892 0 ? SWN 02:44 0:01 (make) root 105 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 107 0.0 0.0 552 0 ? SWN 02:44 0:00 (bash) root 109 0.0 0.0 864 0 ? SWN 02:44 0:00 (make) root 119 0.0 0.0 1416 0 ? SWN 02:44 0:01 (cpp) root 120 0.0 2.8 2776 620 ? R N 02:44 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase main.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 121 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 124 0.0 0.0 952 0 ? SWN 02:44 0:01 (make) root 137 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 138 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 139 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 140 0.0 0.0 1288 0 ? SWN 02:44 0:01 (cpp) root 141 0.0 1.8 3088 408 ? R N 02:44 0:02 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase sched.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -fno-omit-frame-pointer -o - root 142 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 144 0.0 1.9 2612 440 ? R N 02:44 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase dma.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 145 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 146 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 147 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 149 0.0 0.0 1216 0 ? SWN 02:44 0:01 (cpp) root 150 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 151 0.0 0.4 3188 92 ? R N 02:44 0:02 (cc1) root 152 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 153 0.0 0.0 1232 0 ? SWN 02:44 0:00 (cpp) root 154 0.0 0.9 3216 208 ? R N 02:44 0:02 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase exec_domain.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 155 0.0 0.0 1236 0 ? SWN 02:44 0:00 (cpp) root 156 0.0 0.1 3212 40 ? R N 02:44 0:02 (cc1) root 157 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 158 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 159 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 160 0.0 0.0 1144 0 ? SWN 02:44 0:00 (cpp) root 161 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 162 0.1 0.4 3264 108 ? R N 02:44 0:02 (cc1) root 163 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 164 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 165 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 166 0.0 0.0 1420 0 ? SWN 02:44 0:01 (cpp) root 167 0.0 3.6 3100 796 ? R N 02:44 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase sys.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 168 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 169 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 170 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 171 0.0 0.0 1368 0 ? SWN 02:44 0:01 (cpp) root 172 0.0 0.4 3088 100 ? R N 02:44 0:01 (cc1) root 173 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 174 0.0 0.0 1260 0 ? SWN 02:44 0:00 (cpp) root 175 0.0 0.0 1196 0 ? SWN 02:44 0:01 (cpp) root 176 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 177 0.1 1.7 3260 396 ? R N 02:44 0:02 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase exit.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 178 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 179 0.0 0.0 1252 0 ? SWN 02:44 0:00 (cpp) root 180 0.1 1.3 3264 292 ? R N 02:44 0:02 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase signal.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 181 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 182 0.1 0.7 3272 172 ? R N 02:44 0:02 (cc1) root 183 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 184 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 185 0.0 0.0 1236 0 ? SWN 02:44 0:01 (cpp) root 186 0.0 0.8 3212 180 ? R N 02:44 0:02 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase info.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 187 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 188 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 189 0.0 0.0 1316 0 ? SWN 02:44 0:01 (cpp) root 190 0.0 0.9 3144 204 ? R N 02:44 0:02 (cc1) root 191 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 192 0.0 0.0 660 0 ? SWN 02:44 0:00 (gcc) root 193 0.0 0.0 1188 0 ? SWN 02:44 0:00 (cpp) root 194 0.0 0.0 1104 0 ? SWN 02:44 0:00 (cpp) root 195 0.0 3.7 3072 824 ? R N 02:44 0:01 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase resource.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 196 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 197 0.0 3.3 3104 740 ? R N 02:44 0:02 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase softirq.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 198 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 199 0.0 0.0 1356 0 ? SWN 02:44 0:01 (cpp) root 200 0.0 2.5 2512 568 ? R N 02:44 0:00 /usr/local/gnu/lib/gcc-lib/sparc-sun-sunos4.1.4/2.6.3/cc1 -quiet -dumpbase sysctl.c -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -o - root 201 0.0 0.0 1128 0 ? SWN 02:44 0:00 (as) root 1811 0.1 1.0 668 236 ? S 03:20 0:00 /usr/etc/in.telnetd From owner-linux@cthulhu.engr.sgi.com Fri May 10 04:21:09 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA20001; Fri, 10 May 1996 04:21:09 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id LAA12246 for linux-list; Fri, 10 May 1996 11:19:43 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA12234 for ; Fri, 10 May 1996 04:19:40 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA19918 for ; Fri, 10 May 1996 04:19:39 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA12225 for ; Fri, 10 May 1996 04:19:38 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id EAA23217; Fri, 10 May 1996 04:19:37 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id HAA08456; Fri, 10 May 1996 07:19:33 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id HAA00626; Fri, 10 May 1996 07:19:33 -0400 Date: Fri, 10 May 1996 07:19:33 -0400 Message-Id: <199605101119.HAA00626@huahaga.rutgers.edu> From: "David S. Miller" To: lnz@dandelion.com CC: sparclinux@vger.rutgers.edu, lmlinux@neteng.engr.sgi.com Subject: check this out... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk (Leonard, I thought you'd get a kick out of this...) I stress tested my new Sparc SCSI driver with the following bus configuration: ID 3: SCSI2 Seagate disk ID 4: pre-CCS SCSI1 disk of unknown vendor type ;-) ID 5: FAST SCSI2 Conner drive I ran three instances of a program which just did random seeks forever, one on each drive. (thank god for lmbench programs which have dual role as stress/stability testers ;-) I was getting bus lockups now and then, and happily my abort/reset code completely recovered the bus back into a working state and things proceeded. After about 30 minutes of analyzing state dumps from my driver when this would happen I figure out what was going on. My driver now fixes this problem and does not reset anymore no matter how hard I smash all the drives on this chain. Anyways, to get to the point, for your edification Leonard, here is the comment above my fix for the problem. Enjoy ;-) /* A fix for broken SCSI1 targets, when they disconnect * they lock up the bus and confuse ESP. So disallow * disconnects for SCSI1 targets for now until we * find a better fix. * * Addendum: This is funny, I figured out what was going * on. The blotzed SCSI1 target would disconnect, * one of the other SCSI2 targets or both would be * disconnected as well. The SCSI1 target would * stay disconnected long enough that we start * up a command on one of the SCSI2 targets. As * the ESP is arbitrating for the bus the SCSI1 * target begins to arbitrate as well to reselect * the ESP. The SCSI1 target refuses to drop it's * ID bit on the data bus even though the ESP is * at ID 7 and is the obvious winner for any * arbitration. The ESP is a poor sport and refuses * to lose arbitration, it will continue indefinately * trying to arbitrate for the bus and can only be * stopped via a chip reset or SCSI bus reset. * Therefore _no_ disconnects for SCSI1 targets * thank you very much. ;-) */ Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon May 13 07:28:58 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id HAA24667; Mon, 13 May 1996 07:28:57 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id OAA18053 for linux-list; Mon, 13 May 1996 14:27:32 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id HAA18044 for ; Mon, 13 May 1996 07:27:30 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id HAA24594 for ; Mon, 13 May 1996 07:27:29 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id HAA18037 for ; Mon, 13 May 1996 07:27:28 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id HAA02189; Mon, 13 May 1996 07:27:26 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id AAA28631; Mon, 13 May 1996 00:05:06 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id AAA05898; Mon, 13 May 1996 00:05:04 -0400 Date: Mon, 13 May 1996 00:05:04 -0400 Message-Id: <199605130405.AAA05898@huahaga.rutgers.edu> From: "David S. Miller" To: tridge@cs.anu.edu.au CC: lmlinux@neteng.engr.sgi.com, torvalds@cs.helsinki.fi Subject: wicked checksum optimization... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I think I figured out how to do it all "the right way(tm)" The big problem is alignment, but %97 of the time the buffer is aligned how we like. I've decided it is ok to take the hit of an unaligned access trap for the %3 cases, but not that much of a hit. The implementation looks like this: All loads and stores in the ip checksum routines will look the same, the only time we do stores is for the csum/copy routines. Anyways the eight instruction codes recognized will be for: ld [%o0 + offset], %o4 ld [%o0 + offset], %o5 lduh [%o0 + offset], %o4 lduh [%o0 + offset], %o5 st %o4, [%g3 + offset] st %o5, [%g3 + offset] sth %o4, [%g3 + offset] sth %o5, [%g3 + offset] The unaligned trap handler (before it even tries to save any state) will look something like: mna_trap: andcc %l0, PSR_PS, %g0 be,a mna_fromuser ld [%l1], %l5 sethi %hi(LOAD_O4), %l4 and %l5, %l4, %l6 cmp %l6, %l4 bne 1f sethi %hi(LOAD_O5), %l4 mov %l1, %g6 ! %pc sethi %hi(C_LABEL(csum_ldo4_fixup)), %l1 or %l1, %lo(C_LABEL(csum_ldo4_fixup)), %l1 wr %l0, 0x0, %psr ! fix cond-codes and %l5, LOAD_IMMEDIATE_FIELD, %g7 srl %g7, LOAD_IMMEDIATE_SHIFT, %g7 ! offset jmp %l1 rett %l1 + 0x4 1: /* etc. for other instructions recognized */ mna_fromuser: SAVE_ALL /* From user mode or something we don't handle for the * kernel. */ call C_LABEL(do_mna) nop RESTORE_ALL Ok, now the fixup routines just look like: csum_ldo4_fixup: ldub [%o0 + %g7], %g4 add %g7, 1, %g7 ldub [%o0 + %g7], %g5 sll %g4, 24, %g4 add %g7, 1, %g7 sll %g5, 16, %g5 or %g4, %g5, %o4 ldub [%o0 + %g7], %g4 add %g7, 1, %g7 ldub [%o0 + %g7], %g5 sll %g4, 8, %g4 or %g5, %g4, %g4 jmp %g6 ! wheee... or %o4, %g4, %o4 and so on... then csum_parial and friends can just blaze through assuming proper alignment for all pointers to the packet contents etc. Nifty eh? Sparc is fun... Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon May 13 18:24:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA02898; Mon, 13 May 1996 18:24:17 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA11019 for linux-list; Tue, 14 May 1996 01:22:53 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA11014 for ; Mon, 13 May 1996 18:22:52 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id SAA02367 for ; Mon, 13 May 1996 18:22:51 -0700 Message-Id: <199605140122.SAA02367@neteng.engr.sgi.com> To: lmlinux@neteng.engr.sgi.com Subject: Uselinux and the Linux/SPARC port (forwarded) Date: Mon, 13 May 1996 18:22:51 -0700 From: Larry McVoy Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk ------- Forwarded Message Date: Sat, 11 May 1996 10:52:53 -0500 From: Miguel de Icaza To: sparclinux-cvs@caipfs.rutgers.edu cc: davem@caip.rutgers.edu, tridge@cs.anu.edu.au Subject: Uselinux and the Linux/SPARC port Hello guys, On Jannuary the Uselinux conference will be help together with the Usenix technical conference (http://www.usenix.org). David and I had plans to make a technical presentation on the Linux/SPARC port. I think Linux/SPARC is not just another port, but a port that has some unique features not found on other ports. The idea is to co-author this paper with those of you wanting to help/contribute to the article. I have assembled a list of things I think are interesting on Linux/SPARC, I guess that before we can make a presentation on why we find Linux/SPARC to be a unique port we will have to massage this quite a bit. I have already mailed this one to Michael Johnson (He is the technical session chair I think), if you want to co-author this with David and I please, contact me (and CC the sparclinux-cvs list. David will be very busy before leaving to SGI, so I'm doing the coordination for this). Best wishes, Miguel. * MMU/cache Sparc have 3 types of MMU -- this is easy to plug into Linux. Sparc have Virtual Addressed Caches (VAC) and Physical caches -- these require changes to Linux kernel. With the VACs, one must be careful to not complete flush the caches as it was being done initially, because they damage performace quite a bit. As an extra challenge, some MMU are buggy, MMUs are accessed in different ways. Linux/SPARC uses pointer functions for most MMU/cache manipulation * SunOS compatibility. We use the model that Linus used to get OSF/1 compatibility. (we use same constants, and same structures for the kernel, thus no need to translate anything). This model lets us have a userland ready early during the port and the code is written when something fails to run properly. Compare this to NetBSD, 4114 lines of code for Sparc code plus 2753 lines of generic emulation "libraries"; compare this to Linux: 1140 lines. We think this is the right way to future ports. Linux emulation code is mostly related to features not found usually in Linux (like assumption from SunOS applications on the OS), while NetBSD's emulation code is spent on doing conversions in/from each OS constants and data structures, so Linux does not have a runtime performance penalty for running SunOS applications. Sparc drivers have to support the Linux interface and the SunOS interface to make some programs happy (X-Window), the mouse driver, keyboard driver and frame buffer drivers provide SunOS interfaces. The mouse and keyboard driver provide the same interface to Linux applications as it is found on original i386 port. * Drivers for undocumented hardware. Getting information out of Sun is not very easy. Documentation for some hardware came from the vendor that makes the chips (scsi and lance drivers), sources for the NetBSD, Sprite and the Xinu operating system were used as references at the beginning of the port to understand the architecture. bwtwo, cg3 and cg6 drivers were based on existing NetBSD drivers and a generic frame buffer interface for Linux/SPARC was coded. A driver for the cg14 has been written using only Solaris include file for the video card and some poking at the rom letting us emulate a lowend graphics card on it. * Stability and performance. During the port the use of crashme has been constantly used to avoid the same mistakes on Sun operating system. lmbench has been used to test the performance of the operating system. It was not just used as a benchmarking tool, but also to pinpoint weaknesses in the port. After a couple of weeks tunning the port, Linux/SPARC was able to keep up against SunOS and Solaris on the same hardware and in some cases outperforming them. The lmbench results are more interesting than they may appear at first sight: They do not only reflect that Linux is a great operating system, but most sadly it reflects the fact that corporate operating systems are sometimes bloated and slow. The reason for bloated operating systemd may come from different sources, as documented in the 4.3BSD book, there were 13 memory allocators on the BSD kernel in 1986, at that point they were aware of the problem: code is being rewritten over and over. This in my opinion means that most kernel programmers lack a deep knowledge on the operating system and may be writting thing that are not completely clean (anecdote: over the past two weeks I made one remark and one suggestion to the kernel to Linus, and even when they looked fine to me and many people agree they are Linus quickly pointed me out where the design flaws were in; it was related rfork, btw). * SMP Problems encountered when porting Linux to the Sparc. Not all SMP machines are born the same, there are some hacks required to get SMP working on the Sparc. [Ufinished section I will complete this section later] * Portability and the AP+ The Linux/SPARC port is itself a relatively easy to port to non Sun hardware. Andrew Tridgell and his hackers team in Canberra have ported Linux/SPARC to the AP+ multiprocessor. [ This section is still not finished ] * Bootstraping the SPARC. Booting the SPARC required: a) cleaning up the ext2fs to make it aware of the endianess of the SPARC; b) the merging into the kernel of the nfsroot allowed one of the developers to work without a hard disk, and let people test drive Linux kernel without needing to reformat their disks. Jay Eastabrook's Alpha console code split was used as the second attempt at the Linux console code. Once we had this one, we got the same functionality of Linux/i386 on the sparc. * SILO. SILO is unique in one aspect: It is the first Linux boot loader that uses the ext2fs library from the ext2fs tool suite by Remy Card and Ted Tso. This is a good thing because it let us write the boot loader in a very short time frame. The SILO bootloader fully understands the ext2fs and thus does not require a special boot loader installer for each kernel image that is made available. There is still work in progress on LILO to make it work with iso9660 cdroms and boot loading. * The port David Miller setup an account for the developers on vger to have access to his CVS tree so that we could make changes directly to the source tree without taking time from him. Simple rules were set: test before you commit your code. Another idea that was pushed since the beginning was to keep track of current kernel developement. Even if this would imply that we had to spend some time merging and fixing sparc stuff on our kernels, it helped us to merge our tree faster and easier than the other ports. Letting versions slip proved to be not a very good idea, and the MkLinux people will suffer with it as did the m68k guys some months ago. * Userland The first attempt at a Libc port was done by porting Linux's a.out Libc4 to the SPARC. Later a GNU libc port was attempted, but because of the adapting nature of the kernel to the host OS for binary compatibility, the GNU libc port was found to not be possible at the time, we may try again as soon as some issues are hashed out on glibc. Currently the Linux Libc 5 is in use and ELF loading has been fixed into the kernel. Eric Youngdale is making the elf loader less i386-centric, and thus our patches will go in easier. The libc5 supports shared executables and Eric's ld.so linker has been ported to the SPARC, as well as adapting it to Linux (originally it was written and tested on Solaris). What is amazing is that this linker is quite portable nowadays. RedHat and Debian are both working on Linux distributions for the SPARC. The goal is to have the same interface on all different architectures and in the future encourage commercial software companies to compile with a cross compiler versions of their software for all the available platforms of Linux. ------- End of Forwarded Message From owner-linux@cthulhu.engr.sgi.com Mon May 13 18:24:32 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA03012; Mon, 13 May 1996 18:24:31 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA11067 for linux-list; Tue, 14 May 1996 01:23:08 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA11062 for ; Mon, 13 May 1996 18:23:07 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id SAA02399 for ; Mon, 13 May 1996 18:23:06 -0700 Message-Id: <199605140123.SAA02399@neteng.engr.sgi.com> To: lmlinux@neteng.engr.sgi.com Subject: Linux/AP+ technical report (forwarded) Date: Mon, 13 May 1996 18:23:06 -0700 From: Larry McVoy Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk ------- Forwarded Message Date: Sat, 11 May 1996 22:51:12 +1000 From: Andrew Tridgell To: Multiple recipients of list Subject: Linux/AP+ technical report Hi, We've written a short tech report on what we've done so far to port Linux to the AP1000+ multicomputer. Its available on our home page at http://cap.anu.edu.au/cap/projects/linux We'd be very interested to hear comments on what you think of our approach. Obviously our port is still pretty simple, and a lot more needs to be done to make a really multicomputer OS, but at least its a start :-) Andrew PS: I'm also hoping this might start some discussion on this list! ------- End of Forwarded Message From owner-linux@cthulhu.engr.sgi.com Tue May 14 20:30:16 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA09081; Tue, 14 May 1996 20:30:16 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id DAA07340 for linux-list; Wed, 15 May 1996 03:28:51 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA07333 for ; Tue, 14 May 1996 20:28:49 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA09037 for ; Tue, 14 May 1996 20:28:48 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA07320; Tue, 14 May 1996 20:28:48 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id UAA08560; Tue, 14 May 1996 20:28:45 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id XAA00765; Tue, 14 May 1996 23:28:39 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id XAA24278; Tue, 14 May 1996 23:28:38 -0400 Date: Tue, 14 May 1996 23:28:38 -0400 Message-Id: <199605150328.XAA24278@huahaga.rutgers.edu> From: "David S. Miller" To: lm@gate1-neteng.engr.sgi.com CC: lmlinux@neteng.engr.sgi.com, torvalds@cs.helsinki.fi, sparclinux-cvs@caipfs.rutgers.edu Subject: numbers... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Two nights of coding, not bad... This has to be the fastest csum and csum_copy humanly codable on the Sparc. Here are some initial results. On each run the cache was purposely forced to be cold on each iteration: sun4m SS10 115mhz hypersparc, 256k cache measure_csum_partial csum_partial: sz[1024] 10000 iterations takes 17009430 microseconds csum_partial: sz[1024] 1 iteration takes <1700 microseconds>==<332 nanoseconds> csum_partial: sz[2048] 10000 iterations takes 32609649 microseconds csum_partial: sz[2048] 1 iteration takes <3260 microseconds>==<636 nanoseconds> csum_partial: sz[3072] 10000 iterations takes 48152422 microseconds csum_partial: sz[3072] 1 iteration takes <4815 microseconds>==<940 nanoseconds> csum_partial: sz[4096] 10000 iterations takes 63708679 microseconds csum_partial: sz[4096] 1 iteration takes <6370 microseconds>==<1244 nanoseconds> measure_csum_partial_copy csum_partial_copy: sz[1024] 10000 iterations takes 30865212 microseconds csum_partial_copy: sz[1024] 1 iteration takes <3086 microseconds>==<602 nanoseconds> I'm estimating the function call overhead is around 29 nanoseconds to get into the damn routine, and around 3 or 4 nanoseconds overhead from the loop constructs etc. in the benchmark. It seems to scale very nicely, on this chip you tend eat around 8ns for byte end aligned buffers and around 5ns for an extraneous halfword at the end of the buffer. 0.4us/Kbyte for csum, and 0.6us/Kbyte for csum_copy, _really_ impressive. Here are some figures for small buffers on the same cpu: csum_partial: sz[20] 200000 iterations takes 55822206 microseconds csum_partial: sz[20] 1 iteration takes <279 microseconds>==<54 nanoseconds> csum_partial: sz[21] 200000 iterations takes 64016336 microseconds csum_partial: sz[21] 1 iteration takes <320 microseconds>==<62 nanoseconds> csum_partial: sz[22] 200000 iterations takes 61093525 microseconds csum_partial: sz[22] 1 iteration takes <305 microseconds>==<59 nanoseconds> csum_partial: sz[23] 200000 iterations takes 65481187 microseconds csum_partial: sz[23] 1 iteration takes <327 microseconds>==<63 nanoseconds> csum_partial: sz[24] 200000 iterations takes 61168735 microseconds csum_partial: sz[24] 1 iteration takes <305 microseconds>==<59 nanoseconds> csum_partial: sz[25] 200000 iterations takes 69001025 microseconds csum_partial: sz[25] 1 iteration takes <345 microseconds>==<67 nanoseconds> csum_partial: sz[26] 200000 iterations takes 66418949 microseconds csum_partial: sz[26] 1 iteration takes <332 microseconds>==<64 nanoseconds> csum_partial: sz[27] 200000 iterations takes 71029491 microseconds csum_partial: sz[27] 1 iteration takes <355 microseconds>==<69 nanoseconds> csum_partial: sz[28] 200000 iterations takes 66360048 microseconds csum_partial: sz[28] 1 iteration takes <331 microseconds>==<64 nanoseconds> csum_partial: sz[29] 200000 iterations takes 74353705 microseconds csum_partial: sz[29] 1 iteration takes <371 microseconds>==<72 nanoseconds> csum_partial: sz[30] 200000 iterations takes 71737147 microseconds csum_partial: sz[30] 1 iteration takes <358 microseconds>==<69 nanoseconds> csum_partial: sz[31] 200000 iterations takes 76436420 microseconds csum_partial: sz[31] 1 iteration takes <382 microseconds>==<74 nanoseconds> csum_partial: sz[32] 200000 iterations takes 40741293 microseconds csum_partial: sz[32] 1 iteration takes <203 microseconds>==<39 nanoseconds> csum_partial: sz[33] 200000 iterations takes 48651585 microseconds csum_partial: sz[33] 1 iteration takes <243 microseconds>==<47 nanoseconds> csum_partial: sz[34] 200000 iterations takes 46065031 microseconds csum_partial: sz[34] 1 iteration takes <230 microseconds>==<44 nanoseconds> csum_partial: sz[35] 200000 iterations takes 50451529 microseconds csum_partial: sz[35] 1 iteration takes <252 microseconds>==<49 nanoseconds> csum_partial: sz[36] 200000 iterations takes 45143096 microseconds csum_partial: sz[36] 1 iteration takes <225 microseconds>==<43 nanoseconds> csum_partial: sz[37] 200000 iterations takes 53111738 microseconds csum_partial: sz[37] 1 iteration takes <265 microseconds>==<51 nanoseconds> csum_partial: sz[38] 200000 iterations takes 50421138 microseconds csum_partial: sz[38] 1 iteration takes <252 microseconds>==<49 nanoseconds> csum_partial: sz[39] 200000 iterations takes 54893618 microseconds csum_partial: sz[39] 1 iteration takes <274 microseconds>==<53 nanoseconds> csum_partial: sz[40] 200000 iterations takes 50453690 microseconds csum_partial: sz[40] 1 iteration takes <252 microseconds>==<49 nanoseconds> csum_partial: sz[41] 200000 iterations takes 58411664 microseconds csum_partial: sz[41] 1 iteration takes <292 microseconds>==<57 nanoseconds> csum_partial: sz[42] 200000 iterations takes 55732943 microseconds csum_partial: sz[42] 1 iteration takes <278 microseconds>==<54 nanoseconds> csum_partial: sz[43] 200000 iterations takes 60187768 microseconds csum_partial: sz[43] 1 iteration takes <300 microseconds>==<58 nanoseconds> csum_partial: sz[44] 200000 iterations takes 55766810 microseconds csum_partial: sz[44] 1 iteration takes <278 microseconds>==<54 nanoseconds> csum_partial: sz[45] 200000 iterations takes 63732553 microseconds csum_partial: sz[45] 1 iteration takes <318 microseconds>==<62 nanoseconds> Now, some other CPU types. sun4m MicroSparcI, 40mhz, 16k icache 20k dcache (can't remember if thats right or not...): measure_csum_partial csum_partial: sz[1024] 10000 iterations takes 62380730 microseconds csum_partial: sz[1024] 1 iteration takes <6238 microseconds>==<1218 nanoseconds> csum_partial: sz[2048] 10000 iterations takes 127199716 microseconds csum_partial: sz[2048] 1 iteration takes <12719 microseconds>==<2484 nanoseconds> measure_csum_partial_copy csum_partial_copy: sz[1024] 10000 iterations takes 180276825 microseconds csum_partial_copy: sz[1024] 1 iteration takes <18027 microseconds>==<3520 nanoseconds> Thats around 2.5us/Kbyte for csum, 3.6us/Kbyte for csum_copy, not bad and could be a bit better with some reworking of the scheduling tuned for the msI instruction cache to get less stalls. Probably not worth it though (I come to this conclusion notably because when Gordon Irlam reworked the SunOS/Solaris window trap handlers to do an extra window for each trap for cache reasons it turned out to make no difference performance wise in the "real world" although the code was indeed more efficient on the msI). sun4m SS10 Viking/MXCC, 50Mhz, 1mb physical cache, 16k icache 20k dcache (again, correct me here if I am wrong on the i/d sizes): measure_csum_partial csum_partial: sz[1024] 10000 iterations takes 31893405 microseconds csum_partial: sz[1024] 1 iteration takes <3189 microseconds>==<622 nanoseconds> csum_partial: sz[2048] 10000 iterations takes 60608539 microseconds csum_partial: sz[2048] 1 iteration takes <6060 microseconds>==<1183 nanoseconds> csum_partial: sz[3072] 10000 iterations takes 89327514 microseconds csum_partial: sz[3072] 1 iteration takes <8932 microseconds>==<1744 nanoseconds> csum_partial: sz[4096] 10000 iterations takes 118067205 microseconds csum_partial: sz[4096] 1 iteration takes <11806 microseconds>==<2305 nanoseconds> measure_csum_partial_copy csum_partial_copy: sz[1024] 10000 iterations takes 45946764 microseconds csum_partial_copy: sz[1024] 1 iteration takes <4594 microseconds>==<897 nanoseconds> csum_partial_copy: sz[2048] 10000 iterations takes 88614537 microseconds csum_partial_copy: sz[2048] 1 iteration takes <8861 microseconds>==<1730 nanoseconds> csum_partial_copy: sz[3072] 10000 iterations takes 131338863 microseconds csum_partial_copy: sz[3072] 1 iteration takes <13133 microseconds>==<2565 nanoseconds> The huge physical cache certainly seems to make a difference, although I think it is also noticable that the on-chip insn cache would do better with my algorithm if it were just a tad bigger. Ho hum... Note also how it doesn't scale as linearly as on the Hyper and the msI, again this puzzles me bacaus the icache is smaller on msI. sun4c SLC, 20MHZ, 64k I/D combined L2 virtual cache: measure_csum_partial csum_partial: sz[1024] 10000 iterations takes 227199286 microseconds csum_partial: sz[1024] 1 iteration takes <22719 microseconds>==<4437 nanoseconds> measure_csum_partial_copy csum_partial_copy: sz[1024] 10000 iterations takes 539569714 microseconds csum_partial_copy: sz[1024] 1 iteration takes <53956 microseconds>==<10538 nanoseconds> Not too bad for this piece of garbage, the pure virtual 64k cache is probably the real helper here. I see no other factor that can get numbers like this on such a shit cpu. 4.5ms/Kbyte for csum, and 10.6ms/Kbyte for csum/copy... shit Jacobsons m68k algorithm only gets 134us/Kbyte on a 20MHZ 68020. sun4c IPX, 40MHZ, 64k I/D combined L2 virtual cache: measure_csum_partial csum_partial: sz[1024] 10000 iterations takes 112377730 microseconds csum_partial: sz[1024] 1 iteration takes <11237 microseconds>==<2194 nanoseconds> csum_partial: sz[2048] 10000 iterations takes 223668577 microseconds csum_partial: sz[2048] 1 iteration takes <22366 microseconds>==<4368 nanoseconds> measure_csum_partial_copy csum_partial_copy: sz[1024] 10000 iterations takes 345064536 microseconds csum_partial_copy: sz[1024] 1 iteration takes <34506 microseconds>==<6739 nanoseconds> A little more than twice as fast as the SLC, again the 64k virtual cache is the performance factor even here and it seems the cache can keep up with this cpu when it's hot. 2.2us/Kbyte for csum, and 6.8us/Kbyte for csum_copy, not bad at all. I've verified all of my new code with a very extensive "cksum_helper" program I wrote which also ran the above benchmarks after the verification suite completed successfully. Now I just have to stick this shit into the kernel and see if it goes ok. If all goes well we might end up being able to beat Solaris on those TCP lmbench bandwidth numbers, no promises. Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Wed May 15 09:42:22 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA01100; Wed, 15 May 1996 09:42:21 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA26408 for linux-list; Wed, 15 May 1996 16:40:57 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA26403 for ; Wed, 15 May 1996 09:40:55 -0700 Received: from lanta.engr.sgi.com (lanta.engr.sgi.com [192.26.75.15]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA01002 for ; Wed, 15 May 1996 09:40:55 -0700 Received: by lanta.engr.sgi.com (940816.SGI.8.6.9/911001.SGI) id JAA08277; Wed, 15 May 1996 09:40:53 -0700 Date: Wed, 15 May 1996 09:40:53 -0700 From: nn@lanta.engr.sgi.com (Neal Nuckolls) Message-Id: <199605151640.JAA08277@lanta.engr.sgi.com> To: davem@caip.rutgers.edu Subject: Re: numbers... Cc: sparclinux-cvs@caipfs.rutgers.edu, torvalds@cs.helsinki.fi, lmlinux@neteng.engr.sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > sun4m SS10 115mhz hypersparc, 256k cache > measure_csum_partial > csum_partial: sz[1024] 10000 iterations takes 17009430 microseconds > csum_partial: sz[1024] 1 iteration takes <1700 microseconds>==<332 nanoseconds> Maybe I'm dense this morning but I don't understand the numbers. You measure the realtime to do a sequential IP checksum on a 1K buffer and you always invalidate the processor cache (I$, D$, and Secondary$ or just some subset of these?) and don't include the cost of doing the cache invalidate in the time above. 10000 of these costs a hair over 17s, divide by 10000 gives 1.7ms per iteration. This seems way high so must include the cost of the cache invalidate or something? What does the 332ns refer to? My back of the envelope: If I recall, the cacheline on a sun4m is 32bytes. Assuming something in the 300-600ns/secondarycachemiss range and a single pending cachemiss at a time would put most any "touch the data" operation on 1K of data in the 9.6-19.2us ballpark or 9-18ns/byte range. Does the hypersparc processor support multiple concurrent cache misses? Or does it have a Viking-like sequential reference detector and automatic cache prefetch logic? > sun4m MicroSparcI, 40mhz, 16k icache 20k dcache > ... > Thats around 2.5us/Kbyte for csum, This must be hot$ that you're talking about? Exactly when do you invalidate the caches? thanks. neal From owner-linux@cthulhu.engr.sgi.com Wed May 15 15:44:48 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA21025; Wed, 15 May 1996 15:44:47 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA26316 for linux-list; Wed, 15 May 1996 22:43:22 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA26301 for ; Wed, 15 May 1996 15:43:21 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id PAA19394; Wed, 15 May 1996 15:43:19 -0700 Message-Id: <199605152243.PAA19394@neteng.engr.sgi.com> To: tridge@cs.anu.edu.au From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: linux-mc@arvidsjaur.anu.edu.au, Linus.Torvalds@cs.Helsinki.FI, linux@neteng.engr.sgi.com, alan@cymru.net Subject: Re: mpp kernel interface Date: Wed, 15 May 1996 15:43:19 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : With 30 people now on this list there must be someone else who wants : to say something ... I'm going to try. I'm probably going to do a half assed job, as I am feeling a bit sick today. But I'll give it a go. : It really depends on how we end up using this stuff. Does anyone out : there have any experience with implementing things like remote fork, : remote paging, remote files/sockets etc? What sorts of interfaces are : useful for doing stuff like that? I have a few ideas. Lots of them are stolen from the UCAL Locus project, Jim Bob says check it out. First, this is mostly a naming problem. Wrap your brain around that. We need to have clear in our heads exactly how everything is named. Once you can draw that picture, the implementation becomes straight forward. After you read through this, you may or may not be in basic agreement. If we ever converge, I will volunteer to write "man pages" for each of the chunks of work so that we have a well documented TODO list. It is as close as I've ever gotten to a spec. Things we need to name hosts cluster processes devices files sockets other things cluster {join,leave} SMP vs cluster? The hard one is sockets. I've never seen a good solution to that. I'll come back to that. First, I want to go through the other ones and offer suggestions. Hosts are just hosts, nothing changes there. Clusters are a mapping of "cluster_name" -> "list of hosts". Think of getclustbyname(). I did this for SparcClusters, it worked pretty well. The cluster is the name that you use to get to your cluster. This implies that you wack rlogin/telnet and/or you wack DNS to to translate from the cluster name to the hostname to the IP address of that host. DNS is the easiest place. Processes have two major chunks of work, the PID name space and how you do remote processes. For the PID name space, make pid_t a 32 bit int, make the top 16 bits the host part, and the bottom 16 bits the pid part. (We need to come back to the host part when we discuss process migration.) A host part of "0" means "this host". So a "kill -HUP 1" will always restart init. Remote processes. This part gets fun, fun, fun. Think of how we have files as objects in the kernel, in C++ terms, an inode is a class with all virtual methods - each instance of the class implments its own methods. We need to do that for processes. For every operation we currently do on a process, we need to make that a function call. You want this layer to be very thin, it can't be a performance hit for local processes or we blew it. The intances of the process class I imagine are at least "local", "remote", "local debugged", "remote debugged". I can also image using this to implement "local or remote, gang scheduled". See how that works? I'm hand waving like crazy here. I'm not positive the debugging stuff works in this layer, but I would love it if all the System V /proc crap was buried in an optional instance of the process class. I believe that you can make the non debugged instance faster. Devices I sort of punt on. For device access, I would just use the remote mag tape protocol (or something very, very similar) so that all of the locking, etc., still works - since you ship all the requests to the system w/ the device, that kernel can implement the locks. Any issues here? Files. I have also punted on this. I have never gotten that excited about a cache coherent distributed file system, though others certainly do. It's not because I don't think it is useful. I believe it can be done and that we have the talent right here on this list to do it. So I'll bow out of commenting on it, other than to say make sure mmap works right. Sockets. This is a hard problem. Some people think that a socket should stick around after the CPU that created the socket has crashed. I don't know how to do that efficiently, so I punt. The only thing I would suggest in the socket domain is (a) make gethostbyname("cluster") be translated into a getclustbyname("cluster") so that you can think of the cluster as one host (DNS or someone is round robining the host you actually get), and (b) manage the routing tables within the cluster far more dynamically that routing tables are corrently managed. The latter means that you notice immediately when a CPU leaves the cluster and update your routing tables to route around that dead CPU. Cluster {join,leave} This turns out to be a thorny area. You gotta get it right, too. You want the cluster to keep working in the face of a crashed node. You also want nodes to be taken out and added back into the cluster for whatever reasons. There's a whole set of protocol issues here that I'm too sick to describe, trust me that we have a lot of work in this area. SMP vs cluster. Lots of people wonder about this - do you do one, both, neither? The smartest people I know, have all concluded the same thing: you do 4 way SMP nodes, and cluster those to scale beyond the 4 CPUs. The reasoning is as follows: when you are creating processes, you are striping them across the cluster (if you have a coherent distributed mmap, rfork() is not that hard, seems worse than it is, but as a first pass, just do rexec(), that will scale parallel make which is a great test case). It turns out from cache affinity studies that you really want to avoid moving processes from one CPU/cache/memory to another. It screws up your performance. On the other hand, if you get unlucky with your striping alg and land a couple of long running processes on the same node, it is nice to have more than one CPU there to handle the load. Another way to state this: you need to balance your load. If you try and statically balance it at fork and/or exec time, you will make mistakes because you don't have enough info at that point to do perfect scheduling job. If you are sending jobs to SMPs instead of uniprocessers, the SMPs can do a reasonable job of dynamically scheduling the load. And a 4 way SMP is a good first order approximation of an infinitely large SMP, it is rare that you'll screw up so badly that you need more than 4 processors to smooth out the load. So why am I beating on this issue so hard? Because I don't want a fine grained threaded SMP kernel. Threading the kernel that much introduces way too much of a performance penalty for the simple case of "run this one job". Also consider that the SMP kernel may well form the basis for a fully preemptable uniprocessor kernel. I do not want to sacrafice more than 1% performance on the uniprocessor to get preemption. Solaris and IRIX both suck at this - you pay big time for that checklist item. If you walk into the SMP arena with the model that you "fork" your system every 4 processors, then you don't have to work so hard to get scaling. Coarse grained, non intrusive locking will work just fine for 4 processors and you leave the rest to the cluster. Cool? Finally - when doing all of this stuff, please do a 100Mbit ethernet based version as well as the AP version. If you come at it from a network point of view, a whole bunch of problems will _not_ happen in the AP version. When you have all that nice hardware, you tend to use it and it can screw up the architecture such that a network based cluster won't work. On the other hand, if you do a network based cluster, you are guarenteed that you have a partioned solution. As you try and make all of those kernels work on that one big shared memory, you'll find that partitioning is a big performance win. Coming from a network cluster, you'll get that without having to work for it - the other way frequently is harder. That's enough for now, how about some comments? --lm From owner-linux@cthulhu.engr.sgi.com Wed May 15 23:23:37 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA11138; Wed, 15 May 1996 23:23:37 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id GAA20606 for linux-list; Thu, 16 May 1996 06:22:10 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA20601 for ; Wed, 15 May 1996 23:22:09 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA11092 for ; Wed, 15 May 1996 23:22:08 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA20594; Wed, 15 May 1996 23:22:06 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id XAA13123; Wed, 15 May 1996 23:22:04 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id CAA21020; Thu, 16 May 1996 02:21:12 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id CAA10579; Thu, 16 May 1996 02:21:12 -0400 Date: Thu, 16 May 1996 02:21:12 -0400 Message-Id: <199605160621.CAA10579@huahaga.rutgers.edu> From: "David S. Miller" To: nn@lanta.engr.sgi.com CC: sparclinux-cvs@caipfs.rutgers.edu, torvalds@cs.helsinki.fi, lmlinux@neteng.engr.sgi.com In-reply-to: <199605151640.JAA08277@lanta.engr.sgi.com> (nn@lanta.engr.sgi.com) Subject: Re: numbers... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Wed, 15 May 1996 09:40:53 -0700 From: nn@lanta.engr.sgi.com (Neal Nuckolls) > sun4m SS10 115mhz hypersparc, 256k cache > measure_csum_partial > csum_partial: sz[1024] 10000 iterations takes 17009430 microseconds > csum_partial: sz[1024] 1 iteration takes <1700 microseconds>==<332 nanoseconds> Maybe I'm dense this morning but I don't understand the numbers. [NOTE: real lmbench results with the new checksum code in a bit, it's not as much of an improvement as I wanted and Solaris still gets better TCP bandwidth on localhost.] The benchmark looks like: for(iter=0; iter < 10000; iter++) { for(inner=0; inner < 512; inner++) { csum(foo, bar, baz); flush_caches(); } } The 512 number is just imperical because for small buffers (less than 1k) doing just one iteration caused it impossible to measure anything significant. I am factoring in the time the cache flush takes. I calculate how long it takes to do the flush before the loop runs, then subtract that value multiplied by (iter * inner) from the final time. So the 17009430 microseconds is the time it takes to run the entire loop structure minus the flushing overhead. 1700 microseconds is the time each run of the inner for loop took again minus the flush overhead, 332 nanoseconds is the absolute time each instance of the csum() took to run on the buffer once again this is after subtracting the flush overhead. Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Thu May 16 00:04:19 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA12368; Thu, 16 May 1996 00:04:18 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA22629 for linux-list; Thu, 16 May 1996 07:02:54 GMT Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA22622 for ; Thu, 16 May 1996 00:02:53 -0700 Received: from kyoko.mpx.com.au by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id AAA15488; Thu, 16 May 1996 00:02:47 -0700 Received: from gatekeeper.awa.com.au(really [203.10.64.114]) by kyoko.mpx.com.au via smail with smtp id for ; Thu, 16 May 96 17:02:42 +1000 (EST) (/\##/\ Smail3.1.30.13 #30.8 built 5-oct-95) Received: from desertoak.awa.com.au(really [150.207.60.100]) by gatekeeper.awa.com.au via sendmail with esmtp id for ; Sun, 12 May 96 08:56:00 +1000 (AEST) (/\##/\ Smail3.1.30.13 #30.16 built 2-may-96) Received: from cephalotus(really [150.207.24.34]) by desertoak.awa.com.au via sendmail with smtp id for ; Thu, 16 May 96 17:02:38 +1000 (AEST) (/\##/\ Smail3.1.30.13 #30.11 built 8-may-96) Message-Id: Date: Thu, 16 May 96 17:02:38 +1000 (AEST) X-Sender: mbeach@desertoak X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: linux@cthulhu.engr.sgi.com From: Michael Beach Subject: References for MIPS hacking Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hello all. Is anything much happening on this list? I haven't seen any activity for quite a while? A few real questions too... Does this port target the R4000 and up, or is it meant to run on R3000s as well? Also, can anyone point me at the 'canonical reference' for the MIPS processors? Do MIPS publish programmers reference manuals, or do I have to hassle their 'technology partners' ie LSI, IDT etc. Thanks in advance! Regards M.Beach From owner-linux@cthulhu.engr.sgi.com Thu May 16 00:05:53 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA12432; Thu, 16 May 1996 00:05:53 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA22857 for linux-list; Thu, 16 May 1996 07:04:27 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA22842 for ; Thu, 16 May 1996 00:04:24 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA12382 for ; Thu, 16 May 1996 00:04:23 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA22827; Thu, 16 May 1996 00:04:21 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id AAA15579; Thu, 16 May 1996 00:04:19 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id CAA22273; Thu, 16 May 1996 02:53:50 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id CAA12098; Thu, 16 May 1996 02:53:50 -0400 Date: Thu, 16 May 1996 02:53:50 -0400 Message-Id: <199605160653.CAA12098@huahaga.rutgers.edu> From: "David S. Miller" To: lmlinux@neteng.engr.sgi.com CC: torvalds@cs.helsinki.fi, sparclinux-cvs@caipfs.rutgers.edu, alan@cymru.net Subject: lmbench with new checksum code... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk It's not as hot as I wanted it to be, ho hum... Just for flavor I've included numbers for my 115MHZ hypersparc running SunOS so no none forgets that this is all running on a shitty SparcClassic. ;-) I'm probably stalling the chip stupidly in my code or not touching the cache lines in the correct order, ugh this is pissing me off, I'll check it out some more tomorrow when my head doesn't hurt so much... I doubt I can get 2mb/s more out of my code to beat solaris, sigh, where the heck could all this overhead possibly be??? L M B E N C H 1 . 0 S U M M A R Y ------------------------------------ Processor, Processes - times in microseconds -------------------------------------------- Host OS Mhz Null Null Simple /bin/sh Mmap 2-proc 8-proc Syscall Process Process Process lat ctxsw ctxsw --------- ------------- ---- ------- ------- ------- ------- ---- ------ ------ trombetas Linux 1.99.3 50 15 8.8K 40.9K 75K 350 83 100 geneva.ru SunOS 5.5 50 31 33.7K 148.2K 274K 596 174 205 negro.rut SunOS 4.1.3_U 49 124 18.3K 63.9K 110K 470 152 262 huahaga.r SunOS 4.1.4 115 32 10.4K 34.3K 59K 169 96 104 *Local* Communication latencies in microseconds ----------------------------------------------- Host OS Pipe UDP RPC/ TCP RPC/ UDP TCP --------- ------------- ------- ------- ------- ------- ------- trombetas Linux 1.99.3 295 1016 1756 1408 2564 geneva.ru SunOS 5.5 530 1563 2080 1354 2398 negro.rut SunOS 4.1.3_U 890 1375 2287 1573 2804 huahaga.r SunOS 4.1.4 306 616 956 667 1161 *Local* Communication bandwidths in megabytes/second ---------------------------------------------------- Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem reread reread (libc) (hand) read write --------- ------------- ---- ---- ------ ------ ------ ------ ---- ----- trombetas Linux 1.99.3 8 4.8 25.0 17.4 18 24 41 36 geneva.ru SunOS 5.5 8 7.0 12.6 19.5 18 18 40 36 negro.rut SunOS 4.1.3_U 4 2.0 19.5 8.2 18 24 41 36 huahaga.r SunOS 4.1.4 14 5.3 30.2 19.9 20 22 48 37 Memory latencies in nanoseconds (WARNING - may not be correct, check graphs) -------------------------------------------- Host OS Mhz L1 $ L2 $ Main mem TLB Guesses --------- ------------- --- ---- ---- -------- --- ------- trombetas Linux 1.99.3 50 20 170 180 600 No L2 cache? geneva.ru SunOS 5.5 49 - - - - Bad mhz? negro.rut SunOS 4.1.3_U 49 20 175 183 659 No L2 cache? huahaga.r SunOS 4.1.4 115 17 17 510 842 No L1 cache? From owner-linux@cthulhu.engr.sgi.com Thu May 16 02:21:25 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA17152; Thu, 16 May 1996 02:21:25 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id JAA01804 for linux-list; Thu, 16 May 1996 09:20:00 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA01794 for ; Thu, 16 May 1996 02:19:57 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA17105 for ; Thu, 16 May 1996 02:19:57 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA01784; Thu, 16 May 1996 02:19:54 -0700 Received: from snowcrash.cymru.net by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id CAA21099; Thu, 16 May 1996 02:19:50 -0700 Received: (from alan@localhost) by snowcrash.cymru.net (8.7.1/8.7.1) id KAA08950; Thu, 16 May 1996 10:09:19 +0100 From: Alan Cox Message-Id: <199605160909.KAA08950@snowcrash.cymru.net> Subject: Re: mpp kernel interface To: lm@gate1-neteng.engr.sgi.com (Larry McVoy) Date: Thu, 16 May 1996 10:09:17 +0100 (BST) Cc: tridge@cs.anu.edu.au, linux-mc@arvidsjaur.anu.edu.au, Linus.Torvalds@cs.Helsinki.FI, linux@neteng.engr.sgi.com, alan@cymru.net In-Reply-To: <199605152243.PAA19394@neteng.engr.sgi.com> from "Larry McVoy" at May 15, 96 03:43:19 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > : With 30 people now on this list there must be someone else who wants > : to say something ... I've not actually seen anything from the list (should be going to ukuu) > SMP vs cluster? Why vs, why not AND. An SMP box is just a couple of well connected nodes. > The hard one is sockets. I've never seen a good solution to that. > I'll come back to that. First, I want to go through the other ones and > offer suggestions. There are several approaches to this. One is to treat it like a device so you open a socket on a given machine and it like the device doesnt walk. The other is to bend IP mobile to the needs. That would probably want something like an old 486 as a network FEP. > do remote processes. For the PID name space, make pid_t a 32 bit int, > make the top 16 bits the host part, and the bottom 16 bits the pid part. > (We need to come back to the host part when we discuss process migration.) > A host part of "0" means "this host". So a "kill -HUP 1" will always > restart init. We can also do this for devices so you can mknod a printer on a different node. > Devices I sort of punt on. For device access, I would just use the > remote mag tape protocol (or something very, very similar) so that all > of the locking, etc., still works - since you ship all the requests to > the system w/ the device, that kernel can implement the locks. Any > issues here? The vfs issues fairly controlled requests to the FS layer, and the device layer also is fairly clean. The MOSIX project intercepted stuff at this level --- so a remote device turns the request into a message. The system also accounted messages so a process like a find would migrate across cpus as it changed the disk it was searching. > we have the talent right here on this list to do it. So I'll bow out of > commenting on it, other than to say make sure mmap works right. mmap is foul. SYS5 shared memory is just as bad too. > Sockets. This is a hard problem. Some people think that a socket > should stick around after the CPU that created the socket has crashed. If you are having a single apparent IP address this is true for TCP, you can on spotting a down host just send an RST and go into TIME_WAIT to preserve the corruption protection properties of TCP. > is a big performance win. Coming from a network cluster, you'll get that > without having to work for it - the other way frequently is harder. It also means more people can play From owner-linux@cthulhu.engr.sgi.com Thu May 16 02:45:50 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA17955; Thu, 16 May 1996 02:45:50 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id JAA02565 for linux-list; Thu, 16 May 1996 09:44:21 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA02560 for ; Thu, 16 May 1996 02:44:19 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA17903 for ; Thu, 16 May 1996 02:44:18 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA02551 for ; Thu, 16 May 1996 02:44:17 -0700 Received: from snowcrash.cymru.net by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id CAA22098; Thu, 16 May 1996 02:44:14 -0700 Received: (from alan@localhost) by snowcrash.cymru.net (8.7.1/8.7.1) id KAA09812; Thu, 16 May 1996 10:35:05 +0100 From: Alan Cox Message-Id: <199605160935.KAA09812@snowcrash.cymru.net> Subject: Re: lmbench with new checksum code... To: davem@caip.rutgers.edu (David S. Miller) Date: Thu, 16 May 1996 10:35:04 +0100 (BST) Cc: lmlinux@neteng.engr.sgi.com, torvalds@cs.helsinki.fi, sparclinux-cvs@caipfs.rutgers.edu, alan@cymru.net In-Reply-To: <199605160653.CAA12098@huahaga.rutgers.edu> from "David S. Miller" at May 16, 96 02:53:50 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > I doubt I can get 2mb/s more out of my code to beat solaris, sigh, > where the heck could all this overhead possibly be??? What makes you think the Solaris loopback is even doing checksums or a memcpy via kernel space ? They only way you'll beat solaris at the loopback network game is to cheat as they do. Make tcp_connect spot a localhost connection change the socket method to something akin to af_unix but streamlined a bit (only special case is urgent data). Alan From owner-linux@cthulhu.engr.sgi.com Thu May 16 03:10:12 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA18984; Thu, 16 May 1996 03:10:12 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA03443 for linux-list; Thu, 16 May 1996 10:08:46 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA03438 for ; Thu, 16 May 1996 03:08:44 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA18931 for ; Thu, 16 May 1996 03:08:42 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA03430 for ; Thu, 16 May 1996 03:08:41 -0700 Received: from porsta.cs.Helsinki.FI by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id DAA22956; Thu, 16 May 1996 03:08:39 -0700 Received: from linux.cs.Helsinki.FI (linux.cs.Helsinki.FI [128.214.48.39]) by porsta.cs.Helsinki.FI (8.6.10/8.6.9) with SMTP id NAA19285; Thu, 16 May 1996 13:08:28 +0300 Date: Thu, 16 May 1996 13:08:04 +0300 (EET DST) From: Linus Torvalds To: Alan Cox cc: "David S. Miller" , lmlinux@neteng.engr.sgi.com, sparclinux-cvs@caipfs.rutgers.edu Subject: Re: lmbench with new checksum code... In-Reply-To: <199605160935.KAA09812@snowcrash.cymru.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Thu, 16 May 1996, Alan Cox wrote: > > What makes you think the Solaris loopback is even doing checksums or a memcpy > via kernel space ? They only way you'll beat solaris at the loopback network > game is to cheat as they do. Make tcp_connect spot a localhost connection > change the socket method to something akin to af_unix but streamlined a bit > (only special case is urgent data). One day we might actually want to do something like that. No, I'm not suggesting special-casing loopback (we don't need it any more, we're getting good enough performance as-is), but I would suggest that at some point we integrate the networking code a bit tighter in the VFS model of open/close. One problem with the networking code right now is that we can't short-circuit some of the decisions, so we're doing unnecessary run-time checks. This is not really much of a performance problem, I consider it more of a beaty wart right now. For example, when we open a normal pipe (be it unnamed or named), we never go through the filesystem code for that pipe any more - we just make the file operations point directly to the pipe code, and when we read/write to that pipe we don't have any filesystem overhead. In contrast, when we open a network connection, we always go through the network layer, even at run-time. Admittedly there are some reasons for this, but most of them aren't really valid any more. For example, sockets used to really be totally separate entities from inodes, so we couldn't consider sockets to be part of the VFS layer. But that isn't true any more (and hasn't been for a long whole): sockets really _are_ implemented as a part of the inode these days. So a "socket" is really just the network-specific part of an inode (the same way the "normal" filesystems have their own private parts - look at the inode "u" union to see what I mean. However, due to historical reasons, the internal socket routines do not use the VFS "inode" abstraction, but instead they use only the socket sub-part. Sometime in the future I would really like to get rid of that, and make the low-level socket code use the "inode" the same way everybody else does. This is _definitely_ not a huge issue - as I said it's more cleanlyness and encapsulation than performance. It will require making the socket-specific IO operations (recvmsg etc) be first-class members in the VFS layer etc, and in general it requires a lot of minor modifications. Nothing terribly hard (and some things get cleaner thanks to it), but it's a lot of code that has to be worked out. Merging the sockets more tightly into the VFS layer gets rid of the current "struct socket" that we don't really need (as opposed to the "struct sock", which is a different beast altogether) and at least partly the "struct proto_ops" (which would just be part of the "struct file_operations"). We'd get rid of one (slightly confusing) layer of abstraction, and some cases could be streamlined a bit. Finally, let me say again that I don't think we should short-circuit loopback TCP like Solaris does. I used to think it was a nifty feature, but I got better. When I talk about streamlining above, I'm thinking of similar short-circuiting, but on a much smaller scale (getting rid of run-time checks that can be done when the state of the thing changes instead). For an example of what I'm talking about, look at how the tty layer uses the operations pointers to handle hangup etc. It just changes the file operations pointer, which automagically means that the files start behaving differently once they've been hung up (without having the actual routines do any extra "am I hung up" checking). That's the kind of thing that the network layer could do too if it was better integrated with the VFS layer. [ Alan has heard some of this before - I've been talking about these changes for a long time. I've never felt they have been important enough to really do something radical about it, but I still think it's the right thing to do eventually ] Linus From owner-linux@cthulhu.engr.sgi.com Thu May 16 07:22:31 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id HAA26774; Thu, 16 May 1996 07:22:31 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id OAA14020 for linux-list; Thu, 16 May 1996 14:21:06 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id HAA14015 for ; Thu, 16 May 1996 07:21:04 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id HAA26731 for ; Thu, 16 May 1996 07:21:04 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id HAA14001; Thu, 16 May 1996 07:21:01 -0700 Received: from arvidsjaur.anu.edu.au by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id HAA08955; Thu, 16 May 1996 07:20:58 -0700 Received: (from tridge@localhost) by arvidsjaur.anu.edu.au (8.7.3/8.6.9) id AAA24100; Fri, 17 May 1996 00:20:34 +1000 Date: Fri, 17 May 1996 00:20:34 +1000 Message-Id: <199605161420.AAA24100@arvidsjaur.anu.edu.au> From: Andrew Tridgell To: lm@gate1-neteng.engr.sgi.com CC: linux-mc@arvidsjaur.anu.edu.au, Linus.Torvalds@cs.Helsinki.FI, linux@neteng.engr.sgi.com, alan@cymru.net In-reply-to: <199605152243.PAA19394@neteng.engr.sgi.com> (lm@gate1-neteng.engr.sgi.com) Subject: Re: mpp kernel interface Reply-to: Andrew.Tridgell@anu.edu.au Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Larry, I think what you describe is really a blueprint for a "throughput" machine, a machine that gets its parallelism mostly from the fact that you will be running lots of independent jobs on it at once. The alternative is a "parallel" machine, which aims to get optimal performance even when just running one or two programs. For example, a throughput machine is an ideal departmental server. Lots of people doing edits/compiles with some heavy computation thrown in now and then. Its the sort of thing that clusters of workstations normally do. A "parallel" machine is what supercomputer centres often have. They run just one or two jobs at once, but they are big jobs, like climate modelling or fluid dynamics simulations. They use huge amounts of ram (many GB) for the one process and require very tight communications using specialised parallel libraries. Our research group is really centered around parallel systems, with algorithms that scale to thousands of cpus. Unfortunately our budget only stretches to 16 cpus on the AP+ at the moment, but we can also run on much larger systems like we did this week by connecting to the "Parallel Computing Research Facility" at Fujitsu in Japan. This approach has a number of implications: - we're not as worried about the ability to dynamically enter/leave a "cluster". This makes algorithms simpler and faster as they can use data structures that assume that the number of cpus and their layout stays static. - we're not as worried about recovering/continuing if a cpu crashes. If all user jobs are running on all cpus then it doesn't make much sense to try to recover when one goes down, as it kills all user jobs anyway, so you might as well shutdown (crash), replace the part and startup again. Its not as though this is a common experience for us anyway. I don't think we've had a hardware fault on our 128 cpu ap1000 yet, after several years of operation. - we're worried about getting the very best bandwidth/latency out of the communications network, while still providing all the lovely operating system services that Linux provides. - we're worried about providing efficient parallel filesystem, memory and networking abstractions, scalable to lots of processors. > Processes have two major chunks of work, the PID name space and how you > do remote processes. For the PID name space, make pid_t a 32 bit int, > make the top 16 bits the host part, and the bottom 16 bits the pid part. > (We need to come back to the host part when we discuss process migration.) > A host part of "0" means "this host". So a "kill -HUP 1" will always > restart init. ok, this makes sense with what we've done so far, which is really just a tightly integrated network of workstations. I'm not at all sure its what we want in the long term however. It assumes that things like init will be running on every cpu, so that you have to distinguish which copy of init you mean when you send it a signal. I'm hoping that we will eventually have a really "single system image" machine, where only one copy of init is actually running. Most cpus would not be running any system daemons at all, just the necessary kernel threads. Right now we do in fact have one copy of init on each cpu, along with lots of other daemons. We can get away with them all having the same pid because the system isn't really parallel yet, there is no notion of a remote syscall. (we have in fact done a remote signal send operation for parallel programs, but its not as general as a remote kill) > Devices I sort of punt on. For device access, I would just use the > remote mag tape protocol (or something very, very similar) so that all > of the locking, etc., still works - since you ship all the requests to > the system w/ the device, that kernel can implement the locks. Any > issues here? mostly speed issues. Could using something like rmt really scale to lots of processors with reasonable performance? > Files. I have also punted on this. I have never gotten that excited about > a cache coherent distributed file system, though others certainly do. It's > not because I don't think it is useful. I believe it can be done and that > we have the talent right here on this list to do it. So I'll bow out of > commenting on it, other than to say make sure mmap works right. The big problems are indeed cache coherency and things like mmap(). We implemented a parallel filesystem called HiDIOS on the 128 node ap1000 which worked by putting the buffer cache for a block on the cell that owns the block. We didn't support mmap() as the machine had no mmu, and the only cache local to each cpu is an optional one controlled by the user in much the same way as stdio, but applied to file descriptors in the C library. We were able to get away with this because the remote memory access bandwidth was very high (slightly higher in fact than local memory), and latencies were low. We also used a really simple meta data structure that completely elimated indirect blocks to find data on the disk. We got 60MB/sec through the filesystem (the hardware limit is 64MB/sec). We've seen attempts to put standard unix filesystem structures on parallel machines and they are just not efficient enough. The cost of manipulating all that meta data is huge when the disks (in parallel) are capable of higher thoughputs than a local memory copy. We are planning on doing a similar parallel filesystem for Linux/AP+. We'll use a more sophisticated meta data scheme than was used in the AP1000 HiDIOS, but still much simpler than that used in ext2. It will be tuned for big io tasks, like loading 2GB of data before the start of a heavy computing task. It will probably be pathetic for loading your .cshrc, but we aren't going to be encouraging people to use this system to run shell scripts on :-) I still don't know how we are going to handle mmap. We think mmap is very important in a parallel filesystem, but we just don't know how to implement it in a really fast and coherent way yet. > Sockets. This is a hard problem. Some people think that a socket > should stick around after the CPU that created the socket has crashed. yep, sockets are probably hard. We've already met problems with them and we haven't even tried to make them parallel yet :-) We use sockets to implement the stdin/stdout/stderr of parallel processes. The paralleld that launches parallel programs on each cell first creates 3 sockets back to the launching program, setting them up as file desciptors 0, 1 and 2. When it then does a fork()/exec() the parallel program inherits them. The problem is that on a 64 cell machine we end up having 192 sockets connected to the one process on the front end that launched the parallel program. This is madness! It also won't work well if we have 1024 cpus :-) I'm hoping this problem will go away when we revamp the way we launch parallel programs. If we had a remote fork() and/or remote exec() and also had a way for the file descriptors of remote forked processes to feed back into the parent cpu then it would be much better. We'd probably also need to use a tree structure to feed the file descriptors (and paging for that matter) back up into the parent process. 1000 children all writing to one parent would not be pretty. > Cluster {join,leave} This turns out to be a thorny area. You gotta get it > right, too. You want the cluster to keep working in the face of a crashed > node. You also want nodes to be taken out and added back into the cluster > for whatever reasons. There's a whole set of protocol issues here that I'm > too sick to describe, trust me that we have a lot of work in this area. This is a really interesting area to work on, but its probably not something our group will be looking at soon, for the reasons described earlier. We've got to focus our attentions a bit :-) > Finally - when doing all of this stuff, please do a 100Mbit ethernet based > version as well as the AP version. If you come at it from a network point > of view, a whole bunch of problems will _not_ happen in the AP version. > When you have all that nice hardware, you tend to use it and it can > screw up the architecture such that a network based cluster won't work. > On the other hand, if you do a network based cluster, you are guarenteed > that you have a partioned solution. As you try and make all of those > kernels work on that one big shared memory, you'll find that partitioning > is a big performance win. Coming from a network cluster, you'll get that > without having to work for it - the other way frequently is harder. We probably won't do a 100Mbit version ourselves, we just don't have the time. We'd love to cooperate with people that are doing it, however, and I hope that a lot of what we do will be relevant for systems like that. The problem is really latency. Ethernet type systems have latencies which aren't much lower than the system clock tick interval. This means it often makes sense to do things is quite different ways to what we have to do. Cheers, Andrew From owner-linux@cthulhu.engr.sgi.com Thu May 16 09:05:05 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA03283; Thu, 16 May 1996 09:05:04 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA22884 for linux-list; Thu, 16 May 1996 16:03:40 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA22868 for ; Thu, 16 May 1996 09:03:37 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id JAA03193; Thu, 16 May 1996 09:03:36 -0700 Message-Id: <199605161603.JAA03193@neteng.engr.sgi.com> To: "David S. Miller" From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: lmlinux@neteng.engr.sgi.com, torvalds@cs.helsinki.fi, sparclinux-cvs@caipfs.rutgers.edu, alan@cymru.net Subject: Re: lmbench with new checksum code... Date: Thu, 16 May 1996 09:03:36 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : *Local* Communication bandwidths in megabytes/second : ---------------------------------------------------- : Host OS Pipe TCP File Mmap Bcopy Bcopy Mem Mem : reread reread (libc) (hand) read write : --------- ------------- ---- ---- ------ ------ ------ ------ ---- ----- : trombetas Linux 1.99.3 8 4.8 25.0 17.4 18 24 41 36 : geneva.ru SunOS 5.5 8 7.0 12.6 19.5 18 18 40 36 : negro.rut SunOS 4.1.3_U 4 2.0 19.5 8.2 18 24 41 36 THis is sorta weird - why is it that mmap reread is slower than file reread? Do you have a kernel bcopy that is faster than memory read? I think your 4.8MB/sec number is pretty studly. That means you are checksumming 9MB/sec as well as the protocol stack on a system that bcopies at ~20MB/sec. You're already better than 2x the SunOS code. Call it a day, you won. From owner-linux@cthulhu.engr.sgi.com Thu May 16 09:05:29 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA03300; Thu, 16 May 1996 09:05:29 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA23005 for linux-list; Thu, 16 May 1996 16:04:04 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA22994 for ; Thu, 16 May 1996 09:04:03 -0700 Received: from xtp.engr.sgi.com (xtp.engr.sgi.com [150.166.75.34]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA03222 for ; Thu, 16 May 1996 09:04:02 -0700 Received: by xtp.engr.sgi.com (940816.SGI.8.6.9/911001.SGI) id JAA06415; Thu, 16 May 1996 09:04:00 -0700 From: "Greg Chesson" Message-Id: <9605160903.ZM6413@xtp.engr.sgi.com> Date: Thu, 16 May 1996 09:03:58 -0700 In-Reply-To: Linus Torvalds "Re: lmbench with new checksum code..." (May 16, 1:08pm) References: X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: Linus Torvalds , Alan Cox Subject: Re: lmbench with new checksum code... Cc: "David S. Miller" , lmlinux@neteng.engr.sgi.com, sparclinux-cvs@caipfs.rutgers.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk folks have special-cased the loopback driver in the past to improve X performance. g From owner-linux@cthulhu.engr.sgi.com Thu May 16 12:05:09 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id MAA05147; Thu, 16 May 1996 12:05:08 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id TAA22974 for linux-list; Thu, 16 May 1996 19:03:42 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id MAA22942 for ; Thu, 16 May 1996 12:03:39 -0700 Received: from lanta.engr.sgi.com (lanta.engr.sgi.com [192.26.75.15]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id MAA05094 for ; Thu, 16 May 1996 12:03:38 -0700 Received: by lanta.engr.sgi.com (940816.SGI.8.6.9/911001.SGI) id MAA13605; Thu, 16 May 1996 12:03:35 -0700 Date: Thu, 16 May 1996 12:03:35 -0700 From: nn@lanta.engr.sgi.com (Neal Nuckolls) Message-Id: <199605161903.MAA13605@lanta.engr.sgi.com> To: Alan Cox Subject: Re: lmbench with new checksum code... Cc: sparclinux-cvs@caipfs.rutgers.edu, torvalds@cs.helsinki.fi, lmlinux@neteng.engr.sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Alan is right, the Solaris tcp/ip implementation has a special case for loopback which skims just the top of the IP module, no checksum, no copy at that level, large mtu. neal From owner-linux@cthulhu.engr.sgi.com Thu May 16 15:27:34 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA15946; Thu, 16 May 1996 15:27:34 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA29186 for linux-list; Thu, 16 May 1996 22:26:09 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA29178 for ; Thu, 16 May 1996 15:26:08 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA15897 for ; Thu, 16 May 1996 15:26:06 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA29164 for ; Thu, 16 May 1996 15:26:05 -0700 Received: from snowcrash.cymru.net by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id PAA21591; Thu, 16 May 1996 15:25:59 -0700 Received: from lxorguk.ukuu.org.uk (Ulxorguk@localhost) by snowcrash.cymru.net (8.7.1/8.7.1) with UUCP id XAA01922 for neteng.engr.sgi.com!lmlinux; Thu, 16 May 1996 23:12:14 +0100 Received: by lightning.swansea.linux.org.uk (Smail3.1.29.1 #2) id m0uK6ux-0005FbC; Thu, 16 May 96 18:32 BST Message-Id: From: alan@lxorguk.ukuu.org.uk (Alan Cox) Subject: Re: lmbench with new checksum code... To: lm@gate1-neteng.engr.sgi.com (Larry McVoy) Date: Thu, 16 May 1996 18:32:51 +0100 (BST) Cc: davem@caip.rutgers.edu, lmlinux@neteng.engr.sgi.com, torvalds@cs.Helsinki.FI, sparclinux-cvs@caipfs.rutgers.edu, alan@cymru.net In-Reply-To: <199605161603.JAA03193@neteng.engr.sgi.com> from "Larry McVoy" at May 16, 96 09:03:36 am Content-Type: text Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > I think your 4.8MB/sec number is pretty studly. That means you are > checksumming 9MB/sec as well as the protocol stack on a system that Actually the Linux kernel cheats on the receive side of loopback and doesnt checksum. Its too expensive to fiddle around on the send side for that short of doing the whole job and shorting the tcp layer as Solaris seems to. > bcopies at ~20MB/sec. You're already better than 2x the SunOS code. > Call it a day, you won. Na.. We can cut all the checksums, do raw copies with no protocol overhead and possibly later on do user->user copying (with page flips to keep larry happy ;)). I can't see any reason we cannot do about 8-9MB/sec with a bit of extra code and some sneaky tricks. CONFIG_TCP_BENCHMARK_TRICKS anyone ? From owner-linux@cthulhu.engr.sgi.com Thu May 16 15:28:24 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA15968; Thu, 16 May 1996 15:28:23 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA29295 for linux-list; Thu, 16 May 1996 22:26:59 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA29290 for ; Thu, 16 May 1996 15:26:58 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA15928 for ; Thu, 16 May 1996 15:26:57 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA29283 for ; Thu, 16 May 1996 15:26:56 -0700 Received: from snowcrash.cymru.net by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id PAA21745; Thu, 16 May 1996 15:26:49 -0700 Received: from lxorguk.ukuu.org.uk (Ulxorguk@localhost) by snowcrash.cymru.net (8.7.1/8.7.1) with UUCP id XAA01905 for neteng.engr.sgi.com!linux; Thu, 16 May 1996 23:11:50 +0100 Received: by lightning.swansea.linux.org.uk (Smail3.1.29.1 #2) id m0uK6ho-0005FbC; Thu, 16 May 96 18:19 BST Message-Id: From: alan@lxorguk.ukuu.org.uk (Alan Cox) Subject: Re: mpp kernel interface To: Andrew.Tridgell@anu.edu.au Date: Thu, 16 May 1996 18:19:16 +0100 (BST) Cc: lm@gate1-neteng.engr.sgi.com, linux-mc@arvidsjaur.anu.edu.au, Linus.Torvalds@cs.Helsinki.FI, linux@neteng.engr.sgi.com, alan@cymru.net In-Reply-To: <199605161420.AAA24100@arvidsjaur.anu.edu.au> from "Andrew Tridgell" at May 17, 96 00:20:34 am Content-Type: text Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > We use sockets to implement the stdin/stdout/stderr of parallel > processes. The paralleld that launches parallel programs on each cell > first creates 3 sockets back to the launching program, setting them up > as file desciptors 0, 1 and 2. When it then does a fork()/exec() the > parallel program inherits them. Two things strike me here. Firstly if you are doing that kind of output redirection across 192 cells you are going to need 192 logical connections however you do it. Secondly you really want your node end library to be a bit smarter and pass a tty check across the link so you can use tty/pty pairs if the real descriptor is a tty. > parallel programs. If we had a remote fork() and/or remote exec() > and also had a way for the file descriptors of remote forked processes > to feed back into the parent cpu then it would be much better. MOSIX does this by trapping them at the VFS layer. Effectively each inode and file handle has a host field and if the operation is remote you RPC. > We'd probably also need to use a tree structure to feed the file > descriptors (and paging for that matter) back up into the parent > process. 1000 children all writing to one parent would not be pretty. It would be an interesting application of multicast groups to allow the parent to roam as well. With 1000 children thats an even bigger scaling problem, and for sending stuff to a large number of nodes (eg a loosely synchronized SIMD job) its going to be needed. > The problem is really latency. Ethernet type systems have latencies > which aren't much lower than the system clock tick interval. This > means it often makes sense to do things is quite different ways to > what we have to do. Yes. The latency also means that attacking from two other angles is interesting Firstly 10Mbit ethernet - latency is no worse really just we have to be more reluctant to bulk copy data, and also combining it with something like the TTL PAPERS device for the fast sync stuff (its a $60 to build parallel port synchronization system with about a 3uS overhead). Very limited but might solve some of our problems on ethernet linked boxes. Alan From owner-linux@cthulhu.engr.sgi.com Thu May 16 21:01:19 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id VAA23805; Thu, 16 May 1996 21:01:18 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id EAA14641 for linux-list; Fri, 17 May 1996 04:01:14 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id VAA14636 for ; Thu, 16 May 1996 21:01:12 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id VAA23798 for ; Thu, 16 May 1996 21:01:11 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id VAA14628; Thu, 16 May 1996 21:01:10 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id VAA25665; Thu, 16 May 1996 21:01:08 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id AAA20410; Fri, 17 May 1996 00:01:06 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id AAA19770; Fri, 17 May 1996 00:01:05 -0400 Date: Fri, 17 May 1996 00:01:05 -0400 Message-Id: <199605170401.AAA19770@huahaga.rutgers.edu> From: "David S. Miller" To: lm@gate1-neteng.engr.sgi.com CC: lmlinux@neteng.engr.sgi.com, torvalds@cs.helsinki.fi, sparclinux-cvs@caipfs.rutgers.edu, alan@cymru.net In-reply-to: <199605161603.JAA03193@neteng.engr.sgi.com> (lm@gate1-neteng.engr.sgi.com) Subject: Re: lmbench with new checksum code... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) Date: Thu, 16 May 1996 09:03:36 -0700 I think your 4.8MB/sec number is pretty studly. That means you are checksumming 9MB/sec as well as the protocol stack on a system that bcopies at ~20MB/sec. You're already better than 2x the SunOS code. Call it a day, you won. I did not win, this is unacceptable. I am completely convinced based upon the edge I have over Solaris for context switching and general process/trap operations I should be able to match it even with everything going through real networking. Linux + full networking overhead == Solaris memcpy/cow-page overhead I cannot accept this piss poor performance I'm getting, it must be made faster. (Yes, I'm rediculious, Larry will tell you others how I feel that if I am presented with a "next generation" cpu and I cannot get from trap entry to kernel c-code in 12 completely pipelined non-stalling instructions then some hardware engineer has completely wasted his precious time ;-) Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Sat May 18 22:45:33 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA29009; Sat, 18 May 1996 22:45:32 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA16148 for linux-list; Sun, 19 May 1996 05:45:26 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA16130 for ; Sat, 18 May 1996 22:45:24 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA29006 for ; Sat, 18 May 1996 22:45:22 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA16118 for ; Sat, 18 May 1996 22:45:21 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id WAA22054; Sat, 18 May 1996 22:45:20 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id BAA12139; Sun, 19 May 1996 01:45:18 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id BAA21316; Sun, 19 May 1996 01:45:17 -0400 Date: Sun, 19 May 1996 01:45:17 -0400 Message-Id: <199605190545.BAA21316@huahaga.rutgers.edu> From: "David S. Miller" To: ecd@skynet.be CC: lmlinux@neteng.engr.sgi.com, sparclinux-cvs@vger.rutgers.edu, alan@cymru.net, torvalds@cs.helsinki.fi Subject: idea for csum_partial_copy on Viking/MXCC Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk (Note: This is just another one of my crazy ideas, consider this something to do possibly in the future when someone has tons of copious free time. For now I'm going to get the software version working as fast as it can.) (Some background for some of you, Viking/MXCC Sparc has a hardware block copy facility which can copy cache sub-block aligned chunks of ram very quickly.) This is silly, but it would get disgustingly fast numbers. (btw, eddie, still waiting for the memcpy.s of yours so that I can do some testing tonight...) You use the MXCC stream copy stuff if you have a buffer bigger than 256 bytes and you can align it to 32 bytes. The unrolled loops right now look like: ldd [%src + offset + 0x18], %t0; ! multi-cycle cache stall ldd [%src + offset + 0x10], %t2; ! 1 cycle, cache hit ldd [%src + offset + 0x08], %t4; ! 1 cycle, cache hit st %t0, [%dest + offset + 0x18]; ! multi-cycle cache stall addxcc %t0, %accum, %accum; ! 1 cycle, does not pair st %t1, [%dest + offset + 0x1c]; addxcc %t1, %accum, %accum; ! 1 cycle, cache hit st %t2, [%dest + offset + 0x10]; addxcc %t2, %accum, %accum; ! 1 cycle, cache hit ldd [%src + offset + 0x00], %t0; ! 1 cycle, cache hit st %t3, [%dest + offset + 0x14]; ! 1 cycle, cache hit, cannot pair addxcc %t3, %accum, %accum; st %t4, [%dest + offset + 0x08]; ! 1 cycle, cache hit addxcc %t4, %accum, %accum; st %t5, [%dest + offset + 0x0c]; ! 1 cycle, cache hit addxcc %t5, %accum, %accum; st %t0, [%dest + offset + 0x00]; ! 1 cycle, cache hit addxcc %t0, %accum, %accum; st %t1, [%dest + offset + 0x04]; ! 1 cycle, cache hit addxcc %t1, %accum, %accum; ! around 19 clock cycles Bite me, those stores make this stuff impossible to schedule without grabbing a register window which I refuse to do. Ok, on the MXCC you eat some cycles so that you have the registers setup for the source (for the checksum calculations) and the page numbers etc. for the stream operation for the entire chunk being csum/copied. Then it looks like this: st %stream_addr1, [%stream_addr2] ASI_MXCC /* Processor stalls 3 or 4 clocks to get stream operation going. */ ldd [%src + offset + 0x18], %t0; ! cache hit addxcc %t0, %accum, %accum; ! 1 cycle, does pair addxcc %t1, %accum, %accum; ! 1 cycle, no pair ldd [%src + offset + 0x10], %t2; ! cache hit addxcc %t2, %accum, %accum; ! 1 cycle, does pair addxcc %t3, %accum, %accum; ! 1 cycle, no pair ldd [%src + offset + 0x08], %t4; ! cache hit addxcc %t4, %accum, %accum; ! 1 cycle, cache hit addxcc %t5, %accum, %accum; ! 1 cycle, no pair ldd [%src + offset + 0x00], %t0; ! 1 cycle addxcc %t0, %accum, %accum; ! 1 cycle, cache hit addxcc %t1, %accum, %accum; ! 1 cycle, no pair ! around 12 clock cycles MXCC does all those ugly and hard to schedule stores for us ;-) Note that I could probably schedule that new sequence even better. Saving of 7 clock cycles for _every_ 32 byte aligned block we csum, the overhead of setting up for the stream operation is fuzzed away by the fact that we usually run this thing many times in a row (thus the "only do optimization if len >= 256" rule above). Let's assume in such an implementation that we eat around 13 or 14 cycles getting the registers ready for the stream operation. Fine, then after two straight iterations of the above code sequence we are breaking even, we commonly run it many times in a row. Common case for full ethernet frame is that we do 128 bytes at a shot, 11 times. This works out to: (7 clocks saved per iteration * (128 / 32) * 11) - (14 stream-op setup cycles * 11 iterations) == 308 saved cycles - 154 lost cycles == 154 clocks less per csum on ethernet sized packet frame Old code == 846 total cycles for ethernet sized packet frame New code == 692 "" "" We go ~20% faster ;-) A possible issue is overhead of function ptr dereference for the call, but based upon the performance of our dynamic mmu code I doubt it would matter and it would give gcc some dead cycles to fill in the networking code anyways. As noted previously, this would be a "research" venture to see what kind of numbers it would really get. Now that I think about it I would be very leery about putting this into the tree so that we don't hit the sun4d XBUS IOCACHE hardware bug (it is only triggered by MXCC hardware block copy operations and certain types of dma activity with a certain set of bit patterns in the data, nasty bug). For now I'm re-scheduling the software csum/copy code to work as it should (I was hitting the cache in the wrong way I've found from Andy's numbers, fixing this right now). Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon May 20 17:17:32 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA02728; Mon, 20 May 1996 17:17:32 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA07173 for linux-list; Tue, 21 May 1996 00:17:24 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA07156 for ; Mon, 20 May 1996 17:17:23 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA05977 for linux@engr; Mon, 20 May 1996 17:16:59 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199605210016.RAA05977@yon.engr.sgi.com> Subject: Meeting wednesday To: linux@cthulhu.engr.sgi.com Date: Mon, 20 May 1996 17:16:59 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 525 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hi Linuxies As you may know, David Miller's arival is really close now. Larry says this Friday... We reserved Matisse in 9U, for this Wednesday for a one hour meeting. The goal is to try and see what we have ready for David and see how can we improve our preparedness in the last days that remain. David: do you have names for the two hosts by now? Bill: do you have 200MHz CPUs? I understand we were short on our promises to pre-prepare stuff since people were really busy, any good news would be nice. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Mon May 20 22:42:58 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA19515; Mon, 20 May 1996 22:42:58 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA16255 for linux-list; Tue, 21 May 1996 05:42:51 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA16249; Mon, 20 May 1996 22:42:49 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id WAA18921; Mon, 20 May 1996 22:42:49 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id WAA04124; Mon, 20 May 1996 22:42:49 -0700 Date: Mon, 20 May 1996 22:42:49 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199605210542.WAA04124@fir.esd.sgi.com> To: ariel@cthulhu.engr.sgi.com Cc: linux@cthulhu.engr.sgi.com Subject: Re: Meeting wednesday In-Reply-To: <199605210016.RAA05977@yon.engr.sgi.com> References: <199605210016.RAA05977@yon.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ariel Faigon writes: ... > Bill: do you have 200MHz CPUs? ... I don't have the two modules I ordered, because we have a large backlog. I will probably supply something reasonable for the host machine and a 150 MHZ R5000 to put on the target machine, until the modules I ordered show up. From owner-linux@cthulhu.engr.sgi.com Mon May 20 23:25:29 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA19680; Mon, 20 May 1996 23:25:29 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id GAA17803 for linux-list; Tue, 21 May 1996 06:25:25 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA17798 for ; Mon, 20 May 1996 23:25:24 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA06414 for ; Mon, 20 May 1996 23:24:59 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA17794 for ; Mon, 20 May 1996 23:25:22 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) for id XAA03232; Mon, 20 May 1996 23:25:21 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id CAA28911 for ; Tue, 21 May 1996 02:25:20 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id CAA07005; Tue, 21 May 1996 02:25:20 -0400 Date: Tue, 21 May 1996 02:25:20 -0400 Message-Id: <199605210625.CAA07005@huahaga.rutgers.edu> From: "David S. Miller" To: linux@yon.engr.sgi.com Subject: some projections... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Iris SCSI driver: Mildly amusing, once I get the dma stuff straight should be a 3 or 4 day affair to get going in an initial working state. Iris Ethernet driver: Cake walk, 3 nights tops. It seems the HPC drives both of these devices in a similar manner, it also seems that it has little state machines which do things like retransmit collision packets on the SEEQ and various SCSI sequences as well. I need to get it straight in my head where the software driver actually comes into play. I like the HPC dma architecture btw. Console driver: I assume the keyboard/mouse is driven off the Zilog uarts, if so this should be relatively simple as I can adapt most of the code from my Sparc stuff and how I layed that code out. As for the screen I just need to figure out where the frame buffer lives and how to play with the palette registers and I'm set. Also should be cakewalk to do serial console as well. This might be a 4 or 5 day job depending upon how things go initially. So in less than two weeks I could have drivers for all the major devices going already. A large section of my work will be carefully going over the existing code the linux-mips people have and putting together the initial foundation so that I can at least start compiling kernels, then things can run smoothly. Yawn, stretch, more to come... Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon May 20 23:49:58 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA19712; Mon, 20 May 1996 23:49:58 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id GAA18798 for linux-list; Tue, 21 May 1996 06:49:54 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA18793 for ; Mon, 20 May 1996 23:49:53 -0700 Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA06436 for ; Mon, 20 May 1996 23:49:28 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id XAA20269; Mon, 20 May 1996 23:49:51 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id XAA14132; Mon, 20 May 1996 23:49:51 -0700 Date: Mon, 20 May 1996 23:49:51 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199605210649.XAA14132@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@yon.engr.sgi.com Subject: Re: some projections... In-Reply-To: <199605210625.CAA07005@huahaga.rutgers.edu> References: <199605210625.CAA07005@huahaga.rutgers.edu> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: ... > Console driver: I assume the keyboard/mouse is driven off the Zilog > uarts, if so this should be relatively simple as I can > adapt most of the code from my Sparc stuff and how I > layed that code out. As for the screen I just need > to figure out where the frame buffer lives and how to > play with the palette registers and I'm set. Also > should be cakewalk to do serial console as well. This > might be a 4 or 5 day job depending upon how things > go initially. ... The keyboard and mouse, on the Indy and Indigo2, are driven by a PS2-style keyboard and mouse controller. Aside from the different way of addressing the registers, the driver should pretty much be the same as the Linux PS2 keyboard and mouse controller. The frame buffer is not directly addressable. Most operations are performed via commands written to the pixel pipeline, although one can DMA pixels from main memory to the frame buffer. I will arrange for you to talk with the people who do IRIX X and GL for Newport. It will probably be a good idea to boot up on a serial console first, since the graphics interface is a bit more complex than a dumb frame buffer. That is how we usually port IRIX to a new system. Since there are two serial ports, one can run the console on the first port and the remote debugger on the second port, with very little working beside the serial driver and bsaic exception handling (assuming you start by booting using bootp() and the standard PROM). From owner-linux@cthulhu.engr.sgi.com Mon May 20 23:53:05 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA19717; Mon, 20 May 1996 23:53:05 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id GAA18928 for linux-list; Tue, 21 May 1996 06:53:01 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA18923 for ; Mon, 20 May 1996 23:53:00 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA06446 for ; Mon, 20 May 1996 23:52:36 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA18918 for ; Mon, 20 May 1996 23:52:58 -0700 Received: from caipfs.rutgers.edu by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id XAA04842; Mon, 20 May 1996 23:52:56 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id CAA29861; Tue, 21 May 1996 02:52:55 -0400 Received: (davem@localhost) by huahaga.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) id CAA07073; Tue, 21 May 1996 02:52:55 -0400 Date: Tue, 21 May 1996 02:52:55 -0400 Message-Id: <199605210652.CAA07073@huahaga.rutgers.edu> From: "David S. Miller" To: wje@fir.esd.sgi.com CC: linux@yon.engr.sgi.com In-reply-to: <199605210649.XAA14132@fir.esd.sgi.com> (wje@fir.esd.sgi.com) Subject: Re: some projections... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Mon, 20 May 1996 23:49:51 -0700 From: wje@fir.esd.sgi.com (William J. Earl) The keyboard and mouse, on the Indy and Indigo2, are driven by a PS2-style keyboard and mouse controller. Good, thanks. It will probably be a good idea to boot up on a serial console first, since the graphics interface is a bit more complex than a dumb frame buffer. That is how we usually port IRIX to a new system. Good idea, this will be the direction I go in then. Although, I can't wait to have Linux virtual consoles available on an SGI workstation ;-) Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Tue May 21 08:20:37 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id IAA21301; Tue, 21 May 1996 08:20:37 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA17434 for linux-list; Tue, 21 May 1996 15:20:32 GMT Received: from piecomputer.corp.sgi.com (piecomputer.corp.sgi.com [192.102.145.157]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id IAA17426; Tue, 21 May 1996 08:20:31 -0700 Received: by piecomputer.corp.sgi.com (950413.SGI.8.6.12/930416.SGI) id IAA15111; Tue, 21 May 1996 08:20:30 -0700 From: "Bob Mende Pie" Message-Id: <9605210820.ZM15109@piecomputer.corp.sgi.com> Date: Tue, 21 May 1996 08:20:30 -0700 In-Reply-To: ariel@yon.engr.sgi.com (Ariel Faigon) "Meeting wednesday" (May 20, 5:16pm) References: <199605210016.RAA05977@yon.engr.sgi.com> X-URL: http://reality.sgi.com/employees/mende/ X-Mailer: Z-Mail-SGI (3.2S.2 10apr95 MediaMail) To: ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com Subject: Re: Meeting wednesday Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ariel, What time did you schedule the meeting for??? -- /Bob... mende@sgi.com http://reality.sgi.com/mende/ From owner-linux@cthulhu.engr.sgi.com Tue May 21 09:50:13 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA03256; Tue, 21 May 1996 09:50:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA00843 for linux-list; Tue, 21 May 1996 16:50:09 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA00838 for ; Tue, 21 May 1996 09:50:08 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id JAA06906 for linux; Tue, 21 May 1996 09:49:44 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199605211649.JAA06906@yon.engr.sgi.com> Subject: Wednesday meeting To: linux@yon.engr.sgi.com Date: Tue, 21 May 1996 09:49:44 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 173 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Oops sorry, I left the hour out: Linux meeting Matisse Room 9 upper by the kitchen area Wednesday (tomorrow) 1pm to 2pm (David is arriving Friday.) -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Wed May 29 15:00:29 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA01769; Wed, 29 May 1996 15:00:29 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA05014 for linux-list; Wed, 29 May 1996 22:00:22 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA05005 for ; Wed, 29 May 1996 15:00:21 -0700 Received: from lanta.engr.sgi.com (lanta.engr.sgi.com [192.26.75.15]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA01749 for ; Wed, 29 May 1996 15:00:21 -0700 Received: by lanta.engr.sgi.com (940816.SGI.8.6.9/911001.SGI) id OAA09070; Wed, 29 May 1996 14:59:58 -0700 Date: Wed, 29 May 1996 14:59:58 -0700 From: nn@lanta.engr.sgi.com (Neal Nuckolls) Message-Id: <199605292159.OAA09070@lanta.engr.sgi.com> To: torvalds@cs.helsinki.fi, alan@cymru.net Subject: linux needs bsd networking stack Cc: sparclinux-cvs@caipfs.rutgers.edu, lmlinux@neteng.engr.sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Silicon Valley is bubbling with networking startups. Many of these new small companies are designing products based on PC motherboards and doing some sw and/or hw customization to turn them into networking switches, routers, firewalls, etc. Rather than embedding a RTOS, they are choosing a free unix and usually this is FreeBSD since Linux networking is not the de facto BSD stack. The "unique" tcp/ip implementation is a liability to linux. Is anyone working to replace the standard linux stack with port derived from the 4.4BSD code? thanks. neal nuckolls nn@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Wed May 29 15:20:55 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA02708; Wed, 29 May 1996 15:20:54 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA09491 for linux-list; Wed, 29 May 1996 22:20:50 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA09469 for ; Wed, 29 May 1996 15:20:48 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA20059 for linux; Wed, 29 May 1996 15:20:16 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199605292220.PAA20059@yon.engr.sgi.com> Subject: Come say hello to David To: linux@yon.engr.sgi.com Date: Wed, 29 May 1996 15:20:15 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 261 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk For all those who are on the list, haven't met Dave yet, and are in Mountain View. Dave is in Building 9-Upper, North-Western corner, across from Kim Vogt, besides the Schimmels. Please drop by, introduce yourself, see how can you help, etc. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Wed May 29 15:50:31 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA03273; Wed, 29 May 1996 15:50:30 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA13722 for linux-list; Wed, 29 May 1996 22:50:25 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA13701 for ; Wed, 29 May 1996 15:50:24 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA03268; Wed, 29 May 1996 15:50:23 -0700 Date: Wed, 29 May 1996 15:50:23 -0700 Message-Id: <199605292250.PAA03268@neteng.engr.sgi.com> From: "David S. Miller" To: nn@lanta.engr.sgi.com CC: torvalds@cs.helsinki.fi, alan@cymru.net, sparclinux-cvs@caipfs.rutgers.edu, lmlinux@neteng.engr.sgi.com In-reply-to: <199605292159.OAA09070@lanta.engr.sgi.com> (nn@lanta) Subject: Re: linux needs bsd networking stack Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Wed, 29 May 1996 14:59:58 -0700 From: nn@lanta (Neal Nuckolls) The "unique" tcp/ip implementation is a liability to linux. It could also be one of it's greatest assets, and I think this will turn out to be the case. Is anyone working to replace the standard linux stack with port derived from the 4.4BSD code? I will for now only briefly mention why I think this is not very desirable. A couple of weeks ago, Larry was babbling to me "oh the stack is sloowww, I can't push nearly as much over 100mb/s ether as freebsd can, etc." I said, "thats peculiar" so I did some investigation and told Linus about it. Turned out to be a driver bug and after that was fixed the over the wire numbers are unparalleled. The Berkeley stack is dead, but it has one redeeming quality which Linux's stack does desperately need. It has a well defined architecture, I will agree with lm when he mentions that it is a jungle of code to sift through in certain respects. It need a mallet to smooth certain aspects and interfaces out. In the end I think it is best to work on hacking the existing (and upcoming) Linux networking code to have these qualities instead of stuffing the bsd stack into linux (this has been done before a long long time ago btw, before linux had any networking, a man by the name of Charles Hedrick back at Rutgers did it in a few nights). I think the feeling that the linux stack is "hard to follow" or "has very little architecture" has a lot to do with the fact that we don't have 20 books analyzing the code c-statement by c-statement like the bsd stuff does. If we had that, I think this desire to use the berkeley stack would not be as strong. I dislike the berkeley stack, but I am biased in my opinion. I am biased because of the attitude expressed by the people actively working on that code set in the free software world these days, I am also biased because I tend to hack Linux almost exlusively. But, even barring that I believe that some of the elements of the bsd stack will end up being completely flawed when plugged into linux, obvious things like mbufs and other things come to mind right now. It would require a bit of engineering and greatly upset a large community who has put their entire heart and soul into the Linux networking code. I believe at the very least that the Linux networking stack is superior performance wise without any question, and as everyone knows I have numbers to prove it ;-) Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Wed May 29 16:04:45 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA06150; Wed, 29 May 1996 16:04:45 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA16762 for linux-list; Wed, 29 May 1996 23:04:40 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA16744 for ; Wed, 29 May 1996 16:04:38 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id QAA06115; Wed, 29 May 1996 16:04:37 -0700 Message-Id: <199605292304.QAA06115@neteng.engr.sgi.com> To: dm@neteng.engr.sgi.com From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: nn@lanta.engr.sgi.com, torvalds@cs.helsinki.fi, alan@cymru.net, sparclinux-cvs@caipfs.rutgers.edu, lmlinux@neteng.engr.sgi.com Subject: Re: linux needs bsd networking stack Date: Wed, 29 May 1996 16:04:37 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : The "unique" tcp/ip implementation is a liability to linux. : : It could also be one of it's greatest assets, and I think this will : turn out to be the case. : : Is anyone working to replace the standard linux stack : with port derived from the 4.4BSD code? : : A couple of weeks ago, Larry was babbling to me "oh the stack is : sloowww, I can't push nearly as much over 100mb/s ether as freebsd : can, etc." I said, "thats peculiar" so I did some investigation and : told Linus about it. Turned out to be a driver bug and after that was : fixed the over the wire numbers are unparalleled. That's not quite true, I think the BSD numbers are still better, I'll have full lmbench apples to apples runs on the same hardware at the end of this week. : It [bsd] has a well defined architecture, I will agree with lm when he : mentions that it is a jungle of code to sift through in certain : respects. This is one of my complaints. The BSD stack has a defined set of "objects" for dealing with networking; an incomplete list: protocol structure for different address families interface structure for different media types socket structure that cleanly handles different protocols Another big plus of the BSD stack is tcp_input.c and tcp_output.c. These are what most people mean when they say "BSD networking". Downsides of BSD: . I don't particlularly like mbufs; I agree with Linus & Alan that they are overkill. . There are layering "invariants" that affect performance: you really should allocate your send buffers from the interface driver, because it could do some interesting things that would minimize cache flushing. I think Van's prototype did this for witless cards. . Single processor design. This is the biggest drawback, IMO. Proposal/suggestion: . Come up with a strawman proposal for the set of "objects" we think we need in Linux. Do this as part of the work Linus suggested to merge the socket ops with the vfs ops. . Steal the TCP code outright. Nuke the mbuf stuff, use the skbufs or a slightly modified version thereof. . Design in SMP support from the start. This means thinking about thousands of connections running in parallel. : I think the feeling that the linux stack is "hard to follow" or "has : very little architecture" has a lot to do with the fact that we don't : have 20 books analyzing the code c-statement by c-statement like the : bsd stuff does. If we had that, I think this desire to use the : berkeley stack would not be as strong. Yeah, but a very reasonable point is "we don't have that". BSD does. This is a big deal. Documentation is useful. From owner-linux@cthulhu.engr.sgi.com Wed May 29 17:36:27 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA16394; Wed, 29 May 1996 17:36:27 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA03431 for linux-list; Thu, 30 May 1996 00:36:21 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA03420 for ; Wed, 29 May 1996 17:36:20 -0700 Received: from lanta.engr.sgi.com (lanta.engr.sgi.com [192.26.75.15]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA16390; Wed, 29 May 1996 17:36:20 -0700 Received: by lanta.engr.sgi.com (940816.SGI.8.6.9/911001.SGI) id RAA09665; Wed, 29 May 1996 17:36:19 -0700 Date: Wed, 29 May 1996 17:36:19 -0700 From: nn@lanta.engr.sgi.com (Neal Nuckolls) Message-Id: <199605300036.RAA09665@lanta.engr.sgi.com> To: dm@neteng.engr.sgi.com Subject: Re: linux needs bsd networking stack Cc: lmlinux@neteng.engr.sgi.com, sparclinux-cvs@caipfs.rutgers.edu, alan@cymru.net, torvalds@cs.helsinki.fi Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk >> The "unique" tcp/ip implementation is a liability to linux. > > It could also be one of it's greatest assets, and I think this will > turn out to be the case. Whether the linux kernel networking implementation is better or worse than the BSD code isn't my point. The fact that it's not clearly superior, only very different, from the standard is. Most unix and internet R&D community protocol development has been and continues to be within a BSD environment which means that BSD-based kernel networking code is prevalent. If I'm doing some work in this area I can readily grab many free BSD-based protocol pieceparts off the net. New routing protocols, ATM signalling, TCP conjestion improvements, realtime protocol stacks, etc. are all developed in a BSD kernel networking environment. Have been for years. That's not likely to change. There are hundreds of people out there that really know BSD networking. This availability of people and code makes it the standard. Actually, for the startups that I mentioned - those interested in shipping a commercial product - there is no choice, it's FreeBSD, because it comes without the GPL kiss of death. > In the end I think it is best to work on hacking the existing (and > upcoming) Linux networking code to have these qualities instead of > stuffing the bsd stack into linux I think that basing any improvements on a 4.4BSD-based linux stack would result in something more usable. Also, as a side effect, it would encourage more talented networking people to participate and isn't this what freeware is all about? neal From owner-linux@cthulhu.engr.sgi.com Wed May 29 20:02:52 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA07685; Wed, 29 May 1996 20:02:52 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id DAA16701 for linux-list; Thu, 30 May 1996 03:02:47 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA16690 for ; Wed, 29 May 1996 20:02:46 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA07679; Wed, 29 May 1996 20:02:45 -0700 Date: Wed, 29 May 1996 20:02:45 -0700 Message-Id: <199605300302.UAA07679@neteng.engr.sgi.com> From: "David S. Miller" To: nn@lanta.engr.sgi.com CC: lmlinux@neteng.engr.sgi.com, sparclinux-cvs@caipfs.rutgers.edu, alan@cymru.net, torvalds@cs.helsinki.fi In-reply-to: <199605300036.RAA09665@lanta.engr.sgi.com> (nn@lanta) Subject: Re: linux needs bsd networking stack Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Wed, 29 May 1996 17:36:19 -0700 From: nn@lanta (Neal Nuckolls) >> The "unique" tcp/ip implementation is a liability to linux. > > It could also be one of it's greatest assets, and I think this will > turn out to be the case. Most unix and internet R&D community protocol development has been and continues to be within a BSD environment which means that BSD-based kernel networking code is prevalent. If I'm doing some work in this area I can readily grab many free BSD-based protocol pieceparts off the net. New routing protocols, ATM signalling, TCP conjestion improvements, realtime protocol stacks, etc. are all developed in a BSD kernel networking environment. Have been for years. That's not likely to change. There are hundreds of people out there that really know BSD networking. This availability of people and code makes it the standard. Actually, whats funny is that this is exactly what the people doing work on the linux stack have in fact done. Check out the ideas people have put into various berkeley based ventures and research, place our own implementation of the idea into the linux stack, and then improve upon it. The idea behind publicly available standards (at least I believe) was to promote no single entity to have this "defacto" thing which controlled the protocol or what have you, the berkeley phenomenon is not encouraging this idea and is in fact against it. Here the berkeley interpretation and implementation is being considered "the" interpretation and "the" implementation. The Linux code in general moves at an advanced rate, it is constantly evolving and changing for the purposes of improvement. One could argue that this is what makes it so hard to pin down and become very acquainted with it and not just the fact that it's objects and interfaces are not as well defined (as lm mentions, of which I whole heartedly agree, I would some day like to see the Linux networking be as intuitive and seamless as the vm/mm Linux layers, Linus has mentioned moves in this direction via fully integrating the socks more completely into the inode among other things). Actually, for the startups that I mentioned - those interested in shipping a commercial product - there is no choice, it's FreeBSD, because it comes without the GPL kiss of death. I wish it wouldn't come down to a discussion about "what license is better for who and why", I'd rather this be about technical merit. But, I am beginning to realize that this may not be possible. I want Linux to strive and always be on the bleeding edge, as it has been, personally I believe that the "GPL kiss of death" is what makes that possible and will guarentee that this capability cannot be taken away. I think that basing any improvements on a 4.4BSD-based linux stack would result in something more usable. Also, as a side effect, it would encourage more talented networking people to participate and isn't this what freeware is all about? You are correct, this is what "free software" (there is a distinction) is all about. However what it is not about, and what could kill free software is if the "BSD kiss of death" allowed someone to make significant improvements to the Linux code and due to the berkeley license allowed that entity to keep those improvements to themselves so that the free software community loses out. This is precisely what the GPL tries to avoid... Very frequently, Linus himself mentions that the GPL is what has made Linux as powerful as it now is, and he also frequently mentions that GPL'ing the Linux code is the best decision he has ever made. I tend to agree with him. But like I said, I'd rather such a decision be made based upon a technical decision not a "who has the viable licensing terms" decision. It was mentioned that you are more familiar with the berkeley code and many people are. I am more familiar with the Linux code and the work/research which has gone into it, do I have an argument as well? I would not present it this way or drive an argument in that fashion I think. There exists a significant group of people who are in my position and as well there are many in the position you speak of. However, I have been making a significant effort over the past year or so to become familiar with the berkeley code so that I possess the ability to tackle decisions like this based on technical merit, and not turn it into a GPL vs. BSD discussion. Are people supportive of the berkeley side of this argument willing to do the same? I know a few such as lm etc., I would not say they exist within the majority though. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Wed May 29 22:22:26 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA19895; Wed, 29 May 1996 22:22:26 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA27281 for linux-list; Thu, 30 May 1996 05:22:20 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA27276 for ; Wed, 29 May 1996 22:22:19 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA19892 for ; Wed, 29 May 1996 22:22:19 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA27269; Wed, 29 May 1996 22:22:17 -0700 Received: from porsta.cs.Helsinki.FI by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id WAA29720; Wed, 29 May 1996 22:22:14 -0700 Received: from linux.cs.Helsinki.FI (linux.cs.Helsinki.FI [128.214.48.39]) by porsta.cs.Helsinki.FI (8.6.10/8.6.9) with SMTP id IAA26571; Thu, 30 May 1996 08:22:12 +0300 Date: Thu, 30 May 1996 08:21:42 +0300 (EET DST) From: Linus Torvalds To: Neal Nuckolls cc: alan@cymru.net, sparclinux-cvs@caipfs.rutgers.edu, lmlinux@neteng.engr.sgi.com Subject: Re: linux needs bsd networking stack In-Reply-To: <199605292159.OAA09070@lanta.engr.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Wed, 29 May 1996, Neal Nuckolls wrote: > > Silicon Valley is bubbling with networking startups. > Many of these new small companies are designing products > based on PC motherboards and doing some sw and/or hw > customization to turn them into networking switches, > routers, firewalls, etc. Rather than embedding a RTOS, > they are choosing a free unix and usually this is FreeBSD > since Linux networking is not the de facto BSD stack. > The "unique" tcp/ip implementation is a liability to linux. > Is anyone working to replace the standard linux stack > with port derived from the 4.4BSD code? Simple answer: it won't happen. The _only_ advantage of the BSD stack is the de-facto standard thing, and quite frankly that one doesn't make much of a difference - Linux _will_ be the facto standard in one or two more years if everything goes right. Trying to port the BSD stack would be a major mistake, imho. I used to think the BSD stack was an option that we might want to take some day, but I don't think so any more. My main concerns were performance and compatibility, and we've got them both. The problems we still have in networking are not worth worrying about in this context - we'd have a lot more problems if we tried to switch and they wouldn't be any easier to solve. Note that this doesn't mean we shouldn't look at parts of the BSD stack for interesting things (and the BSD stack has obviously been there as a reference). But a whole-sale BSD stack port is not going to happen. Linus From owner-linux@cthulhu.engr.sgi.com Thu May 30 02:49:44 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA26281; Thu, 30 May 1996 02:49:44 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id JAA16929 for linux-list; Thu, 30 May 1996 09:49:38 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA16924 for ; Thu, 30 May 1996 02:49:36 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA26278 for ; Thu, 30 May 1996 02:49:36 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA16917; Thu, 30 May 1996 02:49:34 -0700 Received: from snowcrash.cymru.net by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id CAA16791; Thu, 30 May 1996 02:49:28 -0700 Received: (from alan@localhost) by snowcrash.cymru.net (8.7.1/8.7.1) id KAA23935; Thu, 30 May 1996 10:43:44 +0100 From: Alan Cox Message-Id: <199605300943.KAA23935@snowcrash.cymru.net> Subject: Re: linux needs bsd networking stack To: nn@lanta.engr.sgi.com (Neal Nuckolls) Date: Thu, 30 May 1996 10:43:42 +0100 (BST) Cc: torvalds@cs.helsinki.fi, alan@cymru.net, sparclinux-cvs@caipfs.rutgers.edu, lmlinux@neteng.engr.sgi.com In-Reply-To: <199605292159.OAA09070@lanta.engr.sgi.com> from "Neal Nuckolls" at May 29, 96 02:59:58 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > customization to turn them into networking switches, > routers, firewalls, etc. Rather than embedding a RTOS, > they are choosing a free unix and usually this is FreeBSD > since Linux networking is not the de facto BSD stack. So we should use a defacto BSD stack because its a defacto stack. Ok there is this great OS called windows3. See you later > The "unique" tcp/ip implementation is a liability to linux. I'm not convinced it is. A whole load of SGI people (LM notably) seem intent on "BSD stack, BSD stack, BSD stack". Everyone else I hear is saying "How fast can it go", "How stable can we make it", "Will you please make sure its as solid in 2.0 as in 1.2" > Is anyone working to replace the standard linux stack > with port derived from the 4.4BSD code? No - o The BSD stack doesnt do IPX, AX25, NetROM, Appletalk o There will be no defacto IPv6 for BSD, there are several species o The licensing doesnt permit the two to meet easily o You can't do 400Mbits/second with mbufs so you'd have to break the BSD code anyway Im not convinced about the rest of the argument either. I know one big vendor using the BSD stack for a project. I know several using Linux (Things like the firewall from Mazama). We are seeing primary rate ISDN support for Linux starting to appear, and already have the heavy provider end multiple serial cards. For routers, anyone using a PC style architecture is bounding themselves to small routers anyway. No matter how good the code is you will soon need fancy hardware to handle BGP4, 50,000 routes and fast 100baseT speed switching. And there is no defacto BSD IPv6 Alan From owner-linux@cthulhu.engr.sgi.com Thu May 30 02:50:03 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA26290; Thu, 30 May 1996 02:50:03 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id JAA17002 for linux-list; Thu, 30 May 1996 09:49:59 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA16997 for ; Thu, 30 May 1996 02:49:58 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA26286; Thu, 30 May 1996 02:49:57 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA16992; Thu, 30 May 1996 02:49:56 -0700 Received: from snowcrash.cymru.net by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id CAA16808; Thu, 30 May 1996 02:49:53 -0700 Received: (from alan@localhost) by snowcrash.cymru.net (8.7.1/8.7.1) id KAA24198; Thu, 30 May 1996 10:46:48 +0100 From: Alan Cox Message-Id: <199605300946.KAA24198@snowcrash.cymru.net> Subject: Re: linux needs bsd networking stack To: dm@neteng.engr.sgi.com (David S. Miller) Date: Thu, 30 May 1996 10:46:46 +0100 (BST) Cc: nn@lanta.engr.sgi.com, torvalds@cs.helsinki.fi, alan@cymru.net, sparclinux-cvs@caipfs.rutgers.edu, lmlinux@neteng.engr.sgi.com In-Reply-To: <199605292250.PAA03268@neteng.engr.sgi.com> from "David S. Miller" at May 29, 96 03:50:23 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > It has a well defined architecture, I will agree with lm when he > mentions that it is a jungle of code to sift through in certain > respects. It need a mallet to smooth certain aspects and interfaces > out. I hope to be working full time on this eventually (like when people are paying me for it). I've also started documentation at the driver and skbuff level and will work over it bit by bit - see forthcoming Linux Journal articles then going into the KHG. > their entire heart and soul into the Linux networking code. I believe > at the very least that the Linux networking stack is superior > performance wise without any question, and as everyone knows I have > numbers to prove it ;-) Before you admire the performance numbers get the pre2.1 code off Pedro Roque. Now he has added really neat header prediction code it kicks pre2.0's butt even though its doing a surplus memory alloc we need to tidy up Alan From owner-linux@cthulhu.engr.sgi.com Thu May 30 03:26:35 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA27714; Thu, 30 May 1996 03:26:35 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA19576 for linux-list; Thu, 30 May 1996 10:26:29 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA19571 for ; Thu, 30 May 1996 03:26:28 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA27710; Thu, 30 May 1996 03:26:28 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA19562; Thu, 30 May 1996 03:26:26 -0700 Received: from snowcrash.cymru.net by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id DAA19088; Thu, 30 May 1996 03:26:04 -0700 Received: (from alan@localhost) by snowcrash.cymru.net (8.7.1/8.7.1) id LAA24835; Thu, 30 May 1996 11:12:14 +0100 From: Alan Cox Message-Id: <199605301012.LAA24835@snowcrash.cymru.net> Subject: Re: linux needs bsd networking stack To: nn@lanta.engr.sgi.com (Neal Nuckolls) Date: Thu, 30 May 1996 11:12:12 +0100 (BST) Cc: dm@neteng.engr.sgi.com, lmlinux@neteng.engr.sgi.com, sparclinux-cvs@caipfs.rutgers.edu, alan@cymru.net, torvalds@cs.helsinki.fi In-Reply-To: <199605300036.RAA09665@lanta.engr.sgi.com> from "Neal Nuckolls" at May 29, 96 05:36:19 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > Whether the linux kernel networking implementation is better or > worse than the BSD code isn't my point. The fact that it's not > clearly superior, only very different, from the standard is. Chuckle. The BSD stack doesn't even match the RFC's [ie THE STANDARD] > work in this area I can readily grab many free BSD-based protocol > pieceparts off the net. New routing protocols, ATM signalling, TCP > conjestion improvements, realtime protocol stacks, etc. are all Let me see: Routing protocols is userspace. ATM signalling we have (going in 2.1), Vegas we have in the pre 2.1 stuff. realtime - if you mean low latency then take a look at unet. > Actually, for the startups that I mentioned - those interested in > shipping a commercial product - there is no choice, it's FreeBSD, > because it comes without the GPL kiss of death. So "We should change it for the startups" was message 1. "The startups wont use it was message two". Do you have bullet holes in your shoes by any chance ? > I think that basing any improvements on a 4.4BSD-based linux stack > would result in something more usable. Also, as a side effect, it > would encourage more talented networking people to participate and > isn't this what freeware is all about? We can't use the 4.4BSD stack so that issue is moot. Free software is also about high technical quality. If I wanted to get paid lots of money for hacking kernels I'd go and work for mirkosoft From owner-linux@cthulhu.engr.sgi.com Thu May 30 03:27:05 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA27727; Thu, 30 May 1996 03:27:04 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA19629 for linux-list; Thu, 30 May 1996 10:27:00 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA19624 for ; Thu, 30 May 1996 03:26:59 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA27722; Thu, 30 May 1996 03:26:58 -0700 Received: from sgi.sgi.com (sgi.engr.sgi.com [150.166.76.30]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id DAA19616; Thu, 30 May 1996 03:26:56 -0700 Received: from snowcrash.cymru.net by sgi.sgi.com via ESMTP (950405.SGI.8.6.12/910110.SGI) id DAA19138; Thu, 30 May 1996 03:26:50 -0700 Received: (from alan@localhost) by snowcrash.cymru.net (8.7.1/8.7.1) id LAA24792; Thu, 30 May 1996 11:06:27 +0100 From: Alan Cox Message-Id: <199605301006.LAA24792@snowcrash.cymru.net> Subject: Re: linux needs bsd networking stack To: lm@gate1-neteng.engr.sgi.com (Larry McVoy) Date: Thu, 30 May 1996 11:06:25 +0100 (BST) Cc: dm@neteng.engr.sgi.com, nn@lanta.engr.sgi.com, torvalds@cs.helsinki.fi, alan@cymru.net, sparclinux-cvs@caipfs.rutgers.edu, lmlinux@neteng.engr.sgi.com In-Reply-To: <199605292304.QAA06115@neteng.engr.sgi.com> from "Larry McVoy" at May 29, 96 04:04:37 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > This is one of my complaints. The BSD stack has a defined set of "objects" > for dealing with networking; an incomplete list: > > protocol structure for different address families We have these. > interface structure for different media types We have these > socket structure that cleanly handles different protocols We have most of this. > Another big plus of the BSD stack is tcp_input.c and tcp_output.c. These > are what most people mean when they say "BSD networking". Yep. For 2.0 we have all the core stuff. For pre 2.1 we have stuff going beyond what BSD is doing - Vegas flow control. If you want to work on stealing and working stuff in talk with Pedro Roque, get pre 2.1 and take a good look. > . There are layering "invariants" that affect performance: you really > should allocate your send buffers from the interface driver, because > it could do some interesting things that would minimize cache flushing. > I think Van's prototype did this for witless cards. We could certainly add the allocate via device at very little cost. We just start using dev->kmalloc(). Note that you can't always win on this a packet may change route. > . Single processor design. This is the biggest drawback, IMO. The Linux one is semi designed for MP work. A given socket can do its own locking, and there are only a small number of areas of overlap at the moment. Notably Demultiplex table needs locks Multiple processor writes in parallel/reads in parallel on datagram requires about 10 lines of lock code. We dont run the net_bh() in parallel although most of it we can do very easily. > Proposal/suggestion: > . Come up with a strawman proposal for the set of "objects" we think > we need in Linux. Do this as part of the work Linus suggested to > merge the socket ops with the vfs ops. That certainly cant be counter-productive. > . Steal the TCP code outright. Nuke the mbuf stuff, use the skbufs > or a slightly modified version thereof. We can't steal it outright. 4.4BSD has abominable problems as is. The FreeBSD people have the worst of them fixed but don't have stuff like Vegas and have all the horrible spoofing problems caused by bad timers. > . Design in SMP support from the start. This means thinking about > thousands of connections running in parallel. So long as it still runs very fast for the 99.99% of people with a single CPU 486 PC. Thats the primary target by market volume. > : have 20 books analyzing the code c-statement by c-statement like the > : bsd stuff does. If we had that, I think this desire to use the > : berkeley stack would not be as strong. > Yeah, but a very reasonable point is "we don't have that". BSD does. > This is a big deal. Documentation is useful. Its coming. In fact AW should now have released an English language version of the 1.2 kernel programming book. Alan From owner-linux@cthulhu.engr.sgi.com Thu May 30 11:21:36 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA08947; Thu, 30 May 1996 11:21:35 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA14111 for linux-list; Thu, 30 May 1996 18:21:30 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA14094 for ; Thu, 30 May 1996 11:21:27 -0700 Received: from refugee.engr.sgi.com (refugee.engr.sgi.com [150.166.61.22]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA08942; Thu, 30 May 1996 11:21:27 -0700 Received: from refugee.engr.sgi.com by refugee.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id LAA13683; Thu, 30 May 1996 11:17:21 -0700 Message-Id: <199605301817.LAA13683@refugee.engr.sgi.com> X-Mailer: exmh version 1.6.7 5/3/96 To: Alan Cox Cc: lm@gate1-neteng.engr.sgi.com (Larry McVoy), dm@neteng.engr.sgi.com, nn@lanta.engr.sgi.com, torvalds@cs.helsinki.fi, sparclinux-cvs@caipfs.rutgers.edu, lmlinux@neteng.engr.sgi.com Subject: Re: linux needs bsd networking stack In-reply-to: Message from alan@cymru.net of 30 May 1996 11:06:25 BST Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 May 1996 11:17:21 -0700 From: Steve Alexander Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Alan Cox writes: >We can't steal it outright. 4.4BSD has abominable problems as is. The FreeBSD >people >have the worst of them fixed but don't have stuff like Vegas and have all the >horrible spoofing problems caused by bad timers. I'm not sure I understand what that means, but I'm pretty sure that Vegas is not universally agreed to be a good idea, unless I've missed a meeting. Just to set the record straight, there are people at SGI who don't like either the BSD or Linux stacks ;->. The one thing that I will say about the Linux stack is that it is evolving much more rapidly than any of the public BSD versions are (I spent some time porting aliases forward from one version to another for a friend, and the improvements between versions were amazing), so at some point it will probably win on functionality. -- Steve From owner-linux@cthulhu.engr.sgi.com Sat Jun 1 19:12:14 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA15566; Sat, 1 Jun 1996 19:12:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id CAA12384 for linux-list; Sun, 2 Jun 1996 02:12:04 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA12379 for ; Sat, 1 Jun 1996 19:12:02 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id TAA15557; Sat, 1 Jun 1996 19:12:02 -0700 Date: Sat, 1 Jun 1996 19:12:02 -0700 Message-Id: <199606020212.TAA15557@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: progress, finally... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ok, I have a complete compilation environment that seems to work quite well. All the tools are GNU, I have gcc/ld/as/etc. setups which can create either big or little endian kernels in either ELF or ECOFF format. The target format is that used by the existing Linux/MIPS people. These tools have been linking kernels for two days, I finally got a big endian kernel that sash would eat and it went fine until it tried to look for DECstation devices as that is one of the only machine types the existing Linux/MIPS kernels support (splat!). ;-) For now I'm going to hack the ARC prom code and the SCSI driver in parallel and see how far I can get it booting, more to come. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sat Jun 1 20:36:29 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA20653; Sat, 1 Jun 1996 20:36:29 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id DAA22246 for linux-list; Sun, 2 Jun 1996 03:36:25 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA22241 for ; Sat, 1 Jun 1996 20:36:23 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA24950; Sat, 1 Jun 1996 20:35:48 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606020335.UAA24950@yon.engr.sgi.com> Subject: Re: progress, finally... To: dm@neteng.engr.sgi.com (David S. Miller) Date: Sat, 1 Jun 1996 20:35:47 -0700 (PDT) Cc: linux@cthulhu.engr.sgi.com In-Reply-To: <199606020212.TAA15557@neteng.engr.sgi.com> from "David S. Miller" at Jun 1, 96 07:12:02 pm Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1048 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David, This is very impressive progress. Thanks for the update! I understand you have the prom pointers. A few that _may_ be relevant are in: http://info.engr.sgi.com/~ariel/linux/port.html This doc was put together in a rush, any suggestions, requests for additions etc. would be welcome. > > >Ok, I have a complete compilation environment that seems to work quite >well. > >All the tools are GNU, I have gcc/ld/as/etc. setups which can create >either big or little endian kernels in either ELF or ECOFF format. >The target format is that used by the existing Linux/MIPS people. > >These tools have been linking kernels for two days, I finally got a >big endian kernel that sash would eat and it went fine until it tried >to look for DECstation devices as that is one of the only machine >types the existing Linux/MIPS kernels support (splat!). ;-) > >For now I'm going to hack the ARC prom code and the SCSI driver in >parallel and see how far I can get it booting, more to come. > >Later, >David S. Miller >dm@sgi.com > -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Sat Jun 1 20:47:02 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA02822; Sat, 1 Jun 1996 20:47:02 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id DAA22797 for linux-list; Sun, 2 Jun 1996 03:46:56 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA22786 for ; Sat, 1 Jun 1996 20:46:54 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA02817; Sat, 1 Jun 1996 20:46:54 -0700 Date: Sat, 1 Jun 1996 20:46:54 -0700 Message-Id: <199606020346.UAA02817@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: question Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I understand what all the IP?? things are, but what is the IO4? Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sun Jun 2 15:44:21 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA09646; Sun, 2 Jun 1996 15:44:20 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA15124 for linux-list; Sun, 2 Jun 1996 22:44:17 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA15118 for ; Sun, 2 Jun 1996 15:44:15 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id PAA08072; Sun, 2 Jun 1996 15:44:15 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id PAA29455; Sun, 2 Jun 1996 15:44:13 -0700 Date: Sun, 2 Jun 1996 15:44:13 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606022244.PAA29455@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@cthulhu.engr.sgi.com Subject: Re: question In-Reply-To: <199606020346.UAA02817@neteng.engr.sgi.com> References: <199606020346.UAA02817@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > > I understand what all the IP?? things are, but what is the IO4? IO4 is part of the I/O system on Challenge L and XL ("Everest", "IP19") systems. From owner-linux@cthulhu.engr.sgi.com Mon Jun 3 11:09:11 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA06419; Mon, 3 Jun 1996 11:09:11 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA27254 for linux-list; Mon, 3 Jun 1996 17:12:28 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA27240 for ; Mon, 3 Jun 1996 10:12:26 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) for <@ares.esd.sgi.com:linux@engr.sgi.com> id KAA13259; Mon, 3 Jun 1996 10:12:22 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id KAA17639; Mon, 3 Jun 1996 10:12:20 -0700 Date: Mon, 3 Jun 1996 10:12:20 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606031712.KAA17639@fir.esd.sgi.com> To: linux@cthulhu.engr.sgi.com Subject: mtc0/eret hazard for the R4600, R4700, and R5000 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk We recently noticed an error in the CP0 hazard table for the above processors. Specifically, the eret row in the table in Appendix F is incorrect. There must be two instructions between an mtc0 which changes a register read by eret and an eret, not just one. This is not normally a problem, but it does mean that one must keep the mtc0 which restores $epc far enough away from the eret. From owner-linux@cthulhu.engr.sgi.com Mon Jun 3 11:35:14 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA07273; Mon, 3 Jun 1996 11:35:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA04395 for linux-list; Mon, 3 Jun 1996 17:46:31 GMT Received: from heaven.newport.sgi.com (heaven.newport.sgi.com [169.238.102.134]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA04385 for ; Mon, 3 Jun 1996 10:46:29 -0700 Received: by heaven.newport.sgi.com (940816.SGI.8.6.9/940406.SGI) id KAA06440; Mon, 3 Jun 1996 10:46:27 -0700 From: "Christopher W. Carlson" Message-Id: <9606031046.ZM6438@heaven.newport.sgi.com> Date: Mon, 3 Jun 1996 10:46:26 -0700 In-Reply-To: "David S. Miller" "question" (Jun 1, 8:46pm) References: <199606020346.UAA02817@neteng.engr.sgi.com> X-Mailer: Z-Mail-SGI (3.2S.2 10apr95 MediaMail) To: "David S. Miller" , linux@cthulhu.engr.sgi.com Subject: Re: question Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Jun 1, 8:46pm, David S. Miller wrote: > Subject: question > > I understand what all the IP?? things are, but what is the IO4? > > Later, > David S. Miller > dm@sgi.com >-- End of excerpt from David S. Miller David, For future reference, you might want to check out http://www.asd.sgi.com/bbon/, which is the SGI Big Book Of Names - definitions for all of our acronyms. -- Chris Carlson +------------------------------------------------------+ | Also, carlson@sgi.com | | Work: (714) 756-5976 SGI vmail: x5-8095 | | FAX: (714) 833-9503 | +------------------------------------------------------+ From owner-linux@cthulhu.engr.sgi.com Mon Jun 3 18:03:50 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA21285; Mon, 3 Jun 1996 18:03:49 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA24937 for linux-list; Tue, 4 Jun 1996 01:02:55 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA24926 for ; Mon, 3 Jun 1996 18:02:54 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA21209; Mon, 3 Jun 1996 18:02:54 -0700 Date: Mon, 3 Jun 1996 18:02:54 -0700 Message-Id: <199606040102.SAA21209@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: more progress Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I have my ARCS firmware library code in the kernel to the point where it can do console I/O. Right now the kernel loads from sash and prints the SGI ARCS library version and revision numbers then spins in an endless loop so that it cannot cause any more trouble. ;-) I plan on continuing the ARCS library support code, specifically the code to probe for the physical memory layout of the machine which the rest of the kernel startup code needs anyway, then the device tree manipulation and probing mechanisms as well. Next I will look into getting the kgdb code functioning. And after that I will most likely try to get the generic kernel init'ing such that all the generic data structures and non-device code are setup and the kernel attempts to mount root (which it will not be able to). ;) In parallel I will begin to write the HPC? support, specifically the dma interface code. I will as well be looking into the drivers for scsi, ethernet and graphics console at the same time, coding what I can. Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 3 20:15:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA25344; Mon, 3 Jun 1996 20:15:16 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id DAA14786 for linux-list; Tue, 4 Jun 1996 03:14:30 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA14781 for ; Mon, 3 Jun 1996 20:14:27 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA25310; Mon, 3 Jun 1996 20:14:26 -0700 Date: Mon, 3 Jun 1996 20:14:26 -0700 Message-Id: <199606040314.UAA25310@neteng.engr.sgi.com> From: "David S. Miller" To: carlson@heaven.newport.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <9606031046.ZM6438@heaven.newport.sgi.com> (carlson@heaven.newport.sgi.com) Subject: Re: question Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: "Christopher W. Carlson" Date: Mon, 3 Jun 1996 10:46:26 -0700 For future reference, you might want to check out http://www.asd.sgi.com/bbon/, which is the SGI Big Book Of Names - definitions for all of our acronyms. Thanks. Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 3 22:04:34 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA28837; Mon, 3 Jun 1996 22:04:34 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA24795 for linux-list; Tue, 4 Jun 1996 05:03:56 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA24790 for ; Mon, 3 Jun 1996 22:03:54 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA28754; Mon, 3 Jun 1996 22:03:54 -0700 Date: Mon, 3 Jun 1996 22:03:54 -0700 Message-Id: <199606040503.WAA28754@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: CVS commit mailing list? Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk If anyone wants to keep close track of my progress I could point the CVS commit messages at a generic mailing list so that everyone on this who wants to could see them. Would someone like to set this up? Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Jun 4 00:47:20 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA09919; Tue, 4 Jun 1996 00:47:20 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA09731 for linux-list; Tue, 4 Jun 1996 07:47:11 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA09726 for ; Tue, 4 Jun 1996 00:47:10 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA28057 for linux@engr; Tue, 4 Jun 1996 00:46:32 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606040746.AAA28057@yon.engr.sgi.com> Subject: Re: CVS commit mailing list? To: linux@cthulhu.engr.sgi.com Date: Tue, 4 Jun 1996 00:46:32 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 853 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk If anyone on the linux@engr list is _not_ interested in these CVS commit auto reports, let me know and I'll ask majordomo-owner to create a separate: linux-progress@engr majordomo list. Until we see objections/too-much-traffic, I think Dave can go ahead and auto-mail the reports to linux@engr Personally, I think I'll find these interesting. Anyone? > >I wouldn't mind if you just pointed it at linux@engr (i.e., this list). >Anyone else? > >--lm >--- >Larry McVoy lm@sgi.com http://reality.sgi.com/lm (415) 933-1804 >Copyright 1996, all rights reserved. Microsoft Network is prohibited from >redistributing this work in any form, in whole or in part without license. >License to distribute this work is available to Microsoft at $500. >Transmission without permission constitutes an agreement to these terms. > -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Jun 4 04:55:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA14358; Tue, 4 Jun 1996 04:55:16 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id LAA26107 for linux-list; Tue, 4 Jun 1996 11:55:02 GMT Received: from beyond.clubfed.sgi.com (beyond.clubfed.sgi.com [169.238.1.2]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA26101; Tue, 4 Jun 1996 04:54:58 -0700 Received: from trinbago.clubfed.sgi.com by beyond.clubfed.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/911001.SGI) id HAA21084; Tue, 4 Jun 1996 07:47:03 -0400 Received: by trinbago.clubfed.sgi.com (940816.SGI.8.6.9/940406.SGI.AUTO) id IAA03426; Tue, 4 Jun 1996 08:16:06 -0400 From: "Kwesi Ames" Message-Id: <9606040815.ZM3424@trinbago.clubfed.sgi.com> Date: Tue, 4 Jun 1996 08:15:54 -0400 In-Reply-To: ariel@yon.engr.sgi.com (Ariel Faigon) "Re: CVS commit mailing list?" (Jun 4, 12:46am) References: <199606040746.AAA28057@yon.engr.sgi.com> X-Face: +g~UQT+z9(^"0C`fv,%E,C6_Oe)WXTlrohR/DaIIi.M1K4Q.Lov?w.b5_9)7ttP:DT)a})( Q*I&N#UNe$Tnxu^U!'P8-AbGqCG,y;#j4iO;rkEr`^$o7DmAqm5?uU8@'w88/iSrC-{4,a423@pN,7x&P7n=2@Y8{ X-Mailer: Z-Mail-SGI (3.2S.1 10apr95 MediaMail) To: ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com Subject: Re: CVS commit mailing list? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk [snip] > > Until we see objections/too-much-traffic, I think Dave can > go ahead and auto-mail the reports to linux@engr > > Personally, I think I'll find these interesting. I too find them interesting. -Kwesi > > Anyone? > > > > >I wouldn't mind if you just pointed it at linux@engr (i.e., this list). > >Anyone else? > > [chomp] -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kwesi O. Ames Systems Engineering Support Silicon Graphics Inc. koa@sgi.com "I was one in a MILLON" corp voicemail (800) 326-1020 ext. 5-8713 phone (301) 572-3255 fax (301) 572-3280 http://reality.sgi.com/koa ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-linux@cthulhu.engr.sgi.com Tue Jun 4 09:18:26 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA22705; Tue, 4 Jun 1996 09:18:26 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA20279 for linux-list; Tue, 4 Jun 1996 16:18:17 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA20273; Tue, 4 Jun 1996 09:18:15 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id JAA15037; Tue, 4 Jun 1996 09:18:14 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id JAA15088; Tue, 4 Jun 1996 09:18:04 -0700 Date: Tue, 4 Jun 1996 09:18:04 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606041618.JAA15088@fir.esd.sgi.com> To: ariel@cthulhu.engr.sgi.com Cc: linux@cthulhu.engr.sgi.com Subject: Re: CVS commit mailing list? In-Reply-To: <199606040746.AAA28057@yon.engr.sgi.com> References: <199606040746.AAA28057@yon.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ariel Faigon writes: > > If anyone on the linux@engr list is _not_ interested in these > CVS commit auto reports, let me know and I'll ask majordomo-owner > to create a separate: > > linux-progress@engr > > majordomo list. > > Until we see objections/too-much-traffic, I think Dave can > go ahead and auto-mail the reports to linux@engr > > Personally, I think I'll find these interesting. ... I am interested too, but I would rather have two lists, just as we normally do for regular development (sgi.bugs.xxx for bug reports and checkins about xxx, sgi.engr.xxx for general discussion about xxx). Why don't you set up linux-progress as a clone of linux to start, and people who tire of the reports can unsubscribe from the linux-progress. Having a separate list will also make a little easier to search the archives later on. From owner-linux@cthulhu.engr.sgi.com Tue Jun 4 10:07:31 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA01316; Tue, 4 Jun 1996 10:07:30 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA17723 for linux-list; Tue, 4 Jun 1996 15:52:04 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id IAA17716 for ; Tue, 4 Jun 1996 08:52:03 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id IAA13771; Tue, 4 Jun 1996 08:52:02 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id IAA14993; Tue, 4 Jun 1996 08:51:52 -0700 Date: Tue, 4 Jun 1996 08:51:52 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606041551.IAA14993@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@cthulhu.engr.sgi.com, mani@fir.esd.sgi.com Subject: Re: more progress In-Reply-To: <199606040102.SAA21209@neteng.engr.sgi.com> References: <199606040102.SAA21209@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: ... > Next I will look into getting the kgdb code functioning. And after > that I will most likely try to get the generic kernel init'ing such > that all the generic data structures and non-device code are setup and > the kernel attempts to mount root (which it will not be able to). ;) ... Please check with Mani Varadarajan (mani@esd.sgi.com) about kgdb. He has used it with the DMS Moosehead system simulator, although in that case the simulator acts as the target system monitor, instead of having a program resident in memory with the kernel. I don't know if he had to fix anything for the MIPS architecture; if he did, that might save you some startup time. From owner-linux@cthulhu.engr.sgi.com Tue Jun 4 11:30:01 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA04250; Tue, 4 Jun 1996 11:30:01 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA28851 for linux-list; Tue, 4 Jun 1996 17:17:26 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA28835; Tue, 4 Jun 1996 10:17:22 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA28670; Tue, 4 Jun 1996 10:16:42 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606041716.KAA28670@yon.engr.sgi.com> Subject: Re: CVS commit mailing list? To: wje@fir.esd.sgi.com (William J. Earl) Date: Tue, 4 Jun 1996 10:16:42 -0700 (PDT) Cc: ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com In-Reply-To: <199606041618.JAA15088@fir.esd.sgi.com> from "William J. Earl" at Jun 4, 96 09:18:04 am Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1077 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk OK, I requested linux-progress to be created on majordomo@engr. I guess it'll take some time till someone gets time to set this up, I'll let you know when it is ready. > >Ariel Faigon writes: > > > > If anyone on the linux@engr list is _not_ interested in these > > CVS commit auto reports, let me know and I'll ask majordomo-owner > > to create a separate: > > > > linux-progress@engr > > > > majordomo list. > > > > Until we see objections/too-much-traffic, I think Dave can > > go ahead and auto-mail the reports to linux@engr > > > > Personally, I think I'll find these interesting. >... > > I am interested too, but I would rather have two lists, just as >we normally do for regular development (sgi.bugs.xxx for bug reports and >checkins about xxx, sgi.engr.xxx for general discussion about xxx). >Why don't you set up linux-progress as a clone of linux to start, and >people who tire of the reports can unsubscribe from the linux-progress. >Having a separate list will also make a little easier to search the >archives later on. > -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Jun 4 23:42:45 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA10325; Tue, 4 Jun 1996 23:42:44 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id GAA01954 for linux-list; Wed, 5 Jun 1996 06:42:05 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA01947; Tue, 4 Jun 1996 23:42:04 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA10272; Tue, 4 Jun 1996 23:42:00 -0700 Date: Tue, 4 Jun 1996 23:42:00 -0700 Message-Id: <199606050642.XAA10272@neteng.engr.sgi.com> From: "David S. Miller" To: ariel@cthulhu.engr.sgi.com CC: wje@fir.esd.sgi.com, ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com In-reply-to: <199606041716.KAA28670@yon.engr.sgi.com> (ariel@yon) Subject: Re: CVS commit mailing list? Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: ariel@yon (Ariel Faigon) Date: Tue, 4 Jun 1996 10:16:42 -0700 (PDT) OK, I requested linux-progress to be created on majordomo@engr. I guess it'll take some time till someone gets time to set this up, I'll let you know when it is ready. When you tell me it is up I will point the CVS commit mails at it, thanks Ariel. Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 00:00:14 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA11072; Wed, 5 Jun 1996 00:00:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id GAA03336 for linux-list; Wed, 5 Jun 1996 06:59:38 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA03324 for ; Tue, 4 Jun 1996 23:59:37 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA11058; Tue, 4 Jun 1996 23:59:36 -0700 Date: Tue, 4 Jun 1996 23:59:36 -0700 Message-Id: <199606050659.XAA11058@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: [ariel@yon: linux-progress is allive] Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk ------- Start of forwarded message ------- From: ariel@yon (Ariel Faigon) Subject: linux-progress is allive To: dm@yon (David S. Miller) Date: Tue, 4 Jun 1996 23:53:38 -0700 (PDT) Reply-To: ariel@engr.sgi.com Organization: Silicon Graphics Inc. MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 545 David, could you forward this to 'linux' Majordomo@engr doesn't seem to like me, it keeps bouncing back when I mail this to linux... - ----- Forwarded message from owner-linux@cthulhu ----- The linux-progress list is now set up. My list descriptions somehow evaporated, but this is not important. Feel free to subscribe. To: majordomo@engr.sgi.com subscribe linux-progress David: you may point your CVS commit automailer to it: linux-progress@engr.sgi.com - -- Peace, Ariel - ----- End of forwarded message from owner-linux@cthulhu ----- ------- End of forwarded message ------- From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 00:12:53 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA11479; Wed, 5 Jun 1996 00:12:52 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA05405 for linux-list; Wed, 5 Jun 1996 07:12:18 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA05400 for ; Wed, 5 Jun 1996 00:12:16 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA11472; Wed, 5 Jun 1996 00:12:16 -0700 Date: Wed, 5 Jun 1996 00:12:16 -0700 Message-Id: <199606050712.AAA11472@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: netbooting Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk How much pain is involved in netbooting a kernel from an INDY? Can I just setup a /tftpboot area with the appropriate files and setup a place to place the kernels for the bootloader to find and it'll work? If so, can someone tell me what the necessary magic is that needs to be done? This would speed up my development tremendously ;) Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 00:34:07 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA12214; Wed, 5 Jun 1996 00:34:06 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA08448 for linux-list; Wed, 5 Jun 1996 07:33:37 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA08443 for ; Wed, 5 Jun 1996 00:33:35 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA12209; Wed, 5 Jun 1996 00:33:35 -0700 Date: Wed, 5 Jun 1996 00:33:35 -0700 Message-Id: <199606050733.AAA12209@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: confuscious say... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk "Young grasshopper be very very careful when poking MC memory controller registers you may hose machine to irrecoverable state..." Indeed, even the power switch was useless hehehe... Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 13:49:12 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA03571; Wed, 5 Jun 1996 13:49:12 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA23460 for linux-list; Wed, 5 Jun 1996 18:42:37 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA23448 for ; Wed, 5 Jun 1996 11:42:35 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id LAA18157; Wed, 5 Jun 1996 11:35:29 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id LAA11745; Wed, 5 Jun 1996 11:35:26 -0700 Date: Wed, 5 Jun 1996 11:35:26 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606051835.LAA11745@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@cthulhu.engr.sgi.com Subject: Re: netbooting In-Reply-To: <199606050712.AAA11472@neteng.engr.sgi.com> References: <199606050712.AAA11472@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > > How much pain is involved in netbooting a kernel from an INDY? Can I > just setup a /tftpboot area with the appropriate files and setup a > place to place the kernels for the bootloader to find and it'll work? > If so, can someone tell me what the necessary magic is that needs to > be done? It is easy. On your host system, either put the kernel you want to boot in /usr/local/boot/., or, in /etc/inetd.conf on your host system, add a "-f" to the end of the line and "killall -HUP inetd" (to get inetd to re-read /etc/inetd.conf). Then, on the target system, first set the "netaddr" PROM environment variable. It should be set to the IP address (dotted notation) of the target system. Check it with the "printenv" PROM command. Set it with setenv -p netaddr 1.2.3.4 (replacing "1.2.3.4" with the IP address of the target system). Then, do boot -f bootp()hostsystem:xyx where "hostsystem" is the name of the host system and "xyz" is the name of the kernel you want to boot. If you add "-f" to the bootp line, you can use a full path name on the target system in place of "xyz". Any additional words on the command line are passed to the booted program as a UNIX-style argument list, and the environment variable list is passed as well. That is, on entry, the program will see argc in $a0, argv in $a1, and environ in $a2. On an Indy, the booted kernel (or other program) must be in MIPS ECOFF format. On Moosehead, the kernel must be in ELF format. The "-coff" option to the IRIX ld will cause it to create an ECOFF binary instead of an ELF binary in the final link, even if all the input binaries are in ELF format. If you want to boot an ELF kernel on Indy, you have to boot an indirect loader. You can use the IRIX sash. Put sash in the volume header on the Indy, or in a bootp-able place on the host system. Then do boot -f bootp()hostsystem:sash or boot -f sash and then, in either case boot -f bootp()hostsystem:xyx where the last command is to the sash prompt, not the PROM prompt. sash knows how to load both ELF and ECOFF. On an Indy, the PROM would like you to link the kernel at or above 0x88002000, with the highest address in the linked binary being below 0x88400000 (4 MB). From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 16:40:50 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA10985; Wed, 5 Jun 1996 16:40:49 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA12222 for linux-list; Wed, 5 Jun 1996 23:40:45 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA12213 for ; Wed, 5 Jun 1996 16:40:44 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA09961; Wed, 5 Jun 1996 16:38:09 -0700 Date: Wed, 5 Jun 1996 16:38:09 -0700 Message-Id: <199606052338.QAA09961@neteng.engr.sgi.com> From: "David S. Miller" To: wje@fir.esd.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <199606051835.LAA11745@fir.esd.sgi.com> (wje@fir.esd.sgi.com) Subject: Re: netbooting Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Wed, 5 Jun 1996 11:35:26 -0700 From: wje@fir.esd.sgi.com (William J. Earl) On an Indy, the booted kernel (or other program) must be in MIPS ECOFF format. Know whats strange, I can netboot big endian elf kernels from the ARCS command line monitor with zero problems on my target INDY. ;-) Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 16:56:54 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA15545; Wed, 5 Jun 1996 16:56:53 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA15640 for linux-list; Wed, 5 Jun 1996 23:56:43 GMT Received: from titian (titian.engr.sgi.com [192.102.117.31]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA15634; Wed, 5 Jun 1996 16:56:40 -0700 Received: from localhost by titian via SMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id QAA12520; Wed, 5 Jun 1996 16:56:40 -0700 Message-Id: <199606052356.QAA12520@titian> To: "David S. Miller" cc: wje@fir.esd.sgi.com, linux@cthulhu.engr.sgi.com Subject: Re: netbooting In-reply-to: Your message of "Wed, 05 Jun 1996 16:38:09 PDT." <199606052338.QAA09961@neteng.engr.sgi.com> Date: Wed, 05 Jun 1996 16:56:39 -0700 From: Mike McDonald Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk >Date: Wed, 5 Jun 1996 16:38:09 -0700 >From: "David S. Miller" >To: wje@fir.esd.sgi.com >Subject: Re: netbooting > > Date: Wed, 5 Jun 1996 11:35:26 -0700 > From: wje@fir.esd.sgi.com (William J. Earl) > > On an Indy, the booted kernel (or other program) must be > in MIPS ECOFF format. > >Know whats strange, I can netboot big endian elf kernels from the ARCS >command line monitor with zero problems on my target INDY. ;-) > >Later, >David S. Miller >dm@engr.sgi.com My understanding was that sash had to be COFF due to the proms but that the newer versions of sash understood both COFF and ELF kernels. Something like that anyway. Mike McDonald mikemac@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 17:28:25 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA18391; Wed, 5 Jun 1996 17:28:25 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA23246 for linux-list; Thu, 6 Jun 1996 00:27:19 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA23223 for ; Wed, 5 Jun 1996 17:27:14 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id RAA03914; Wed, 5 Jun 1996 17:27:05 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id RAA12455; Wed, 5 Jun 1996 17:26:22 -0700 Date: Wed, 5 Jun 1996 17:26:22 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606060026.RAA12455@fir.esd.sgi.com> To: Mike McDonald Cc: "David S. Miller" , linux@cthulhu.engr.sgi.com Subject: Re: netbooting In-Reply-To: <199606052356.QAA12520@titian> References: <199606052338.QAA09961@neteng.engr.sgi.com> <199606052356.QAA12520@titian> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Mike McDonald writes: > > >Date: Wed, 5 Jun 1996 16:38:09 -0700 > >From: "David S. Miller" > >To: wje@fir.esd.sgi.com > >Subject: Re: netbooting > > > > Date: Wed, 5 Jun 1996 11:35:26 -0700 > > From: wje@fir.esd.sgi.com (William J. Earl) > > > > On an Indy, the booted kernel (or other program) must be > > in MIPS ECOFF format. > > > >Know whats strange, I can netboot big endian elf kernels from the ARCS > >command line monitor with zero problems on my target INDY. ;-) > > > >Later, > >David S. Miller > >dm@engr.sgi.com > > My understanding was that sash had to be COFF due to the proms but > that the newer versions of sash understood both COFF and ELF kernels. > Something like that anyway. Yes, that is correct. If David is leaving off the "-f", it is possible that the PROM is booting sash first, and letting sash boot the kernel. On the other hand, David's Indy does have the latest Indy PROM, so it is possible that the PROM developer dropped in ELF support. We can't assume it is available on an Indy, so we let sash do the work. I checked on the PROM source, and the recent PROMs, such as what David has, do indeed boot ELF binaries directly. That is, both ELF and ECOFF are turned on in the recent Indy PROMs. From owner-linux@cthulhu.engr.sgi.com Sat Jun 8 02:09:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA07026; Sat, 8 Jun 1996 02:09:17 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id JAA28985 for linux-list; Sat, 8 Jun 1996 09:09:10 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA28980 for ; Sat, 8 Jun 1996 02:09:08 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id CAA07021; Sat, 8 Jun 1996 02:09:08 -0700 Date: Sat, 8 Jun 1996 02:09:08 -0700 Message-Id: <199606080909.CAA07021@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: wheee... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I finally got interrupts working... more to come Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sat Jun 8 04:23:48 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA07867; Sat, 8 Jun 1996 04:23:48 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id LAA03208 for linux-list; Sat, 8 Jun 1996 11:23:34 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA03203 for ; Sat, 8 Jun 1996 04:23:33 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id EAA07860; Sat, 8 Jun 1996 04:23:33 -0700 Date: Sat, 8 Jun 1996 04:23:33 -0700 Message-Id: <199606081123.EAA07860@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: Are you satisfied now Mr. McVoy? ;-) Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Calibrating delay loop.. ok - 91.96 BogoMIPS Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sat Jun 8 05:19:57 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id FAA08549; Sat, 8 Jun 1996 05:19:57 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id MAA04756 for linux-list; Sat, 8 Jun 1996 12:19:44 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id FAA04751 for ; Sat, 8 Jun 1996 05:19:43 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA08535; Sat, 8 Jun 1996 05:19:46 -0700 Date: Sat, 8 Jun 1996 05:19:46 -0700 Message-Id: <199606081219.FAA08535@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: well it is about time... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk This port is going like a funeral procession, I apologize. Ok, quick report: 1) Interrupts work, with a little more coding it will handle the setup and registering of all interrupts and handlers on the INDY for whatever driver requests them. 2) Timers work, I am using the r4k counter/compare register timer mechanism because of the bug in the i8254 Intel timer chips on certain INDY's. The calibration of the compare offsets needs some work but the working framework is there and needs a little tweaking, basically my algorithm is: a) setup i8254 counter 0 and counter 2 such that the period of counter 0 is the desired HZ value b) poll counter 0 waiting for a value of 1 c) quickly set CP0_COUNTER to zero d) poll counter 0 for value of 1 e) quickly read CP0_COUNTER value This seems to approximate the value I want in it's current form pretty well. I have to add some fuzz factors into it and possibly write the calibration code in assembly to get the accuracy I want/need. 3) The kernel boots decently far. It init's all of memory management, sets up the buffer cache, sets up the inode table, inits the networking stack, prints the linux banner and is about to fork off the init kernel thread. At this point my task list looks like: 1) Clean up and finish all the krufty code I wrote tonight ;-) 2) Write console/keyboard/mouse/serial drivers as these will need to be done anyways. 3) Do some verification on what works at that point. 4) Look into getting kgdb working. 5) Write ethernet/scsi drivers. 6) (fingers crossed) shell prompt... we hope... As far as I'm concerned I am severely behind schedule. I will try to get the pace going more quickly soon, I promise. Sorry. God, I'm so slow, two weeks to get the thing to half boot, sheesh! Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sat Jun 8 11:23:39 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA12624; Sat, 8 Jun 1996 11:23:39 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA20038 for linux-list; Sat, 8 Jun 1996 18:23:29 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA20033 for ; Sat, 8 Jun 1996 11:23:28 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id LAA01539; Sat, 8 Jun 1996 11:22:46 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606081822.LAA01539@yon.engr.sgi.com> Subject: Re: Are you satisfied now Mr. McVoy? ;-) To: dm@neteng.engr.sgi.com (David S. Miller) Date: Sat, 8 Jun 1996 11:22:46 -0700 (PDT) Cc: linux@cthulhu.engr.sgi.com In-Reply-To: <199606081123.EAA07860@neteng.engr.sgi.com> from "David S. Miller" at Jun 8, 96 04:23:33 am Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 688 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > > >Calibrating delay loop.. ok - 91.96 BogoMIPS > Will a Triton CPU (R5000) make this better ? :-) For those who are not familiar with bogomips, my Pentium-100 at home does 39.94 bogomips. And the best number I've seen for a desktop is almost 300 bogomips for an Alpha 21064 overclocked to 300MHz. The 91.96 number for a 150MHz Indy sounds pretty good. Still, I would like to know, David: What clock factor are you using? The DEC Alphas do one clock pre instruction, so their factor is 1, why is the Indy at less than two-thirds of its clock rate? Fr more details: http://sunsite.unc.edu/linux/HOWTO/mini/BogoMips It would be nice to send them the new data... -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Mon Jun 10 09:56:40 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA25215; Mon, 10 Jun 1996 09:56:40 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA15622 for linux-list; Mon, 10 Jun 1996 16:56:35 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA15615 for ; Mon, 10 Jun 1996 09:56:34 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id JAA22016; Mon, 10 Jun 1996 09:56:33 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id JAA28660; Mon, 10 Jun 1996 09:56:22 -0700 Date: Mon, 10 Jun 1996 09:56:22 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606101656.JAA28660@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@cthulhu.engr.sgi.com Subject: Re: Are you satisfied now Mr. McVoy? ;-) In-Reply-To: <199606081123.EAA07860@neteng.engr.sgi.com> References: <199606081123.EAA07860@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > > Calibrating delay loop.. ok - 91.96 BogoMIPS I assume this is on the target system, which should be a 133 MHZ R4600SC. From owner-linux@cthulhu.engr.sgi.com Mon Jun 10 10:00:04 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA25259; Mon, 10 Jun 1996 10:00:04 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA16313 for linux-list; Mon, 10 Jun 1996 17:00:00 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA16307 for ; Mon, 10 Jun 1996 09:59:59 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id JAA22242; Mon, 10 Jun 1996 09:59:58 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id JAA28671; Mon, 10 Jun 1996 09:59:47 -0700 Date: Mon, 10 Jun 1996 09:59:47 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606101659.JAA28671@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@cthulhu.engr.sgi.com Subject: Re: well it is about time... In-Reply-To: <199606081219.FAA08535@neteng.engr.sgi.com> References: <199606081219.FAA08535@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > > This port is going like a funeral procession, I apologize. Not at all--nice work. Considering some of the messy stuff you have to deal with, it is going quite well. .. > 2) Timers work, I am using the r4k counter/compare register timer > mechanism because of the bug in the i8254 Intel timer chips > on certain INDY's. The calibration of the compare offsets > needs some work but the working framework is there and needs > a little tweaking, basically my algorithm is: > > a) setup i8254 counter 0 and counter 2 such that the period > of counter 0 is the desired HZ value > b) poll counter 0 waiting for a value of 1 > c) quickly set CP0_COUNTER to zero > d) poll counter 0 for value of 1 > e) quickly read CP0_COUNTER value > > This seems to approximate the value I want in it's current form > pretty well. I have to add some fuzz factors into it and possibly > write the calibration code in assembly to get the accuracy I > want/need. When it is time to do R4000 support, I can show you how to work around the R4000 count/compare bug. (This does not apply to other processors, such as the R4600, R5000, or R10000.) From owner-linux@cthulhu.engr.sgi.com Mon Jun 10 10:02:23 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA25357; Mon, 10 Jun 1996 10:02:23 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA16773 for linux-list; Mon, 10 Jun 1996 17:02:15 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA16758 for ; Mon, 10 Jun 1996 10:02:14 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id JAA25237; Mon, 10 Jun 1996 09:59:38 -0700 Date: Mon, 10 Jun 1996 09:59:38 -0700 Message-Id: <199606101659.JAA25237@neteng.engr.sgi.com> From: "David S. Miller" To: wje@fir.esd.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <199606101656.JAA28660@fir.esd.sgi.com> (wje@fir.esd.sgi.com) Subject: Re: Are you satisfied now Mr. McVoy? ;-) Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Mon, 10 Jun 1996 09:56:22 -0700 From: wje@fir.esd.sgi.com (William J. Earl) David S. Miller writes: > Calibrating delay loop.. ok - 91.96 BogoMIPS I assume this is on the target system, which should be a 133 MHZ R4600SC. Yes, but beware my r4k compare register calibration still needs some work, this value could be off a bit... Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 10 10:03:14 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA25452; Mon, 10 Jun 1996 10:03:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA16904 for linux-list; Mon, 10 Jun 1996 17:03:05 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA16889; Mon, 10 Jun 1996 10:03:04 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id KAA22379; Mon, 10 Jun 1996 10:03:01 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id KAA28690; Mon, 10 Jun 1996 10:02:50 -0700 Date: Mon, 10 Jun 1996 10:02:50 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606101702.KAA28690@fir.esd.sgi.com> To: ariel@cthulhu.engr.sgi.com Cc: dm@neteng.engr.sgi.com (David S. Miller), linux@cthulhu.engr.sgi.com Subject: Re: Are you satisfied now Mr. McVoy? ;-) In-Reply-To: <199606081822.LAA01539@yon.engr.sgi.com> References: <199606081123.EAA07860@neteng.engr.sgi.com> <199606081822.LAA01539@yon.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ariel Faigon writes: > > > > > >Calibrating delay loop.. ok - 91.96 BogoMIPS > > > Will a Triton CPU (R5000) make this better ? :-) An R5000 should scale with clock rate, relative to the 133 MHZ R4600 David is using. The 180 MHZ R5000 would then be 124.46. > For those who are not familiar with bogomips, my Pentium-100 > at home does 39.94 bogomips. And the best number I've seen > for a desktop is almost 300 bogomips for an Alpha 21064 > overclocked to 300MHz. The 91.96 number for a 150MHz Indy > sounds pretty good. I think the 150 MHZ R4400 is in David's host machine, with the 133 MHZ R4600 in his target machine, so the 91.96 should be for the latter. From owner-linux@cthulhu.engr.sgi.com Mon Jun 10 10:16:08 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA25944; Mon, 10 Jun 1996 10:16:08 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA19095 for linux-list; Mon, 10 Jun 1996 17:16:00 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA19090 for ; Mon, 10 Jun 1996 10:15:59 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA25937; Mon, 10 Jun 1996 10:15:59 -0700 Date: Mon, 10 Jun 1996 10:15:59 -0700 Message-Id: <199606101715.KAA25937@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: oh btw... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk (for those not following the CVS commit mailing list...) I got the Linux graphics console working on the NEWPORT tonight, seems to work decently well... you guys make some strange graphics hardware... ;-) Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 10 17:13:53 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA11152; Mon, 10 Jun 1996 17:13:53 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA10445 for linux-list; Tue, 11 Jun 1996 00:13:41 GMT Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA10419 for ; Mon, 10 Jun 1996 17:13:38 -0700 Received: by soyuz.wellington.sgi.com (951211.SGI.8.6.12.PATCH1042/940406.SGI) for linux@cthulhu.engr.sgi.com id MAA03444; Tue, 11 Jun 1996 12:13:36 +1200 From: alambie@wellington.sgi.com (Alistair Lambie) Message-Id: <199606110013.MAA03444@soyuz.wellington.sgi.com> Subject: Is this a silly idea? To: linux@cthulhu.engr.sgi.com Date: Tue, 11 Jun 1996 12:13:36 +1200 (NZT) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 835 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Folks, I guess a lot of people will have both Linux and that other operating system on there machines for various reasons. One thing that I know I would find useful is to be able to have a filesystem that could be accessed from whichever OS you had loaded (eg. for putting mail and other common things on). I'm not sure what the best way to attack this would be, but my guess is that we need to put the common filesystem in Irix, as I would pick that it would be difficult to get the buyin to port one of our filesystems to Linux. Several questions: 1. Is this sensible (or is there already a way of doing this)? 2. If it is sensible, what should we do (type of fs etc)? 3. Does anyone know how easy this is (I'm not sure whether I'm brave enough!)? Just a thought.... Alistair PS - I get 61.64 Bogomips on a 100MHz R4600PC From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 10:36:25 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA05933; Tue, 11 Jun 1996 10:36:25 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA11086 for linux-list; Tue, 11 Jun 1996 17:36:18 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA11075 for ; Tue, 11 Jun 1996 10:36:17 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA05924; Tue, 11 Jun 1996 10:36:16 -0700 Date: Tue, 11 Jun 1996 10:36:16 -0700 Message-Id: <199606111736.KAA05924@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: my CVS tree Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I want to have my CVS tree moved into a place which is backed up often and is stable + globally accessible with ease by others. And after seeing my home directory get spammed not two days after I get here, neteng is currently _not_ the place as of now, I feel more confident having it stay on my workstation as it does indeed right now. It would be a shame to lose all the work I have done, so I'd like to take care of this soon. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 10:39:01 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA05960; Tue, 11 Jun 1996 10:39:01 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA11605 for linux-list; Tue, 11 Jun 1996 17:38:57 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA11600 for ; Tue, 11 Jun 1996 10:38:56 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA05955; Tue, 11 Jun 1996 10:38:50 -0700 Date: Tue, 11 Jun 1996 10:38:50 -0700 Message-Id: <199606111738.KAA05955@neteng.engr.sgi.com> From: "David S. Miller" To: alambie@wellington.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <199606110013.MAA03444@soyuz.wellington.sgi.com> (alambie@wellington.sgi.com) Subject: Re: Is this a silly idea? Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: alambie@wellington.sgi.com (Alistair Lambie) Date: Tue, 11 Jun 1996 12:13:36 +1200 (NZT) I'm not sure what the best way to attack this would be, but my guess is that we need to put the common filesystem in Irix, as I would pick that it would be difficult to get the buyin to port one of our filesystems to Linux. I planned on hacking xfs _and_ efs implementations into Linux. Several questions: 1. Is this sensible (or is there already a way of doing this)? 2. If it is sensible, what should we do (type of fs etc)? 3. Does anyone know how easy this is (I'm not sure whether I'm brave enough!)? Also, I wouldn't mind seeing an ext2 implementation in IRIX, I could probably hack up an initial read-only kernel module implementation in a very short amount of time. This is all only a matter of someone sitting behind the screen and whacking away at the code for 2 or 3 days, nothing more. I'd rather concentrate on getting bootstrapped at this point, but after that I'll probably hack on something like xfs/efs or whatever. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 10:48:11 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA06125; Tue, 11 Jun 1996 10:48:11 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA13132 for linux-list; Tue, 11 Jun 1996 17:48:01 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA13124 for ; Tue, 11 Jun 1996 10:47:59 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id KAA06117; Tue, 11 Jun 1996 10:47:59 -0700 Message-Id: <199606111747.KAA06117@neteng.engr.sgi.com> To: linux@neteng.engr.sgi.com Cc: jmy@neteng.engr.sgi.com From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) Subject: Re: Is this a silly idea? Date: Tue, 11 Jun 1996 10:47:59 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : I planned on hacking xfs _and_ efs implementations into Linux. We will shoot that plan in the head right away. EFS is dead technology and XFS is family jewels. If we start putting XFS into Linux, there will be hell to pay. Besides, XFS is 45K lines of code (probably more now) and it is really non trivial. Porting that to Linux would take quite a while. I would like to have an XFS port eventually, but we need to figure out a way to keep it SGI source. Last I checked, there was noise that doing stuff as a loadable module was not enough. Any news on that? I think porting ext2fs to IRIX is a much better idea. : Also, I wouldn't mind seeing an ext2 implementation in IRIX, I could : probably hack up an initial read-only kernel module implementation in : a very short amount of time. Please. I have some file system notes somewhere that talk about the data structures needed to do this. James is a good resource, he did cachefs. He's a busy, but nice, guy and he sits near you. --lm From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 11:45:46 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA07237; Tue, 11 Jun 1996 11:45:46 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA23150 for linux-list; Tue, 11 Jun 1996 18:45:37 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA23138 for ; Tue, 11 Jun 1996 11:45:36 -0700 Received: from storm.engr.sgi.com (storm.engr.sgi.com [192.26.79.92]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA07226 for ; Tue, 11 Jun 1996 11:45:35 -0700 Received: by storm.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux@neteng id LAA25628; Tue, 11 Jun 1996 11:44:13 -0700 From: "Donna Yobs" Message-Id: <9606111144.ZM25626@storm.engr.sgi.com> Date: Tue, 11 Jun 1996 11:44:12 -0700 In-Reply-To: lm@gate1-neteng (Larry McVoy) "Re: Is this a silly idea?" (Jun 11, 10:47am) References: <199606111747.KAA06117@neteng.engr.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: linux@neteng.engr.sgi.com Subject: Re: Is this a silly idea? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk lm is right, we don't want to let the xfs source out; but if we could do just the loadable modules it would show an advantage of mips technology on linux (or is that counter culture, sigh). -d -- ------------------------------------------------------------------------- Donna Derby Yobs Silicon Graphics - NSD yobs@engr.sgi.com Product Marketing From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 12:48:07 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id MAA08750; Tue, 11 Jun 1996 12:48:07 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id TAA03375 for linux-list; Tue, 11 Jun 1996 19:48:02 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id MAA03370 for ; Tue, 11 Jun 1996 12:48:01 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id MAA08744; Tue, 11 Jun 1996 12:48:00 -0700 Message-Id: <199606111948.MAA08744@neteng.engr.sgi.com> To: "Donna Yobs" From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: linux@neteng.engr.sgi.com Subject: Re: Is this a silly idea? Date: Tue, 11 Jun 1996 12:48:00 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : lm is right, we don't want to let the xfs source out; : but if we could do just the loadable modules it would : show an advantage of mips technology on linux (or is : that counter culture, sigh). We will need to do this eventually. From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 15:35:21 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA14658; Tue, 11 Jun 1996 15:35:21 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA28354 for linux-list; Tue, 11 Jun 1996 22:35:15 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA28349 for ; Tue, 11 Jun 1996 15:35:13 -0700 Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA14655 for ; Tue, 11 Jun 1996 15:35:13 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA06140; Tue, 11 Jun 1996 15:34:31 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606112234.PAA06140@yon.engr.sgi.com> Subject: Re: Is this a silly idea? To: yobs@storm.engr.sgi.com (Donna Yobs) Date: Tue, 11 Jun 1996 15:34:30 -0700 (PDT) Cc: linux@neteng.engr.sgi.com In-Reply-To: <9606111144.ZM25626@storm.engr.sgi.com> from "Donna Yobs" at Jun 11, 96 11:44:12 am Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 861 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > >lm is right, we don't want to let the xfs source out; >but if we could do just the loadable modules it would >show an advantage of mips technology on linux (or is >that counter culture, sigh). > Donna, I think this is a good realistic compromise that can be accepted both by SGI and the Linux community. On the way to "world domination now" (as Linus puts it), Linux enthusiasts must learn how to realistically compromise here and there. Think of it: a much more significant "compromise" is to support the Windows API via WINE etc. rather than trying to force the Unix APIs upon the rest of the software-developers-world and lose. With clever compromises that the commercial world can accept and by keeping the vast majority of the value under the GPL, Linux will gradually get where Linus (and some of the rest of us :-) want it to be. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 15:55:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA15626; Tue, 11 Jun 1996 15:55:16 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA00759 for linux-list; Tue, 11 Jun 1996 22:55:12 GMT Received: from storm.engr.sgi.com (storm.engr.sgi.com [192.26.79.92]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA00750 for ; Tue, 11 Jun 1996 15:55:10 -0700 Received: by storm.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux id PAA26486; Tue, 11 Jun 1996 15:53:48 -0700 Date: Tue, 11 Jun 1996 15:53:48 -0700 From: yobs@storm.engr.sgi.com (Donna Yobs) Message-Id: <199606112253.PAA26486@storm.engr.sgi.com> To: linux@storm.engr.sgi.com Subject: nt... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hate to muddy the waters, but a customer has asked about getting some basic tools onto NT so that we can interop better. Hoping someone in this group may have some insight, I'm including the email. Let me know if you have any ideas. I'm trying to iron out a list of what we should do to have a better PC friendly view of the world, without going to NT. thanks -- included text -- The type of NT tools that I would be looking for is as follows: Our company writes glue to tie many of the entertainment type applications together. We have translaters, display tools, programs that scan disk directories and verify that all the frames of a shot are present, etc. For example, we have a small program that sircheck (for Solitair Image Recorder Check) that opens each frame of a shot and reads the header to make sure that all the frames are of the same resolution. If you have been doing a shot at video res and rerender at 2k resolution, It is possible that all of the frames are present, but that one of them is still the old version. The most common mistake is to copy frames 1-99 and then 101-199 skipping frame 100. Customers now have NT workstations -- whether for 3Dstudio, lightwave, Softimage, or whatever. We are being asked for the ability to execute sircheck from an NT workstation so that the files can be verified by the animator before he turns the tape over to the guy who will be shooting the shot on an SGI workstation. This utility is part of what makes our film recorder package more attractive than the competition. Failure to respond to this kind of request would make our company appear less responsive in a business that borders on the edge of custom consultation. We have been exclusively SGI based since 1984, and have very little NT experience. Most of our utilities have some kind of GL or OpenGL based GUI. I am looking for any help to run this kind of program on NT. There is no high performance graphics involved. Nor do I wish to redesign the interface to match NT style. I think I can do some of what I want with the software GL emulator that was presented for Windows 95. I need some no cost software like that GL package. In addition, I need low level stuff like what is in the developers toolbox. Readers and writers and low level chunks. For example, we need the ability to read SGI .rgb format files on NT. The net abounds with utilities for Unix type things on NT, such as tar. I spoke with the toolbox janitors about collecting these type of utilities and seeing which ones support the IRIX versions. For example, finding or adapting a public domain NT tar package such that it will easily recognize and handle the default SGI tar block sizes and byte order. Our customers are artists and animators, not computer programmers. They need the ability to read tapes, translate files, and in general, go back and forth between tools and packages without typing a 60 character command line. They need more than an NFS mounted partition shared between the SGI and NT. What good is an NFS mounted partition if you can't read the file format? The developers toolbox is a wouderful, useful, and esential effort. It contains much public stuff cleansed for use with SGI machines. I believe that if the effort is expanded to include tools for NT that would enable SGI machines to better fit into a mixed environment, our ability to sell SGI into these accounts would be greatly enhanced. Right now, I am under a lot of pressure to port our whole film recorder to NT. This would be a big project, and one I am not wild about. If I can not make it easier for SGI's and NT to co-exist, we will have to give it serious thought. I hope this answers some of your questions. I see that my sticky keyboard has played havok with my spelling. I can not seem to find a decent mail package that can work between my PC and the SGI mailhost that we have at RFX. Another example of problems working with NT and SGI. It is agravating not being able to spellcheck or to edit. Ray Feeney ------------------------------------------------------------------------- Donna Derby Yobs Silicon Graphics - NSD yobs@engr.sgi.com Product Marketing http://storm.engr From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 17:04:42 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA17294; Tue, 11 Jun 1996 17:04:42 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA12447 for linux-list; Wed, 12 Jun 1996 00:04:31 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA12442 for ; Tue, 11 Jun 1996 17:04:30 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA17283; Tue, 11 Jun 1996 17:04:30 -0700 Date: Tue, 11 Jun 1996 17:04:30 -0700 Message-Id: <199606120004.RAA17283@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: I fixed the r4ktimer code... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Calibrating delay loop.. ok - 138.04 BogoMIPS Much better ;-) Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 18:11:20 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA21562; Tue, 11 Jun 1996 18:11:20 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA24805 for linux-list; Wed, 12 Jun 1996 01:11:12 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA24799 for ; Tue, 11 Jun 1996 18:11:10 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id SAA09358; Tue, 11 Jun 1996 18:11:09 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id SAA08986; Tue, 11 Jun 1996 18:11:05 -0700 Date: Tue, 11 Jun 1996 18:11:05 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606120111.SAA08986@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@cthulhu.engr.sgi.com Subject: Re: I fixed the r4ktimer code... In-Reply-To: <199606120004.RAA17283@neteng.engr.sgi.com> References: <199606120004.RAA17283@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > > Calibrating delay loop.. ok - 138.04 BogoMIPS > > Much better ;-) Yes, except that it should really be 133.33 on the 133 MHZ R4600SC. I don't have any idea where the 4% error would be coming from, unless there is something wrong with the external timer. One way of checking the timer might be to measure a tick of the Dallas clock/calendar chip. I believe the one we use in Indy counts 0.01 second units, so noticing the $count change over, say, a 0.5 second interval, as measured by the Dallas part, would be a way of validating the timer configuration. From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 18:22:26 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA21879; Tue, 11 Jun 1996 18:22:26 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA26908 for linux-list; Wed, 12 Jun 1996 01:22:21 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA26898 for ; Tue, 11 Jun 1996 18:22:20 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAB21833; Tue, 11 Jun 1996 18:19:45 -0700 Date: Tue, 11 Jun 1996 18:19:45 -0700 Message-Id: <199606120119.SAB21833@neteng.engr.sgi.com> From: "David S. Miller" To: wje@fir.esd.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <199606120111.SAA08986@fir.esd.sgi.com> (wje@fir.esd.sgi.com) Subject: Re: I fixed the r4ktimer code... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Tue, 11 Jun 1996 18:11:05 -0700 From: wje@fir.esd.sgi.com (William J. Earl) David S. Miller writes: > > Calibrating delay loop.. ok - 138.04 BogoMIPS > > Much better ;-) Yes, except that it should really be 133.33 on the 133 MHZ R4600SC. I don't have any idea where the 4% error would be coming from, unless there is something wrong with the external timer. One way of checking the timer might be to measure a tick of the Dallas clock/calendar chip. I believe the one we use in Indy counts 0.01 second units, so noticing the $count change over, say, a 0.5 second interval, as measured by the Dallas part, would be a way of validating the timer configuration. Peculiar... but I believe if you look at the calibrate_delay() function I sent you earlier you will see that the way it performs the calculation implies a certain error fuzz all in the name of efficiency (some time back calibrate_delay() was much more accurate but took 3 or 4 seconds to run at boot time, ugh, the lesser of two evils) The new way I calculate the r4k compare register offset is that I set the rate generation of the Intel counter at 1HZ. I then make 4 samples of how far the r4k counter goes every time the Intel counter makes a full 1 HZ iteration. I then average these 4 samples and multiply by HZ (which == 100 for the Mips port of Linux) to find the final r4k offset value that I use. Anyways, BogoMIPS is by definition "bogus" ;-) It is only used by the kernel to do quick microsecond delays in various places of the kernel. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 12 16:14:43 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA01877; Wed, 12 Jun 1996 16:14:42 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA21396 for linux-list; Wed, 12 Jun 1996 23:14:37 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA21388 for ; Wed, 12 Jun 1996 16:14:36 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA01857; Wed, 12 Jun 1996 16:14:35 -0700 Date: Wed, 12 Jun 1996 16:14:35 -0700 Message-Id: <199606122314.QAA01857@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: off topic question Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk What is a good program under IRIX for creating figures and slides? Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 12 16:23:55 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA01964; Wed, 12 Jun 1996 16:23:55 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA23238 for linux-list; Wed, 12 Jun 1996 23:23:51 GMT Received: from beyond.clubfed.sgi.com (beyond.clubfed.sgi.com [169.238.1.2]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA23215 for ; Wed, 12 Jun 1996 16:23:47 -0700 Received: from trinbago.clubfed.sgi.com by beyond.clubfed.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/911001.SGI) id TAA01662; Wed, 12 Jun 1996 19:22:12 -0400 Received: by trinbago.clubfed.sgi.com (940816.SGI.8.6.9/940406.SGI.AUTO) id TAA01821; Wed, 12 Jun 1996 19:44:59 -0400 From: "Kwesi Ames" Message-Id: <9606121944.ZM1819@trinbago.clubfed.sgi.com> Date: Wed, 12 Jun 1996 19:44:50 -0400 In-Reply-To: "David S. Miller" "off topic question" (Jun 12, 4:14pm) References: <199606122314.QAA01857@neteng.engr.sgi.com> X-Face: +g~UQT+z9(^"0C`fv,%E,C6_Oe)WXTlrohR/DaIIi.M1K4Q.Lov?w.b5_9)7ttP:DT)a})( Q*I&N#UNe$Tnxu^U!'P8-AbGqCG,y;#j4iO;rkEr`^$o7DmAqm5?uU8@'w88/iSrC-{4,a423@pN,7x&P7n=2@Y8{ X-Mailer: Z-Mail-SGI (3.2S.1 10apr95 MediaMail) To: "David S. Miller" , linux@cthulhu.engr.sgi.com Subject: Re: off topic question Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Jun 12, 4:14pm, David S. Miller wrote: > Subject: off topic question > > What is a good program under IRIX for creating figures and slides? > > Later, > David S. Miller > dm@sgi.com >-- End of excerpt from David S. Miller You mean other than Showcase?? Kwesi -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kwesi O. Ames Systems Engineering Support Silicon Graphics Inc. koa@sgi.com "I was one in a MILLON" corp voicemail (800) 326-1020 ext. 5-8713 phone (301) 572-3255 fax (301) 572-3280 http://reality.sgi.com/koa ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-linux@cthulhu.engr.sgi.com Wed Jun 12 16:27:35 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA02031; Wed, 12 Jun 1996 16:27:34 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA23886 for linux-list; Wed, 12 Jun 1996 23:27:31 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA23881 for ; Wed, 12 Jun 1996 16:27:29 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA02023; Wed, 12 Jun 1996 16:27:27 -0700 Date: Wed, 12 Jun 1996 16:27:27 -0700 Message-Id: <199606122327.QAA02023@neteng.engr.sgi.com> From: "David S. Miller" To: koa@trinbago.clubfed.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <9606121944.ZM1819@trinbago.clubfed.sgi.com> (koa@trinbago.clubfed.sgi.com) Subject: Re: off topic question Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: "Kwesi Ames" Date: Wed, 12 Jun 1996 19:44:50 -0400 You mean other than Showcase?? Thank you... I didn't know about showcase. ;) Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sun Jun 16 18:44:09 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA19168; Sun, 16 Jun 1996 18:44:09 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA24443 for linux-list; Mon, 17 Jun 1996 01:43:41 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA24438 for ; Sun, 16 Jun 1996 18:43:40 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA19157; Sun, 16 Jun 1996 18:43:39 -0700 Date: Sun, 16 Jun 1996 18:43:39 -0700 Message-Id: <199606170143.SAA19157@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: SHELLL PROMPT!!! Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk And some other userland utilities work as well... wheee... Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 17 13:51:15 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA16944; Mon, 17 Jun 1996 13:51:15 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA24316 for linux-list; Mon, 17 Jun 1996 20:51:09 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA24309 for ; Mon, 17 Jun 1996 13:51:08 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id NAA16930; Mon, 17 Jun 1996 13:51:07 -0700 Date: Mon, 17 Jun 1996 13:51:07 -0700 Message-Id: <199606172051.NAA16930@neteng.engr.sgi.com> From: "David S. Miller" To: linux@neteng.engr.sgi.com Subject: strace project Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I'm just curious how strace support for IRIX 6.2 is coming along? It would be _extremely_ useful and make me _extremely_ happy to have so that I can write all of the IRIX system call compatability code when I return from my talks in the U.K. on Thursday. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 17 13:58:13 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA17123; Mon, 17 Jun 1996 13:58:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA26260 for linux-list; Mon, 17 Jun 1996 20:58:06 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA26244 for ; Mon, 17 Jun 1996 13:58:04 -0700 Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA17113 for ; Mon, 17 Jun 1996 13:58:04 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id NAA12238; Mon, 17 Jun 1996 13:58:03 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id NAA10393; Mon, 17 Jun 1996 13:58:02 -0700 Date: Mon, 17 Jun 1996 13:58:02 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606172058.NAA10393@fir.esd.sgi.com> To: dm@sgi.com Cc: linux@neteng.engr.sgi.com Subject: Re: strace project In-Reply-To: <199606172051.NAA16930@neteng.engr.sgi.com> References: <199606172051.NAA16930@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > > I'm just curious how strace support for IRIX 6.2 is coming along? > > It would be _extremely_ useful and make me _extremely_ happy to have > so that I can write all of the IRIX system call compatability code > when I return from my talks in the U.K. on Thursday. If by strace you mean tracing system call arguments and results, try using par(1). (It does not help if you want to decode argument structures, however.) Here is a sample: par -s -SS date Mon Jun 17 13:56:39 PDT 1996 0mS was sent signal SIGUSR1 0mS END-pause() errno = 4 (Interrupted system call) 0mS received signal SIGUSR1 0mS sigreturn(0x7fff2a00) OK 1mS execve(/usr/bsd/date, 0x7fff2ea8, 0x7fff2eb0) errno = 2 (No such file or directory) 1mS execve(/usr/new/date, 0x7fff2ea8, 0x7fff2eb0) errno = 2 (No such file or directory) 1mS execve(/usr/people/wje/abi-bin/date, 0x7fff2ea8, 0x7fff2eb0) errno = 2 (No such file or directory) 2mS execve(/usr/people/wje/irix-bin/date, 0x7fff2ea8, 0x7fff2eb0) errno = 2 (No such file or directory) 2mS execve(/usr/bin/date, 0x7fff2ea8, 0x7fff2eb0) OK 74mS open(/lib/rld, O_RDONLY, 04) = 3 74mS read(3, <7f 45 4c 46 01 02 01 00 00 00 00 00 00 00 00 00>..., 52) = 52 74mS lseek(3, 52, SEEK_SET) = 52 74mS read(3, <70 00 00 00 00 00 00 a0 0f b6 00 a0 0f b6 00 a0>..., 96) = 96 74mS elfmap(3, 0x7fff21bc, 2) = 0xfb60000 75mS close(3) OK 76mS getpagesize() = 4096 77mS getpid() = 10390 ppid=10389 78mS syssgi(SGI_TOSSTSAVE) OK 78mS getpagesize() = 4096 78mS brk(0x10002000) OK 80mS time() = 835044999 80mS ioctl(1, TCGETA, 0x7fff2cd8) = 0 81mS write(1, "Mon Jun 17 13:56:39 PDT 1996\n", 29) = 29 81mS prctl(PR_GETNSHARE) = 0 81mS exit(0) exit : 1 times read : 2 times write : 1 times open : 1 times close : 1 times time : 1 times brk : 1 times lseek : 1 times getpid : 1 times syssgi : 2 times ioctl : 1 times sysmp : 2 times execve : 5 times sigreturn : 1 times prctl : 1 times From owner-linux@cthulhu.engr.sgi.com Mon Jun 17 14:20:50 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA17642; Mon, 17 Jun 1996 14:20:50 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id VAA01426 for linux-list; Mon, 17 Jun 1996 21:20:44 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA01414 for ; Mon, 17 Jun 1996 14:20:41 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id OAA17636; Mon, 17 Jun 1996 14:20:40 -0700 Date: Mon, 17 Jun 1996 14:20:40 -0700 Message-Id: <199606172120.OAA17636@neteng.engr.sgi.com> From: "David S. Miller" To: linux@neteng.engr.sgi.com Subject: native Linux/MIPS binaries Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I'm going to be away giving talks in the U.K. until Thursday afternoon. With that in mind I'm going to show people how they can begin to become acquainted with the work that is already done, and how to setup a cross-compilation environment both for the kernel and for userland binaries. If you want to checkout and build your own SGILinux kernels, Larry and myself have set things up so that this is possible on neteng. Just ask Larry to put you into group 'hackers' on neteng and you'll be able to check out a CVS kernel source tree. Step 1: Get added to group 'hackers' on neteng. Step 2: Make sure the following are close to the beginning of your PATH: /usr/local/gnu-cross-seb/bin These are the cross gcc/binutils utilities necessary to build a SGI Linux kernel. /hosts/neteng/usr/people/dm/install/bin These are miscellaneous GNU utilities such as CVS, GNU make, and GNU awk, which are required for the build process. Step 3: Set CVSROOT environment variable to /hosts/tanya/cvs and checkout your very own kernel. $ export CVSROOT=/hosts/tanya/cvs $ mkdir src $ cd src $ cvs checkout linux If you've had a tree for a while, or see some updates on linux-progress you would like integrated into your tree do this. $ cd src $ cvs update linux If you want to make changes to the source, and feel overly free to, specify the file to be 'committed' back into the CVS repository like this. $ cd src/linux/drivers/net $ cvs commit -m "My cool checkin message." sgiseeq.c sgiseeq.h CVS has a lot of other powerful features such as revision diffs, automatic commit conflict detection etc. Step 4: Configure and build. $ cd linux $ make oldconfig $ make dep; make clean $ make vmlinux Or if you like parallel builds (neteng can build Linux kernels in around 2 1/2 minutes flat) replace the last command with. $ make -j Step 5: If you want, boot the thing. $ cp vmlinux /usr/local/boot Go into the ARCS boot monitor prompt on the other machine and say something like >> bootp()server:vmlinux And it should at least do something interesting ;-) For userland, unfortunately, I can only point you at where the current Linux/MIPS information is located. I will be doing some detective work on native userland binaries myself when I return, but people can check it out for now if they would like to. The current main distribution site is: ftp.fnet.fr:/linux-mips/ The current library the other MIPS are using as a basis cannot be obtained from the above site, it is a pre-test release of GNU libc, you can obtain snapshots of these prereleases from: alpha.gnu.ai.mit.edu:/roland/ These are developer snapshots, so don't be surprised if it doesn't work without applying a hammer to the code/makefiles. ;-) I believe that the cross-development tools provided on ftp.fnet.fr can be used to compile the GNU libc and subsequently the userlevel binaries linked with GNU libc. The Linux/MIPS web site hasn't been talking to me lately, seems like a configuration on their end, but for reference it is: http://www.fnet.fr/linux-mips/ The documation provided there can be found at the Linux/MIPS ftp site as well I believe. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 17 15:28:36 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA23455; Mon, 17 Jun 1996 15:28:36 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA20651 for linux-list; Mon, 17 Jun 1996 22:27:38 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA20641 for ; Mon, 17 Jun 1996 15:27:37 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id PAA23297; Mon, 17 Jun 1996 15:27:36 -0700 Message-Id: <199606172227.PAA23297@neteng.engr.sgi.com> To: wje@fir.esd.sgi.com (William J. Earl) From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: linux@neteng.engr.sgi.com Subject: Re: strace project Date: Mon, 17 Jun 1996 15:27:36 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : If by strace you mean tracing system call arguments and results, : try using par(1). (It does not help if you want to decode argument structures, : however.) Here is a sample: He needs to decode args. The idea was that strace groks most of the ioctls in most OS's. If we ever want to run little endian binaries on a big endian kernel (which would be kinda cool) we need the arg decode. David wanted it for something else too. --lm From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 09:41:56 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA03622; Tue, 18 Jun 1996 09:41:55 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA17045 for linux-list; Tue, 18 Jun 1996 16:41:49 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA17026 for ; Tue, 18 Jun 1996 09:41:48 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id JAA03609; Tue, 18 Jun 1996 09:41:47 -0700 Message-Id: <199606181641.JAA03609@neteng.engr.sgi.com> To: linux@neteng.engr.sgi.com Cc: olson@neteng.engr.sgi.com Subject: anyone know if this is true? Date: Tue, 18 Jun 1996 09:41:47 -0700 From: Larry McVoy Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk If it isn't true, can someone send mail to Tiemann and tell him the facts. Sounds like we're getting bad press. ------- Forwarded Message Date: Tue, 18 Jun 1996 05:22:52 -0700 From: Michael Tiemann To: lm@sgi.com Subject: [comp.sys.sgi.apps] gcc part II Is this not fixed in 6.2? I upgraded my machine at home yesterday, and it looked suspiciously like SGI was providing headers and libraries as part of the std 6.2 release. From: jon@vcnet.com (Jon Rust) Subject: gcc part II Newsgroups: comp.sys.sgi.apps Date: Mon, 17 Jun 1996 22:25:34 -0700 Organization: IAVC Path: cygnus.com!kithrup.com!news.Stanford.EDU!agate!howland.reston.ans.net !newsfeed.internetmci.com!in1.uu.net!news.vcnet.com!jon.vc.net!user Lines: 21 Message-ID: NNTP-Posting-Host: jon.vc.net X-Newsreader: Yet Another NewsWatcher 2.2.0b4 Before I fly off the handle, I wanna make sure this is true. You can't build ***anything*** unless you fork over a huge wad of cash to SGI for their compiler and dev enviro? **If** this is true, it's horseshit. No wonder SGI is so far down the food chain in the land of UNIX. Buying SGI could be one of the biggest mistakes I've made since openning my business over 15 months ago. I wonder if my 30 days are up. Maybe I can ship it back. I only wish I'd bought [insert any other UNIX platform here]. If it's not true, could someone plz point me in the right direction to get gcc working so I can compile BIND, RADIUS, wuftpd, etc... pissed off with no build capability, jon -------------------------------------------------------- Jon Rust Internet Access of Ventura County jon@vc.net http://www.vc.net 805.383.3500 I know that gcc is not yet 6.2-friendly, but that's much more easily fixed than the library/header problem. Michael ------- End of Forwarded Message From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 10:11:31 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA04781; Tue, 18 Jun 1996 10:11:30 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA24241 for linux-list; Tue, 18 Jun 1996 17:11:26 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA24232; Tue, 18 Jun 1996 10:11:24 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA14821; Tue, 18 Jun 1996 10:10:31 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606181710.KAA14821@yon.engr.sgi.com> Subject: Re: anyone know if this is true? To: lm@neteng.engr.sgi.com (Larry McVoy) Date: Tue, 18 Jun 1996 10:10:31 -0700 (PDT) Cc: linux@cthulhu.engr.sgi.com, gcc@corp.sgi.com, tiemann@cygnus.com In-Reply-To: <199606181641.JAA03609@neteng.engr.sgi.com> from "Larry McVoy" at Jun 18, 96 09:41:47 am Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2672 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Sadly, it *is* true. I guess many more 6.2 pissed off customers are waiting down the pipeline. We can solve it by getting David Miller's development environment packaged as freeware, (it includes a GNU linker that works) and put it (really quick) outside the firewall for whoever is interested. 1) Someone with a couple of days of time needs to take this and just do it. I was planning on it, but I need another week or so to start. 2) I'm afraid we'll need to add crt[1n].o as binaries as these are *not* shipped with the headers and libraries of 6.2 Any comments, objections from anyone (especially for step 2) ? > >If it isn't true, can someone send mail to Tiemann and tell him the >facts. Sounds like we're getting bad press. > >------- Forwarded Message > >Date: Tue, 18 Jun 1996 05:22:52 -0700 >From: Michael Tiemann >To: lm@sgi.com >Subject: [comp.sys.sgi.apps] gcc part II > >Is this not fixed in 6.2? I upgraded my machine at home yesterday, and >it looked suspiciously like SGI was providing headers and libraries as >part of the std 6.2 release. > > From: jon@vcnet.com (Jon Rust) > Subject: gcc part II > Newsgroups: comp.sys.sgi.apps > Date: Mon, 17 Jun 1996 22:25:34 -0700 > Organization: IAVC > Path: cygnus.com!kithrup.com!news.Stanford.EDU!agate!howland.reston.ans.net >!newsfeed.internetmci.com!in1.uu.net!news.vcnet.com!jon.vc.net!user >Lines: 21 >Message-ID: >NNTP-Posting-Host: jon.vc.net >X-Newsreader: Yet Another NewsWatcher 2.2.0b4 > > Before I fly off the handle, I wanna make sure this is true. > > You can't build ***anything*** unless you fork over a huge wad of cash to > SGI for their compiler and dev enviro? > > **If** this is true, it's horseshit. No wonder SGI is so far down the food > chain in the land of UNIX. Buying SGI could be one of the biggest mistakes > I've made since openning my business over 15 months ago. I wonder if my 30 > days are up. Maybe I can ship it back. I only wish I'd bought [insert any > other UNIX platform here]. > > If it's not true, could someone plz point me in the right direction to get > gcc working so I can compile BIND, RADIUS, wuftpd, etc... > > pissed off with no build capability, > jon > > -------------------------------------------------------- > Jon Rust > Internet Access of Ventura County > jon@vc.net http://www.vc.net 805.383.3500 > >I know that gcc is not yet 6.2-friendly, but that's much more easily >fixed than the library/header problem. > >Michael > >------- End of Forwarded Message > -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 10:11:55 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA04792; Tue, 18 Jun 1996 10:11:54 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA24347 for linux-list; Tue, 18 Jun 1996 17:11:51 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA24341 for ; Tue, 18 Jun 1996 10:11:49 -0700 Received: from anchor.engr.sgi.com (anchor.engr.sgi.com [192.102.117.8]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA04788; Tue, 18 Jun 1996 10:11:49 -0700 Received: (from olson@localhost) by anchor.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA13973; Tue, 18 Jun 1996 10:11:49 -0700 Date: Tue, 18 Jun 1996 10:11:49 -0700 From: olson@anchor.engr.sgi.com (Dave Olson) Message-Id: <199606181711.KAA13973@anchor.engr.sgi.com> To: linux@neteng.engr.sgi.com, Larry McVoy Subject: Re: anyone know if this is true? Cc: olson@neteng.engr.sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk It's not true. All he has to do is install eoe.hdrs and compiler_eoe.hdrs. That's just the *BASE* header files. Dave Olson, Silicon Graphics Guru and busybody at large http://reality.sgi.com/olson olson@sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 10:16:14 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA04903; Tue, 18 Jun 1996 10:16:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA25475 for linux-list; Tue, 18 Jun 1996 17:16:09 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA25469 for ; Tue, 18 Jun 1996 10:16:08 -0700 Received: from storm.engr.sgi.com (storm.engr.sgi.com [192.26.79.92]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA04897; Tue, 18 Jun 1996 10:16:07 -0700 Received: by storm.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) id KAA11458; Tue, 18 Jun 1996 10:14:37 -0700 From: "Donna Yobs" Message-Id: <9606181014.ZM11456@storm.engr.sgi.com> Date: Tue, 18 Jun 1996 10:14:37 -0700 In-Reply-To: Larry McVoy "anyone know if this is true?" (Jun 18, 9:41am) References: <199606181641.JAA03609@neteng.engr.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Larry McVoy , linux@neteng.engr.sgi.com Subject: Re: anyone know if this is true? Cc: olson@neteng.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk You do get the basics with eoe: versions long eoe.hdr.lib shows what hdrs are on basic irix versions long eoe.hdr.lib|wc 283 1415 17711 both are default: eoe.hdr.lib [d] compiler_eoe.hdr.lib [d] -- ------------------------------------------------------------------------- Donna Derby Yobs Silicon Graphics - NSD yobs@engr.sgi.com Product Marketing From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 10:22:18 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA05141; Tue, 18 Jun 1996 10:22:18 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA27398 for linux-list; Tue, 18 Jun 1996 17:22:13 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA27374 for ; Tue, 18 Jun 1996 10:22:10 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA14883; Tue, 18 Jun 1996 10:21:17 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606181721.KAA14883@yon.engr.sgi.com> Subject: Re: anyone know if this is true? To: olson@anchor.engr.sgi.com (Dave Olson) Date: Tue, 18 Jun 1996 10:21:17 -0700 (PDT) Cc: linux@cthulhu.engr.sgi.com In-Reply-To: <199606181711.KAA13973@anchor.engr.sgi.com> from "Dave Olson" at Jun 18, 96 10:11:49 am Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 869 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > >It's not true. All he has to do is install eoe.hdrs and compiler_eoe.hdrs. > Dave, I'm afraid you're misinformed. The problem is real. Customers cannot build anything on 6.2 even if the install the above subsystems, unless they buy our IDO. I said it many times, to be able to build anything on 6.2 they still miss a linker (the GNU linker is not supported in any official GNU or Cygnus releases on any SGI and we don't include /usr/lib/crt[1n].o with our headers and libraries) David Miller has a heavily patched working GNU linker that creates Linux elf-32 binaries. He told me that it should be easy to make it produce native IRIX binaries. As for the crt[1n].o files I really hope they are not a problem to give away. >That's just the *BASE* header files. > This is correct. From the point of view of the original complaint Is not enough. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 10:35:29 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA05281; Tue, 18 Jun 1996 10:35:28 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA01291 for linux-list; Tue, 18 Jun 1996 17:35:24 GMT Received: from sgi.sgi.com (sgi.engr.sgi.com [192.26.80.37]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA01275; Tue, 18 Jun 1996 10:35:23 -0700 Received: from cygnus.com (cygnus.com [140.174.1.1]) by sgi.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA02315; Tue, 18 Jun 1996 10:35:20 -0700 Received: from localhost.cygnus.com (axon.cygnus.com [140.174.1.116]) by cygnus.com (8.6.12/8.6.9) with ESMTP id KAA22547; Tue, 18 Jun 1996 10:35:19 -0700 Message-Id: <199606181735.KAA22547@cygnus.com> To: ariel@cthulhu.engr.sgi.com cc: lm@neteng.engr.sgi.com (Larry McVoy), linux@cthulhu.engr.sgi.com, gcc@corp.sgi.com, tiemann@cygnus.com Subject: Re: anyone know if this is true? In-reply-to: Your message of "Tue, 18 Jun 1996 10:10:31 PDT." <199606181710.KAA14821@yon.engr.sgi.com> Date: Tue, 18 Jun 1996 10:35:19 -0700 From: Michael Tiemann Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hey Ariel, good to hear from you! It sounds to me like (1) SGI intended to make GCC a viable freeware option for Irix 6.2, (2) the support in 6.2 is not quite right, due to slight technical problems. If I understand this correctly, then I think it won't be too hard to fix the PR-related issues, and I'll be happy to chime in our support for the intended solution (whatever it may be). If SGI isn't committing to supplying a reasonable foundation to GNU (w/o ProDev or IDO), then that's another story. Michael From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 11:39:51 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA08153; Tue, 18 Jun 1996 11:39:50 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA13620 for linux-list; Tue, 18 Jun 1996 18:39:45 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA13610; Tue, 18 Jun 1996 11:39:43 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id LAA07982; Tue, 18 Jun 1996 11:39:41 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id LAA09663; Tue, 18 Jun 1996 11:39:40 -0700 Date: Tue, 18 Jun 1996 11:39:40 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606181839.LAA09663@fir.esd.sgi.com> To: ariel@cthulhu.engr.sgi.com Cc: olson@anchor.engr.sgi.com (Dave Olson), linux@cthulhu.engr.sgi.com Subject: Re: anyone know if this is true? In-Reply-To: <199606181721.KAA14883@yon.engr.sgi.com> References: <199606181711.KAA13973@anchor.engr.sgi.com> <199606181721.KAA14883@yon.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ariel Faigon writes: > > > >It's not true. All he has to do is install eoe.hdrs and compiler_eoe.hdrs. > > > Dave, I'm afraid you're misinformed. The problem is real. > Customers cannot build anything on 6.2 even if the install the above > subsystems, unless they buy our IDO. > > I said it many times, to be able to build anything on 6.2 > they still miss a linker (the GNU linker is not supported in > any official GNU or Cygnus releases on any SGI and we don't include > /usr/lib/crt[1n].o with our headers and libraries) Those files are included only in dev.sw.lib, not in irix.sw.irix_lib. I agree that they should be in the latter. ld is shipped in compiler_eoe.sw.lboot, but it is located under /usr/cpu/sysgen/root/usr/bin/. From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 16:25:00 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA18230; Tue, 18 Jun 1996 16:25:00 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA02396 for linux-list; Tue, 18 Jun 1996 23:24:54 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA02391 for ; Tue, 18 Jun 1996 16:24:52 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA15589; Tue, 18 Jun 1996 16:23:57 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606182323.QAA15589@yon.engr.sgi.com> Subject: gcc solution looks plausible (was: anyone know if this is true?) To: olson@anchor.engr.sgi.com (Dave Olson) Date: Tue, 18 Jun 1996 16:23:56 -0700 (PDT) Cc: gcc@corp.sgi.com, linux@cthulhu.engr.sgi.com In-Reply-To: <199606182106.OAA15730@anchor.engr.sgi.com> from "Dave Olson" at Jun 18, 96 02:06:24 pm Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 973 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk [I'm Ccing gcc@corp and linux@engr, some more people may be happy to hear this] Dave Olson wrote to me about 'ld': > >The one in /var/sysgen/root is the same one that driverwrap invokes. > >There are two ld's, the one in usr/lib, and the one in usr/bin. They >are different. There is a one to one match between /usr/bin/ld and >/var/sysgen/root/usr/bin/ld, and similarly for /usr/lib/ld and >/var/sysgen/root/ld > >(assuming a 32 bit system) > Thanks! that's encouraging. I assume this means that I should install two symlinks: /usr/freeware/bin/ld -> /var/sysgen/root/usr/bin/ld /usr/freeware/lib/gcc-lib/mips-sgi-irixX.Y/2.7.2/ld -> /var/sysgen/root/ld Or something close to this. This plus building gcc -with-gnu-as, using -32 -old_ld in the specs file and Bean's permission to package crt[1n].o should solve all the problems I'm aware of and make many customers happy. That was very helpful. Looks like a solution is close. Thanks again. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Thu Jun 20 04:03:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA27017; Thu, 20 Jun 1996 04:03:16 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id LAA24827 for linux-list; Thu, 20 Jun 1996 11:03:06 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA24816 for ; Thu, 20 Jun 1996 04:03:05 -0700 Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA27014 for ; Thu, 20 Jun 1996 04:03:02 -0700 Received: by soyuz.wellington.sgi.com (951211.SGI.8.6.12.PATCH1042/940406.SGI) for linux@neteng.engr.sgi.com id XAA02623; Thu, 20 Jun 1996 23:02:59 +1200 From: alambie@wellington.sgi.com (Alistair Lambie) Message-Id: <199606201102.XAA02623@soyuz.wellington.sgi.com> Subject: Kernel doesn't work on 200MHz Indy To: linux@neteng.engr.sgi.com Date: Thu, 20 Jun 1996 23:02:58 +1200 (NZT) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 694 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Just incase anyone is interested: I was able to boot Davids kernel on my Indy when I only had a 100MHz R4600PC, but know I've upgraded to a 200MHz R4400SC it dies! Looks like something to do with the memory controller... Here goes a bit of what comes out: Bad pmd in pte_alloc_kernel: 00000000 Double fault caused by invalid entries in pgd: Double fault address : ffffffffe4000000 c0_epc : ffffffff88093ebc Of course there was heaps more, but I couldn't get cut and paste to work :-) I haven't had time to have a look at what's going on yet. Cheers, Alistair PS - It only gives a BogoMIPS reading of 103.63, which is around what I got when it was a 100MHz chip. From owner-linux@cthulhu.engr.sgi.com Thu Jun 20 11:12:30 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA01257; Thu, 20 Jun 1996 11:12:29 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA16912 for linux-list; Thu, 20 Jun 1996 18:12:23 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA16875 for ; Thu, 20 Jun 1996 11:12:20 -0700 Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA01241 for ; Thu, 20 Jun 1996 11:12:19 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id LAA24562; Thu, 20 Jun 1996 11:12:19 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id LAA24532; Thu, 20 Jun 1996 11:12:17 -0700 Date: Thu, 20 Jun 1996 11:12:17 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606201812.LAA24532@fir.esd.sgi.com> To: alambie@wellington.sgi.com (Alistair Lambie) Cc: linux@neteng.engr.sgi.com Subject: Re: Kernel doesn't work on 200MHz Indy In-Reply-To: <199606201102.XAA02623@soyuz.wellington.sgi.com> References: <199606201102.XAA02623@soyuz.wellington.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Alistair Lambie writes: > Just incase anyone is interested: > > I was able to boot Davids kernel on my Indy when I only had a 100MHz R4600PC, > but know I've upgraded to a 200MHz R4400SC it dies! Looks like something > to do with the memory controller... There is no way the kernel could work on an R4000 or R4400 without changes to the cache routines, as well as the addition of certain workarounds for processor errata. Stick to R4600 and R5000 processors for the time being. I asked David to start with the R4600, because the workarounds for the errata are far simpler, and because it and the R5000 are the volume processors for Indy. It will not be all that hard to add R4000 and R4400 support, but there are several messy workarounds to implement, so it is more interesting to get a complete system working on an R4600 or R5000. ... > PS - It only gives a BogoMIPS reading of 103.63, which is around what I got > when it was a 100MHz chip. That is to be expected. BogoMIPS is essentiall 2 times the number of times one can execute a loop like this: la a0,0x7FFFFFFF 1: bltz a0,1b addu a0,-1 On an R3000, R4600, or R5000, the branch executes in two cycles (counting one for the branch delay slot), so BogoMIPS equals the processor clock rate. On an R4000 or R4400, the branch executes in four cycles (counting one for the branch delay slot), so BogoMIPS equals one half the processor clock rate. There appears to be a small error in the current logic for calibrating the processor clock rate, which accounts for the BogoMIPS being 103.63 instead of 100.00. From owner-linux@cthulhu.engr.sgi.com Fri Jun 21 00:49:05 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA06976; Fri, 21 Jun 1996 00:49:05 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA27055 for linux-list; Fri, 21 Jun 1996 07:49:00 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA27050 for ; Fri, 21 Jun 1996 00:48:58 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA06968; Fri, 21 Jun 1996 00:48:58 -0700 Date: Fri, 21 Jun 1996 00:48:58 -0700 Message-Id: <199606210748.AAA06968@neteng.engr.sgi.com> From: "David S. Miller" To: wje@fir.esd.sgi.com CC: alambie@wellington.sgi.com, linux@neteng.engr.sgi.com In-reply-to: <199606201812.LAA24532@fir.esd.sgi.com> (wje@fir.esd.sgi.com) Subject: Re: Kernel doesn't work on 200MHz Indy Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Thu, 20 Jun 1996 11:12:17 -0700 From: wje@fir.esd.sgi.com (William J. Earl) There is no way the kernel could work on an R4000 or R4400 without changes to the cache routines, as well as the addition of certain workarounds for processor errata. Stick to R4600 and R5000 processors for the time being. I asked David to start with the R4600, because the workarounds for the errata are far simpler, and because it and the R5000 are the volume processors for Indy. It will not be all that hard to add R4000 and R4400 support, but there are several messy workarounds to implement, so it is more interesting to get a complete system working on an R4600 or R5000. Heh, I go the the UK and people are trying my kernel out all over the place. This is good. I will work on the issues necessary for R4[40]00 processor support certainly. Take note that I worked to get a shell prompt on my target machine "by all means necessary" as quickly as possible so that I could have an early proof of concept to show everyone. With this there are some hard coded items in the tree that need to be attended to, but I should be able to get it all to work. One notable thing is that machines not equipped with NEWPORT graphics cards, and instead possess an INDY with the older EXPRESS graphics card, will not be able to get things working until I get the serial console up or I write a driver for the EXPRESS. Both will happen in due time. As you can see I am back from the UK, and will try to get back on track this weekend. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sat Jun 22 20:19:58 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA13640; Sat, 22 Jun 1996 20:19:58 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id DAA22390 for linux-list; Sun, 23 Jun 1996 03:19:17 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA22384 for ; Sat, 22 Jun 1996 20:19:15 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA13617; Sat, 22 Jun 1996 20:19:15 -0700 Date: Sat, 22 Jun 1996 20:19:15 -0700 Message-Id: <199606230319.UAA13617@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: what I am up to... Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I've just checked in last night an initial serial driver for the INDY. Since this machine (as do some other SGI's) have the Zilog85C30 on board, I just took my Sparc driver and hacked it a little. Currently it works well as the console, and some initial tests with KGDB show that it is ok for the KGDB packets as well. KGDB needs some work on the host end of things before I can use it very much. I'm cleaning up the source tree. The end result will hopefully be a single kernel which can work flawlessly on any Mips CPU variant. I know what need to be done for this to work. In the end the goal is to be able to fire up the same Linux kernel on _any_ SGI piece of hardware and it just works, just like the Sparc kernel does. More to come... Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 24 05:25:27 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id FAA18489; Mon, 24 Jun 1996 05:25:26 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id MAA04132 for linux-list; Mon, 24 Jun 1996 12:25:19 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id FAA04127 for ; Mon, 24 Jun 1996 05:25:18 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA18480; Mon, 24 Jun 1996 05:25:17 -0700 Date: Mon, 24 Jun 1996 05:25:17 -0700 Message-Id: <199606241225.FAA18480@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: R4k taglo/taghi hardware bugs^H^H^H^Hfeatures? Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Are there any known problems with the taglo/taghi registers showing what they should after "indexed load tag secondary" cache instructions? Whatever is in both registers before the cache instruction, is still in there afterwards... I've also tried the primary-data and primary-instruction variants of the cache operations and still same results. I don't know, but it is so nice how the primary cache sizes are stored in well defined config registers in CP0, yet the secondary cache needs to be sized by complete magic and diagnostic mechanisms. The CPU knows the size of the secondary cache lines, why so difficult to put the secondary cache total size somewhere similar? (for those of you playing at home, yes I know the R5k Triton does this in the CP0 config register, but all other R4k variants do not) I've been up all night trying to figure out what (isn't) happening... Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 24 15:44:56 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA13863; Mon, 24 Jun 1996 15:44:56 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA29789 for linux-list; Mon, 24 Jun 1996 22:44:50 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA29784 for ; Mon, 24 Jun 1996 15:44:49 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA24773 for linux; Mon, 24 Jun 1996 15:43:51 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606242243.PAA24773@yon.engr.sgi.com> Subject: External Linux/MIPS list To: linux@yon.engr.sgi.com Date: Mon, 24 Jun 1996 15:43:51 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2697 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk In order to prevent confidential data leaks (like random mentions of Speedracer or Lego), and in order to build critical-mass support to the Linux port outside SGI. I have created a separate linux mailing list for non-SGI interested parties. It seems that there is a lot of interest outside SGI from people who may be important assets for the Linux/MIPS effort in the future. People who sell Linux CDROMs, talented developers, etc. I enclose the welcome message for your reference. if you feel you know someone nice outside who you think should be on this list (and they agree) just subscribe them by mailing to: external-majordomo@postofc.corp.sgi.com with body: subscribe linuxmips their@email.address Once we have enough people on that list, I will send a short summary of the current status to them. Please: 1) Don't mix between linux@engr (our internal list) and linuxmips@corp (free for all) [The list-names are different on purpose.] 2) Feel free to Cc linuxmips@corp on any message that doesn't contain SGI confidential data. -- Peace, Ariel ----- Forwarded message from MAILMAN@palladium.corp.sgi.com ----- >From owner-linuxmips-outgoing@palladium.corp.sgi.com Mon Jun 24 15:25:28 1996 Date: Mon, 24 Jun 1996 15:26:21 -0700 Message-Id: <199606242226.PAA11036@palladium.corp.sgi.com> To: linuxmips@palladium.corp.sgi.com Subject: Welcome to linuxmips From: MAILMAN@palladium.corp.sgi.com Sender: owner-linuxmips@palladium.corp.sgi.com Precedence: bulk Reply-To: MAILMAN@palladium.corp.sgi.com Welcome to the linuxmips mailing list! To unsubscribe from this list send email to: external-majordomo@postofc.corp.sgi.com with the following line in the _body_ of the message: unsubscribe linuxmips _your_email_address_here_ To post a message to this mailing list use this address: linuxmips@postofc.corp.sgi.com Here's some general information for the linuxmips mailing list: Welcome to the linuxmips mailing list ! linuxmips@corp.sgi.com linuxmips will be used to update interested parties not affiliated with SGI on the status of the ongoing Linux/MIPS port within SGI. Thanks to the Linux/MIPS effort going on in Germany (thanks guys!) and to David Miller's summer's internship at SGI we expect Linux soon to be running on many SGI platforms and be able to run IRIX binaries. We intend to release the port under the GPL as a part of mainstream Linux and hope that other Linux/MIPS enthusiasts will join the effort once the first step is done and released to the net. Feel free to tell your friends about this list. -- Ariel (ariel@sgi.com) ----- End of forwarded message from MAILMAN@palladium.corp.sgi.com ----- From owner-linux@cthulhu.engr.sgi.com Mon Jun 24 18:35:45 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA18378; Mon, 24 Jun 1996 18:35:45 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA00738 for linux-list; Tue, 25 Jun 1996 01:35:40 GMT Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA00723 for ; Mon, 24 Jun 1996 18:35:37 -0700 Received: from windy.wellington.sgi.com by soyuz.wellington.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/940406.SGI) for id NAA03612; Tue, 25 Jun 1996 13:35:34 +1200 Received: (alambie@localhost) by windy.wellington.sgi.com (950413.SGI.8.6.12/8.6.9) id NAA02028 for linux@engr; Tue, 25 Jun 1996 13:35:33 +1200 From: "Alistair Lambie" Message-Id: <9606251335.ZM2026@windy.wellington.sgi.com> Date: Tue, 25 Jun 1996 13:35:33 +0000 X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: linux@cthulhu.engr.sgi.com Subject: Userland binaries Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Being miles away in New Zealand it is kind of hard to know who is doing what! I have been playing around with cross compiling userland binaries. But before I get carried away here are some questions: 1. Is anyone already doing this? 2. Should we set up a repository so we don't all spend our time doing the same thing? 3. I have used the the cross compiler from ftp.fnet.fr. The libc I have used is the gnu one that has just appeared on ftp.fnet.fr in the last week. Are these the right ones to be using (they only allow static linking)? 4. If several people are doing this maybe we should coordinate the effort so we don't all do the same packages. That should be enough questions for this week :-) Cheers, Alistair -- Alistair Lambie alambie@wellington.sgi.com Silicon Graphics New Zealand SGI Voicemail: 56791 Level 5, Walsh Wrightson Tower, Ph: +64-4-802 1455 94-96 Dixon St, Wellington, NZ Fax: +64-4-802 1459 From owner-linux@cthulhu.engr.sgi.com Tue Jun 25 06:44:36 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id GAA06332; Tue, 25 Jun 1996 06:44:35 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id NAA20004 for linux-list; Tue, 25 Jun 1996 13:44:31 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id GAA19995 for ; Tue, 25 Jun 1996 06:44:29 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id GAA06325; Tue, 25 Jun 1996 06:44:15 -0700 Date: Tue, 25 Jun 1996 06:44:15 -0700 Message-Id: <199606251344.GAA06325@neteng.engr.sgi.com> From: "David S. Miller" To: alambie@wellington.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <9606251335.ZM2026@windy.wellington.sgi.com> (alambie@wellington.sgi.com) Subject: Re: Userland binaries Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: "Alistair Lambie" Date: Tue, 25 Jun 1996 13:35:33 +0000 Being miles away in New Zealand it is kind of hard to know who is doing what! I wasn't far from there last week ;-) (for those who do not know I gave two talks in Manchester England last week) I have been playing around with cross compiling userland binaries. But before I get carried away here are some questions: 1. Is anyone already doing this? Not that I know of. 2. Should we set up a repository so we don't all spend our time doing the same thing? Good idea. 3. I have used the the cross compiler from ftp.fnet.fr. The libc I have used is the gnu one that has just appeared on ftp.fnet.fr in the last week. Are these the right ones to be using (they only allow static linking)? This should be correct. That libc snapshot probably only does static binaries, the developers have initial 'hello world' type shared binaries working from what I hear so expect some more about this soon. I'll update the list on any progress on shared libraries I hear about myself. 4. If several people are doing this maybe we should coordinate the effort so we don't all do the same packages. Another good idea. ;-) Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Thu Jun 27 15:47:52 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA06305; Thu, 27 Jun 1996 15:47:51 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA13235 for linux-list; Thu, 27 Jun 1996 22:47:46 GMT Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA13222 for ; Thu, 27 Jun 1996 15:47:42 -0700 Received: from windy.wellington.sgi.com by soyuz.wellington.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/940406.SGI) id KAA02245; Fri, 28 Jun 1996 10:47:44 +1200 Received: (alambie@localhost) by windy.wellington.sgi.com (950413.SGI.8.6.12/8.6.9) id KAA04678; Fri, 28 Jun 1996 10:47:43 +1200 From: "Alistair Lambie" Message-Id: <9606281047.ZM4676@windy.wellington.sgi.com> Date: Fri, 28 Jun 1996 10:47:42 +0000 In-Reply-To: "David S. Miller" "Re: Userland binaries" (Jun 26, 1:44am) References: <199606251344.GAA06325@neteng.engr.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: dm@sgi.com, alambie@wellington.sgi.com Subject: Re: Userland binaries Cc: linux@cthulhu.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Jun 26, 1:44am, David S. Miller wrote: > Subject: Re: Userland binaries > From: "Alistair Lambie" > Date: Tue, 25 Jun 1996 13:35:33 +0000 > > Being miles away in New Zealand it is kind of hard to know who is > doing what! > > I wasn't far from there last week ;-) (for those who do not know I > gave two talks in Manchester England last week) > Yeah...only another 24 hours flying and you too could have been here. > I have been playing around with cross compiling userland binaries. > But before I get carried away here are some questions: > > 1. Is anyone already doing this? > > Not that I know of. > Judging by the resounding silence I guess you are correct! > 2. Should we set up a repository so we don't all spend our time > doing the same > thing? > > Good idea. > Can someone point me at a place (I could host here, but it seems crazy for everyone to try suck everything up a 64k pipe...of course this assumes that people are actually interested!!). > 4. If several people are doing this maybe we should coordinate the > effort so > we don't all do the same packages. > > Another good idea. ;-) So far I've done sh-utils and file-utils. Next I'm planning on SYSVinit and whatever packages have getty/login/security. Then some more shells and an editor. I guess after that the next thing might be some of the networking stuff. I'm using the RedHat SRPMS for this, and applying their patches unless they are platform specific. Does anyone have any wild objections to this? Also, what format would people prefer for packages...just tar.gz or RPM? (guess this also raises the point that I need to do some binaries to deal with however we package things!) Cheers, Alistair -- Alistair Lambie alambie@wellington.sgi.com Silicon Graphics New Zealand SGI Voicemail: 56791 Level 5, Walsh Wrightson Tower, Ph: +64-4-802 1455 94-96 Dixon St, Wellington, NZ Fax: +64-4-802 1459 From owner-linux@cthulhu.engr.sgi.com Sat Jun 29 00:07:58 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA17310; Sat, 29 Jun 1996 00:07:58 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA04533 for linux-list; Sat, 29 Jun 1996 07:07:54 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA04526 for ; Sat, 29 Jun 1996 00:07:52 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA17304; Sat, 29 Jun 1996 00:07:52 -0700 Date: Sat, 29 Jun 1996 00:07:52 -0700 Message-Id: <199606290707.AAA17304@neteng.engr.sgi.com> From: "David S. Miller" To: linux@neteng.engr.sgi.com Subject: NIS rarpd entries Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk When I'm booting my test box I have to run a bogus hacked up copy of rarpd because the NIS maps in my domain don't have an ethers entry for stacey.engr What is a better way of dealing with this? Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sat Jun 29 18:27:31 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA26278; Sat, 29 Jun 1996 18:27:31 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA04482 for linux-list; Sun, 30 Jun 1996 01:27:26 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA04477 for ; Sat, 29 Jun 1996 18:27:24 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA01788; Sat, 29 Jun 1996 18:26:23 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606300126.SAA01788@yon.engr.sgi.com> Subject: NIS rarpd entries (fwd) To: dpinto@yon.engr.sgi.com (Demetrio Pinto) Date: Sat, 29 Jun 1996 18:26:23 -0700 (PDT) Cc: linux@cthulhu.engr.sgi.com Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 813 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Demetrio, Will it be possible to add an ethers entry for stacey.engr to our ypmaps ? Thanks! If yes, David, could you send Demetrio the ethernet address ? ----- Forwarded message from David S. Miller ----- >From owner-linux@cthulhu Sat Jun 29 00:07:01 1996 Date: Sat, 29 Jun 1996 00:07:52 -0700 Message-Id: <199606290707.AAA17304@neteng.engr.sgi.com> From: "David S. Miller" To: linux@neteng Subject: NIS rarpd entries Reply-to: dm@sgi.com Sender: owner-linux@cthulhu Precedence: bulk When I'm booting my test box I have to run a bogus hacked up copy of rarpd because the NIS maps in my domain don't have an ethers entry for stacey.engr What is a better way of dealing with this? Later, David S. Miller dm@sgi.com ----- End of forwarded message from David S. Miller ----- -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Sat Jun 29 22:39:46 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA16738; Sat, 29 Jun 1996 22:39:46 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA23565 for linux-list; Sun, 30 Jun 1996 05:39:41 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA23560; Sat, 29 Jun 1996 22:39:39 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA16730; Sat, 29 Jun 1996 22:39:38 -0700 Date: Sat, 29 Jun 1996 22:39:38 -0700 Message-Id: <199606300539.WAA16730@neteng.engr.sgi.com> From: "David S. Miller" To: ariel@cthulhu.engr.sgi.com CC: dpinto@yon.engr.sgi.com, linux@cthulhu.engr.sgi.com In-reply-to: <199606300126.SAA01788@yon.engr.sgi.com> (ariel@yon) Subject: Re: NIS rarpd entries (fwd) Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: ariel@yon (Ariel Faigon) Date: Sat, 29 Jun 1996 18:26:23 -0700 (PDT) Will it be possible to add an ethers entry for stacey.engr to our ypmaps ? Thanks! If yes, David, could you send Demetrio the ethernet address ? 8:0:69:8:8a:18 stacey.engr.sgi.com Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jul 1 05:29:52 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id FAA11470; Mon, 1 Jul 1996 05:29:52 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id MAA06255 for linux-list; Mon, 1 Jul 1996 12:28:22 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id FAA06250 for ; Mon, 1 Jul 1996 05:28:20 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA11437; Mon, 1 Jul 1996 05:28:20 -0700 Date: Mon, 1 Jul 1996 05:28:20 -0700 Message-Id: <199607011228.FAA11437@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: wheee, irix binaries... Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Well, it at least appears that I have a stock IRIX 'sed' binary working. The initial framework for IRIX syscall compatability is in the tree now and I will just whack away at this until most 'reasonable' binaries work. For those who are wondering, sproc() shouldn't even be that hard believe it or not, in fact I am told someone out there in linux land has already written the kernel code for preliminary support. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jul 1 11:04:42 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA26346; Mon, 1 Jul 1996 11:04:41 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA10735 for linux-list; Mon, 1 Jul 1996 18:03:04 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA10717 for ; Mon, 1 Jul 1996 11:03:03 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id LAA26269; Mon, 1 Jul 1996 11:03:02 -0700 Message-Id: <199607011803.LAA26269@neteng.engr.sgi.com> To: dm@sgi.com From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: linux@cthulhu.engr.sgi.com Subject: Re: wheee, irix binaries... Date: Mon, 01 Jul 1996 11:03:02 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : For those who are wondering, sproc() shouldn't even be that hard : believe it or not, in fact I am told someone out there in linux land : has already written the kernel code for preliminary support. Linus already has something called "clone" which is quite similar to sproc(). Somebody did the arg swizlling so that most sproced stuff works. From owner-linux@cthulhu.engr.sgi.com Mon Jul 1 11:27:45 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA27363; Mon, 1 Jul 1996 11:27:44 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA17331 for linux-list; Mon, 1 Jul 1996 18:26:25 GMT Received: from demi.engr.sgi.com (demi.engr.sgi.com [150.166.61.27]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA17316; Mon, 1 Jul 1996 11:26:24 -0700 Received: (from dpinto@localhost) by demi.engr.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) id LAA03874; Mon, 1 Jul 1996 11:26:23 -0700 From: "Demetrio Pinto" Message-Id: <9607011126.ZM3872@demi.engr.sgi.com> Date: Mon, 1 Jul 1996 11:26:23 -0700 In-Reply-To: ariel@yon (Ariel Faigon) "NIS rarpd entries (fwd)" (Jun 29, 6:26pm) References: <199606300126.SAA01788@yon.engr.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: ariel@cthulhu.engr.sgi.com Subject: Re: NIS rarpd entries (fwd) Cc: dpinto@yon.engr.sgi.com (Demetrio Pinto), linux@cthulhu.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ariel, David, On Jun 29, 6:26pm, Ariel Faigon wrote: > Subject: NIS rarpd entries (fwd) > Demetrio, > > Will it be possible to add an ethers entry for stacey.engr > to our ypmaps ? stacey is ALREADY in the YP hosts maps demi 39# ypmatch stacey.engr hosts 150.166.75.5 stacey.engr.sgi.com demi 40# (BTW, 150.166.75 is one of the NetWork Group nets.) > Thanks! > > If yes, David, could you send Demetrio the ethernet address ? > > > ----- Forwarded message from David S. Miller ----- > > >From owner-linux@cthulhu Sat Jun 29 00:07:01 1996 > Date: Sat, 29 Jun 1996 00:07:52 -0700 > Message-Id: <199606290707.AAA17304@neteng.engr.sgi.com> > From: "David S. Miller" > To: linux@neteng > Subject: NIS rarpd entries > Reply-to: dm@sgi.com > Sender: owner-linux@cthulhu > Precedence: bulk > > > When I'm booting my test box I have to run a bogus hacked up copy of > rarpd because the NIS maps in my domain don't have an ethers entry for > stacey.engr This is from your system tanya 2% ypmatch stacey hosts 150.166.75.5 stacey.engr.sgi.com stacey tanya 3% Demetrio > > What is a better way of dealing with this? > > Later, > David S. Miller > dm@sgi.com > > ----- End of forwarded message from David S. Miller ----- > > -- > Peace, Ariel >-- End of excerpt from Ariel Faigon From owner-linux@cthulhu.engr.sgi.com Mon Jul 1 11:48:34 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA28143; Mon, 1 Jul 1996 11:48:34 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA23066 for linux-list; Mon, 1 Jul 1996 18:48:29 GMT Received: from demi.engr.sgi.com (demi.engr.sgi.com [150.166.61.27]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA23035; Mon, 1 Jul 1996 11:48:25 -0700 Received: (from dpinto@localhost) by demi.engr.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) id LAA03934; Mon, 1 Jul 1996 11:48:19 -0700 From: "Demetrio Pinto" Message-Id: <9607011148.ZM3932@demi.engr.sgi.com> Date: Mon, 1 Jul 1996 11:48:18 -0700 In-Reply-To: "David S. Miller" "Re: NIS rarpd entries (fwd)" (Jun 29, 10:39pm) References: <199606300539.WAA16730@neteng.engr.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: dm@sgi.com, ariel@cthulhu.engr.sgi.com Subject: Re: NIS rarpd entries (fwd) Cc: dpinto@yon.engr.sgi.com, linux@cthulhu.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David, Added cthulhu 22% grep stacey ethers 8:0:69:8:8a:18 stacey cthulhu 23% Give it about 15 vminutes to propagate. Demetrio PS Please disregard my previous mail. I am not complety awake. On Jun 29, 10:39pm, David S. Miller wrote: > Subject: Re: NIS rarpd entries (fwd) > From: ariel@yon (Ariel Faigon) > Date: Sat, 29 Jun 1996 18:26:23 -0700 (PDT) > > Will it be possible to add an ethers entry for stacey.engr > to our ypmaps ? Thanks! > > If yes, David, could you send Demetrio the ethernet address ? > > 8:0:69:8:8a:18 stacey.engr.sgi.com > > Later, > David S. Miller > dm@sgi.com >-- End of excerpt from David S. Miller From owner-linux@cthulhu.engr.sgi.com Mon Jul 1 15:13:49 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA24213; Mon, 1 Jul 1996 15:13:49 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA19372 for linux-list; Mon, 1 Jul 1996 22:13:44 GMT Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA19365 for ; Mon, 1 Jul 1996 15:13:40 -0700 Received: from windy.wellington.sgi.com by soyuz.wellington.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/940406.SGI) for id KAA02362; Tue, 2 Jul 1996 10:13:24 +1200 Received: (alambie@localhost) by windy.wellington.sgi.com (950413.SGI.8.6.12/8.6.9) id KAA01446 for linux@engr; Tue, 2 Jul 1996 10:13:23 +1200 From: "Alistair Lambie" Message-Id: <9607021013.ZM1444@windy.wellington.sgi.com> Date: Tue, 2 Jul 1996 10:13:22 +0000 X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: linux@cthulhu.engr.sgi.com Subject: (Fwd) Re: SGI/MIPS Linux port status Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Folks, I ping'ed Ralf about shared GNU libc for big endian machines. At the end of his reply he asks for some info to help him. I'm not sure if he is on the list of blessed people or not, and I suspect there are some others who would be far more able to answer his question than myself. Can someone follow this up.....(Ariel, Larry, Bill ???) Cheers, Alistair --- Forwarded mail from Ralf Baechle From: Ralf Baechle Subject: Re: SGI/MIPS Linux port status To: alambie@wellington.sgi.com (Alistair Lambie) Date: Mon, 1 Jul 1996 23:54:00 +0200 (MET DST) Hi, > > The even better news is that I've started to rebuild my entire system > > using ELF shared libraries. I'll try to make first alpha release of > > shared library binaries tomorrow for little endian binaries (the above > > mentioned machines are all little endian); I'll try to generate big > > endian libs as soon as possible. > > > I have been building up a core set of binaries for us to use on the SGI boxes. > These are of course big endian, and naturally HUGE because they are statically > linked! I know how big your binaries are - after all I'm still using a mostly static linked system also. So I assume that your /bin/ls is also about 15 times the size of the i486-linux shared /bin/ls ... Can you let me know when you have big endian shared libs so I can have > something a little more sane to deal with. I'm rebulding my entire toolchain for big endian. This night I should find the time to rebuild the libs, also. > BTW, I assume that you are using GNU libc? Yes, I'm using GNU libc snapshot 960619. Linux libc is lacking tons of code required for MIPS fp support. The problem is simply that MIPS only has the capabilities to add, subtract, multiply and divide in hardware, some FPUs can do sqrt() while Intel/68881/68882 can do many complex computations in hardware. Also HJ's way to maintain the code and the code itself made it a bit of a pain to use Linux libc ... On which libc is your SGI stuff based? Also I'm trying to make my work as SGI-ish as possible. I don't have access to a SGI or documentation but have some questions about IRIX regarding the shared lib stuff, PIC code and more. Can you help me? Happy hacking, Ralf ---End of forwarded mail from Ralf Baechle -- Alistair Lambie alambie@wellington.sgi.com Silicon Graphics New Zealand SGI Voicemail: 56791 Level 5, Walsh Wrightson Tower, Ph: +64-4-802 1455 94-96 Dixon St, Wellington, NZ Fax: +64-4-802 1459 From owner-linux@cthulhu.engr.sgi.com Wed Jul 3 17:27:39 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA14416; Wed, 3 Jul 1996 17:27:39 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA10041 for linux-list; Thu, 4 Jul 1996 00:27:35 GMT Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA10007 for ; Wed, 3 Jul 1996 17:27:24 -0700 Received: from windy.wellington.sgi.com by soyuz.wellington.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/940406.SGI) for id MAA03745; Thu, 4 Jul 1996 12:26:57 +1200 Received: (alambie@localhost) by windy.wellington.sgi.com (950413.SGI.8.6.12/8.6.9) id MAA01564 for linux@engr; Thu, 4 Jul 1996 12:26:56 +1200 From: "Alistair Lambie" Message-Id: <9607041226.ZM1562@windy.wellington.sgi.com> Date: Thu, 4 Jul 1996 12:26:56 +0000 X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: linux@cthulhu.engr.sgi.com Subject: (Fwd) Libraries uploaded Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David, Looks like the new GNU libc stuff needs a newer kernel. Do you have any plans to roll to a later one in the near future? Cheers, Alistair --- Forwarded mail from Systemkennung Linux From: Systemkennung Linux Subject: Libraries uploaded To: linux-mips@fnet.fr, linuxmips@palladium.corp.sgi.com Date: Wed, 3 Jul 1996 15:45:53 +0200 (MET DST) Reply-To: Systemkennung Linux -----BEGIN PGP SIGNED MESSAGE----- Hi all, I've uploaded the first shared library binaries for Linux/MIPS to ftp.fnet.fr where they'll appear in /linux-mips/ as soon as someone has moved them online. The binaries are based on GNU libc snapshot 960619. In order to use these libraries you also have to: - Run Linux/MIPS kernel version 2.0.1 or newer. I'll upload this one rsn. - Install new binutils and GCC. These are yet unreleased; I'll release the patches rsn. This is necessary even if you link your programs static only because on MIPS even the static archives contain PIC code which the current binutils can't handle. The dynamic linker clearly still has alpha status; expect to see all sorts of bugs. The little endian binaries are those that I use on my system. I provide the big endian binaries untested and in the hope that they'll be usefull. Ralf e015d5d14cd2d9d38c30a01eafc6628f mips-linuxelf/libc-960619-2.tar.gz c23155bfbb0a62a119cc2ffae9d54b50 mipsel-linuxelf/libc-960619-2.tar.gz -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAgUBMdp5jUckbl6vezDBAQFqQgP/Vla+a6jK9D5A6xReNq2jTwI0HZdaAI1U qKQIfq2Q7sSOau4liKpxSTsIg92MG5nmKy4k1lJNAWW0sUwsWFs+JBN1/h7kggcb 2CufsNMju0K5le257ykGe5BmVK27tNzC/SibAU8LVfV2+AehBN+VTdZAAbxWxsnn 7vvgro2IXCg= =uDU6 -----END PGP SIGNATURE----- ---End of forwarded mail from Systemkennung Linux -- Alistair Lambie alambie@wellington.sgi.com Silicon Graphics New Zealand SGI Voicemail: 56791 Level 5, Walsh Wrightson Tower, Ph: +64-4-802 1455 94-96 Dixon St, Wellington, NZ Fax: +64-4-802 1459 From owner-linux@cthulhu.engr.sgi.com Wed Jul 3 17:29:34 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA14655; Wed, 3 Jul 1996 17:29:34 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA10330 for linux-list; Thu, 4 Jul 1996 00:29:30 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA10318 for ; Wed, 3 Jul 1996 17:29:29 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA14541; Wed, 3 Jul 1996 17:29:12 -0700 Date: Wed, 3 Jul 1996 17:29:12 -0700 Message-Id: <199607040029.RAA14541@neteng.engr.sgi.com> From: "David S. Miller" To: alambie@wellington.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <9607041226.ZM1562@windy.wellington.sgi.com> (alambie@wellington.sgi.com) Subject: Re: (Fwd) Libraries uploaded Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: "Alistair Lambie" Date: Thu, 4 Jul 1996 12:26:56 +0000 Looks like the new GNU libc stuff needs a newer kernel. Do you have any plans to roll to a later one in the near future? I'll perform a full merge this evening, will certainly be more fun than IRIX syscall compatability stuff I am working on now ;-) Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sun Jul 7 21:27:00 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id VAA19021; Sun, 7 Jul 1996 21:27:00 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id EAA04264 for linux-list; Mon, 8 Jul 1996 04:26:56 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id VAA04259 for ; Sun, 7 Jul 1996 21:26:54 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id VAA19016; Sun, 7 Jul 1996 21:26:54 -0700 Date: Sun, 7 Jul 1996 21:26:54 -0700 Message-Id: <199607080426.VAA19016@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: working strace for IRIX6 Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I've hacked up the strace source so that it works under IRIX6.* ... took me all of 15 minutes to get working, it is just that I thought someone else was working on it so I haven't bothered to look at it until today. You can snag a binary from: /hosts/neteng/usr/people/dm/bin/strace and source from: /hosts/neteng/usr/people/dm/src/strace-3.0.14 As with anything else, it is being kept under CVS revision control on tanya.engr.sgi.com:/cvs, source directory name is 'strace' with version and vendor tag of STRACE_SGI. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Jul 9 21:52:33 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id VAA21779; Tue, 9 Jul 1996 21:52:33 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id EAA10731 for linux-list; Wed, 10 Jul 1996 04:51:14 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id VAA10724 for ; Tue, 9 Jul 1996 21:51:13 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id VAA21507; Tue, 9 Jul 1996 21:51:12 -0700 Date: Tue, 9 Jul 1996 21:51:12 -0700 Message-Id: <199607100451.VAA21507@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: wheee, good news.... Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I just successfully built a Linux kernel on an INDY under Linux itself. All of the build tools and the shell were GNU utilities, but were IRIX binaries. It took some hacking, and I had to type make a few times becuase the compiler would crash here and there, but it did work. To test how well it went I then proceeded to boot the INDY using the Linux kernel it had just built for itself, and it worked! ;-) SCSI driver is next... Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Thu Jul 11 02:30:11 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA10976; Thu, 11 Jul 1996 02:30:10 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id JAA09205 for linux-list; Thu, 11 Jul 1996 09:30:06 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA09199 for ; Thu, 11 Jul 1996 02:30:04 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id CAA10970; Thu, 11 Jul 1996 02:30:04 -0700 Date: Thu, 11 Jul 1996 02:30:04 -0700 Message-Id: <199607110930.CAA10970@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: wheeee... Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk >> bootp()tanya:vmlinux Obtaining vmlinux from server tanya PROMLIB: SGI ARCS firmware Version 1 Revision 10 PROMLIB: Total free ram 65269760 bytes (63740K,62MB) Primary ICACHE 16K (linesize 32 bytes) Primary DCACHE 16K (linesize 32 bytes) R4600/R5000 SCACHE size 512K linesize 32 bytes ARCH: SGI-IP22 CPU: MIPS-R4600 FPU ICACHE DCACHE SCACHE MC: SGI memory controller Revision 3 calculating r4koff... 000a87b4(690100) get_zs: Returning bfbd9830 zs0: console input zs0: console I/O Calibrating delay loop.. ok - 137.63 BogoMIPS Memory: 60624k/196604k available (740k kernel code, 2980k data) Swansea University Computer Society NET3.035 for Linux 2.0 NET3: Unix domain sockets 0.12 for Linux NET3.035. Swansea University Computer Society TCP/IP for NET3.034 IP Protocols: ICMP, UDP, TCP Checking for 'wait' instruction... available. Linux version 2.0.4 (dm@neteng) (gcc version 2.7.2) #37 Thu Jul 11 02:16:15 PDT 1996 SGI Zilog8530 serial driver version 1.00 tty00 at 0xbfbd9838 (irq = 21) is a Zilog8530 tty01 at 0xbfbd9830 (irq = 21) is a Zilog8530 PS/2 auxiliary pointing device detected -- driver installed. wd33c93-0: chip=WD33c93B microcode=0d driver version 1.21 - 20/Apr/1996 compiled on Jul 11 1996 at 02:16:20 scsi0 : SGI WD93 scsi : 1 host. Started kswapd v 1.2 Vendor: SGI Model: SEAGATE ST32430N Rev: 0240 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi disk sda at scsi0, channel 0, id 1, lun 0 scsi : detected 1 SCSI disk total. SCSI device sda: hdwr sector= 512 bytes. Sectors= 4197405 [2049 MB] [2.0 GB] sgiseeq.c: David S. Miller (dm@engr.sgi.com) eth0: SGI Seeq8003 08:00:69:08:8a:18 Partition check: sda: sda1 sda2 sda3 sda4 Sending BOOTP and RARP requests.... OK Root-NFS: Got RARP answer from 150.166.75.7, my address is 150.166.75.5 Root-NFS: Got file handle for /tftpboot/150.166.75.5 via RPC VFS: Mounted root (nfs filesystem). bash# From owner-linux@cthulhu.engr.sgi.com Thu Jul 18 06:39:14 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id GAA17308; Thu, 18 Jul 1996 06:39:14 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id NAA19991 for linux-list; Thu, 18 Jul 1996 13:39:06 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id GAA19979 for ; Thu, 18 Jul 1996 06:39:05 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id GAA17302; Thu, 18 Jul 1996 06:39:05 -0700 Date: Thu, 18 Jul 1996 06:39:05 -0700 Message-Id: <199607181339.GAA17302@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: har har har Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hacking GNU libc is fun, wheee... gnu-libc/string/string.h: /* Find the first occurence of NEEDLE in HAYSTACK. NEEDLE is NEEDLELEN bytes long; HAYSTACK is HAYSTACKLEN bytes long. */ extern __ptr_t memmem __P ((__const __ptr_t __haystack, size_t __haystacklen, __const __ptr_t __needle, size_t __needlelen)); /* Sautee STRING briskly. */ extern char *strfry __P ((char *__string)); /* Frobnicate N bytes of S. */ extern __ptr_t memfrob __P ((__ptr_t __s, size_t __n)); ----------------------------------------------//// Yow! 233 microsecond remote host TCP latency ---- beat that --------------------------------------------////__________ o David S. Miller, dm@engr.sgi.com /_____________/ / // /_/ >< From owner-linux@cthulhu.engr.sgi.com Sun Jul 28 20:38:48 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA04468; Sun, 28 Jul 1996 20:38:47 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id DAA12038 for linux-list; Mon, 29 Jul 1996 03:38:40 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA12032 for ; Sun, 28 Jul 1996 20:38:38 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA04462; Sun, 28 Jul 1996 20:38:38 -0700 Date: Sun, 28 Jul 1996 20:38:38 -0700 Message-Id: <199607290338.UAA04462@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: question Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk http://www-add.engr.sgi.com/nsd/htmls/prodmkt/HP_NET/100BT.html#100Base-TforIndy Are any of these available for INDY yet? If so, I'd like to write a driver for one under Linux and see if we can get the _real_ world record for over the wire tcp latency on _real_ hardware, an SGI machine. Oh btw, userland is coming along. I'll post a progress report sometime soon... dm@engr.sgi.com 'Ooohh.. "FreeBSD is faster over loopback, when compared to Linux over the wire". Film at 11.' -Linus From owner-linux@cthulhu.engr.sgi.com Wed Jul 31 11:34:45 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA01791; Wed, 31 Jul 1996 11:34:44 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA07802 for linux-list; Wed, 31 Jul 1996 18:34:32 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA07794 for ; Wed, 31 Jul 1996 11:34:30 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id LAA01787; Wed, 31 Jul 1996 11:34:33 -0700 Date: Wed, 31 Jul 1996 11:34:33 -0700 Message-Id: <199607311834.LAA01787@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: Thanks Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Thanks to all those who got me the current status on the INDY 100mb/s cards. It was very informative. dm@engr.sgi.com 'Ooohh.. "FreeBSD is faster over loopback, when compared to Linux over the wire". Film at 11.' -Linus From owner-linux@cthulhu.engr.sgi.com Wed Jul 31 17:50:24 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA09318; Wed, 31 Jul 1996 17:50:24 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA26701 for linux-list; Thu, 1 Aug 1996 00:50:18 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA26688 for ; Wed, 31 Jul 1996 17:50:17 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA10293 for linux; Wed, 31 Jul 1996 17:48:43 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199608010048.RAA10293@yon.engr.sgi.com> Subject: Linux: the next step To: linux@yon.engr.sgi.com Date: Wed, 31 Jul 1996 17:48:43 +1700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 544 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hi Linuxies, So soon the port will be "over". What's next? Can we turn this from a neat hacker's adventure into something really beneficial to SGI? Thanks to Larry and David, I started collecting some thoughts in: http://info.engr/linux/next-step.html P.S. I also talked to some people who oppose all this so I made their voices heard in: http://info.engr/linux/skeptic.html I hope you'll find these two mildly interesting. I wish TJ could join us in this new endeavor. Any constructive input is as always welcome. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Thu Aug 1 13:48:04 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA07790; Thu, 1 Aug 1996 13:48:04 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA21059 for linux-list; Thu, 1 Aug 1996 20:47:57 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA21054 for ; Thu, 1 Aug 1996 13:47:55 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id NAA11583 for linux; Thu, 1 Aug 1996 13:46:21 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199608012046.NAA11583@yon.engr.sgi.com> Subject: Those FreeBSD guys... To: linux@yon.engr.sgi.com Date: Thu, 1 Aug 1996 13:46:21 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2001 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Yesterday, I went to the MindSource monthly meeting (Michael's at Shoreline) where three FreeBSD people gave a talk. Jordan Hubbard (he is on a visit from Ireland), Sameer Parekh (sp?), and Matt Dillon. Of course there were persistent questions from the audience to the tune of "I have this other system at home that starts with L..., why should I switch to FreeBSD?" Here are some of the answers given (from memory): "Our impression of the Linux community is that they are a bunch of Cowboys, they don't even use a source-control system to coordinate and split the work. We have these great development control tools: cvsup and sup ... we work really well together. all the core team has write permission to the source tree" There are 47 people doing major contributions. 14 of them are core. "Linux might give you the "feeling" it is faster, but it is because we gave a lot of thought in the design to scalability and SMP, when you load Linux the great performance suddenly drops down sharply while BSD scales nicely." "If you want a single user Unix to play at home, Linux is fine but if you are a commercial entity or ISP and you count on reliability and solid network performance, complex routing etc. use FreeBSD" "Linux is just a kernel, when you go to a full distribution things are much more complex, there are too many Linux distributions there's only one FreeBSD source base and it is complete with all utilities" "They try to run on too many architectures and the code is not clean We (FreeBSD as opposed to NetBSD) focus on Intel only, do it cleanly and make sure it works well" "They have the momentum and we don't underestimate this... we learned that we need to be nicer towards newbie questions to establish a larger user base" The future of FreeBSD is really promising: Clustering & Log filesystems are coming. SMP is already here (although it is not exactly symmetrical)" Sounds like these guys haven't seen linux since 0.99... Interesting nevertheless. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Thu Aug 1 18:14:49 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA18865; Thu, 1 Aug 1996 18:14:49 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA29537 for linux-list; Fri, 2 Aug 1996 01:14:37 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA29527 for ; Thu, 1 Aug 1996 18:14:35 -0700 Received: from neteng.engr.sgi.com (gate5-neteng.engr.sgi.com [150.166.61.33]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA11931 for ; Thu, 1 Aug 1996 18:13:01 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA18859; Thu, 1 Aug 1996 18:14:34 -0700 Date: Thu, 1 Aug 1996 18:14:34 -0700 Message-Id: <199608020114.SAA18859@neteng.engr.sgi.com> From: "David S. Miller" To: ariel@cthulhu.engr.sgi.com CC: linux@yon.engr.sgi.com In-reply-to: <199608012046.NAA11583@yon.engr.sgi.com> (ariel@yon) Subject: Re: Those FreeBSD guys... Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: ariel@yon (Ariel Faigon) Date: Thu, 1 Aug 1996 13:46:21 -0700 (PDT) I can't help, I have to comment on some of this ;-) My comments probably look like flame fare, but statements like the following make my stomach turn. Enter this mail at your own risk. ;) Yesterday, I went to the MindSource monthly meeting (Michael's at Shoreline) where three FreeBSD people gave a talk. Jordan Hubbard (he is on a visit from Ireland), Sameer Parekh (sp?), and Matt Dillon. My pinhead radar was on high lately, this must have been what set it off ;) "Our impression of the Linux community is that they are a bunch of Cowboys, " Yee haw! "they don't even use a source-control system to coordinate and split the work. We have these great development control tools: cvsup and sup ... we work really well together. all the core team has write permission to the source tree" There are 47 people doing major contributions. 14 of them are core. Mostly untrue. Fact: Linus is the only person who can get at the master tree, of what use are source control tools when this is the case is beyond me. Fact: The entire world has write permission to the Linux sources, because of the GPL. The FreeBSD tree can be encorporated into things where the sources aren't publicly available. Fact: Those subprojects (mostly the ports) do use source control systems (the same ones the FreeBSD people use, sans sup which is truly braindamaged and useless, cvs does everything sup claims to be doing) when multiple people are working on tree, because it makes _sense_ here. Fact: FreeBSD people are jealous that we have allowed one person to drive the firetruck "by himslef" and provide free QA for all kernel development. In Linus we trust. "Linux might give you the "feeling" it is faster, but it is because we gave a lot of thought in the design to scalability and SMP, when you load Linux the great performance suddenly drops down sharply while BSD scales nicely." Fact: FreeBSD has been talking/toying with an SMP implementation for many years now, currently the best it can do is run user processes on one cpu and service interrupts on another on one particular dual-pentium system. Linux has SMP working on all Intel platforms which at least closely adhere to the Intel SMP specification. We also have SMP fully working on Sparc machines, MIPS should be next. Fact: It not only feels faster, it is faster, and on all supported platforms. We have shown this with benchmarks, and real life examples. On my 4 processor SparcStation I got Sparc/ Linux smp working on, I had a load of 600 for 3 hours going on that machine. The jobs were a mixture of lat_tcp's, bw_tcp's parallel kernel makes on both local disk and over NFS, 300 invocations of crashme, and my X session locally on the machine. The machine had filled up %92 of it's swap space (the machine had 168mb of ram if I recall), typing commands in my xterms were still spiffy. Next. "If you want a single user Unix to play at home, Linux is fine but if you are a commercial entity or ISP and you count on reliability and solid network performance, complex routing etc. use FreeBSD" Fact: Linux survives crashme and other stress tests longer than any commercial or free operating system out there. Fact: FreeBSD is faster over loopback when compared to Linux over the wire. ;-) "Linux is just a kernel, when you go to a full distribution things are much more complex, there are too many Linux distributions there's only one FreeBSD source base and it is complete with all utilities" Fact: Entities like RedHat and others provide prepackaged, plug in and go, click your mouse button on this and it works, Linux installations and full support. Fact: More distributions give Linux more flavor. If I don't like the way the distribution scheme is layed out in the FreeBSD "one true" distribution, I'm out of luck because "I have no choice." "They try to run on too many architectures and the code is not clean We (FreeBSD as opposed to NetBSD) focus on Intel only, do it cleanly and make sure it works well" I don't think I even need to say how bolixed this statement is. "They have the momentum and we don't underestimate this... we learned that we need to be nicer towards newbie questions to establish a larger user base" I am happy that they do not understand the real reason we have so much momentum. The future of FreeBSD is really promising: Clustering & Log filesystems are coming. SMP is already here (although it is not exactly symmetrical)" Linux has real symmetrical SMP today, we have MPP support and work on multicomputers, we are X/Open and POSIX branded. Fine grained SMP, IPV6, and more + faster support on more architectures in in the works. People are working on clustering and logging filesystems for Linux as well. Sounds like these guys haven't seen linux since 0.99... Interesting nevertheless. I agree. dm@engr.sgi.com 'Ooohh.. "FreeBSD is faster over loopback, when compared to Linux over the wire". Film at 11.' -Linus From owner-linux@cthulhu.engr.sgi.com Thu Aug 1 20:38:22 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA20608; Thu, 1 Aug 1996 20:38:22 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id DAA23655 for linux-list; Fri, 2 Aug 1996 03:38:15 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA23648 for ; Thu, 1 Aug 1996 20:38:14 -0700 Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA12032 for ; Thu, 1 Aug 1996 20:36:30 -0700 Received: from windy.wellington.sgi.com by soyuz.wellington.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/940406.SGI) id PAA04878; Fri, 2 Aug 1996 15:37:39 +1200 Received: (alambie@localhost) by windy.wellington.sgi.com (950413.SGI.8.6.12/8.6.9) id PAA16834; Fri, 2 Aug 1996 15:37:38 +1200 From: "Alistair Lambie" Message-Id: <9608021537.ZM16832@windy.wellington.sgi.com> Date: Fri, 2 Aug 1996 15:37:37 +0000 In-Reply-To: ariel@yon.engr.sgi.com (Ariel Faigon) "Linux: the next step" (Aug 1, 12:51pm) References: <199608010048.RAA10293@yon.engr.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: Linux: the next step Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Aug 1, 12:51pm, Ariel Faigon wrote: > Subject: Linux: the next step > Hi Linuxies, > > So soon the port will be "over". > > What's next? > > Can we turn this from a neat hacker's adventure into > something really beneficial to SGI? > > Thanks to Larry and David, I started collecting some > thoughts in: > > http://info.engr/linux/next-step.html > My 2c...maybe it isn't even worth that much! I know that there is a lot of politics here, so some of this may be just dreaming.... I'll break it into the same sections as Ariel has: We need more contributors to keep momentum: 1. We will HAVE to seed machines to people as I'm guessing most people have ~$0 budget for hardware. 2. We need to make sure the basic tools (gcc/glibc) make it as seamless as possilble to port things (ie, just configure/make and it happens). I think David is doing a great job here, but we are probably going to need an ongoing effort from a real good libc hacker who can get any compatability/conflict type problems sorted intelligently. What is David's commitment when he leaves...or are we going to let him leave?? 3. We need to get some of the neat Indy features supported. We need an SGI graphics wizard to make X fly, then things like ISDN and audio. These are the sorts of things that will make people want to use Indy's as their primary dev environments. Fast and great functionality. 4. We need to have some people who are able to commit to help contributors who need to find out things. It needs to be easy for people to find out information they need. This is a tricky area as sometimes people really will need to know confidential info...how can we handle this. I know Ralph has found it real difficult at times to find things out...we need to make this easier so as not to slow things down. We should start thinking marketing 1. I believe RedHat would be the best candidate for distribution. I would like to see it 'launched' at some high profile conference (Linux related), have it on a CD that has 'awesome' artwork (the old WebForce CD's are a good example) and becomes a great collectors item afterwards, and is packaged with a real cool T-Shirt for the first X copies. This stuff should be firmly Linux relevant from the design point (penguins??) but at the same time be SGI through and through. SGI should probably contribute this part. 2. Don't let marketing name it or we'll get Cosmo Linux....just kidding :-) I think we need to emphasis that SGI has put real dollars into this and is committed to make it work, rather than the 'faster' bandwagon. To emphasis this point I feel we need to have it run on any new platforms at first shipment, and support the neat features. Nothing will kill it quicker than if people get this feeling that this is second tier and nobody cares. We need a number of us to commit to give quality help to people on mailing lists/newgroups. Shucks...maybe if we even had 5% of the budget IRIX has... 3. Sponsor Linux events etc....give away Indy's etc...and other things like apparel and mugs. These should all have professional art work that is to die for....this stuff works when people really want it. It should really put SGI in front of people. My feeling is that we can really get in front of the technical people in a lot of places and get them on our side. While they might not be the decision makers, it sure helps sales people if the techo's in the organisation are on side rather than fighting against you! 4. A Web/FTP server is a great idea. Let's get some real great design on the Web server though so that the quality is similar to Silicon Surf. Again, it gets the message across that we are serious, committed etc. We also want people accessing as many things with .sgi.com in them!! 5. If we can't get people to come to sgi, how about we sponsor good net connections for them that are in a domain linux.sgi.com. Subtle, but it does get sgi associated with them on the net....and we do have a backbone to most parts of the world. > > P.S. I also talked to some people who oppose all this > so I made their voices heard in: > > http://info.engr/linux/skeptic.html > One comment I would make here is that people really need to work out whether we are a hardware or software company. I realise that this is probably contentious (sp?), but my feeling is that we are a company who make hardware, and the software is really a means to an end...selling more hardware. If this is true, then people need to look at where we are going to get the greatest number of hardware sales from....Irix or Linux. We need both I think to hit different markets, and maybe we even need NT (don't want to get into that argument!). Maybe we should be getting agreement from management for funding based on sales, and I'll bet we can get a lot more mileage from the funding than Irix will :-) > I hope you'll find these two mildly interesting. It's great having someone pull it all together, thanks. Cheers, Alistair -- Alistair Lambie alambie@wellington.sgi.com Silicon Graphics New Zealand SGI Voicemail: 56791 Level 5, Walsh Wrightson Tower, Ph: +64-4-802 1455 94-96 Dixon St, Wellington, NZ Fax: +64-4-802 1459 From owner-linux@cthulhu.engr.sgi.com Fri Aug 2 16:09:19 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA16192; Fri, 2 Aug 1996 16:09:18 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA08028 for linux-list; Fri, 2 Aug 1996 23:07:57 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA08021 for ; Fri, 2 Aug 1996 16:07:55 -0700 Received: from aa5b.engr.sgi.com (aa5b.engr.sgi.com [192.102.117.24]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA13474 for ; Fri, 2 Aug 1996 16:06:18 -0700 Received: from aa5b (localhost [127.0.0.1]) by aa5b.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id QAA13029; Fri, 2 Aug 1996 16:07:41 -0700 Message-ID: <32028A3C.2781@engr.sgi.com> Date: Fri, 02 Aug 1996 16:07:40 -0700 From: Nigel Gamble X-Mailer: Mozilla 2.02S (X11; I; IRIX 6.2 IP22) MIME-Version: 1.0 To: Alistair Lambie CC: ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: Linux: the next step References: <199608010048.RAA10293@yon.engr.sgi.com> <9608021537.ZM16832@windy.wellington.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Alistair Lambie wrote: > To > emphasis this point I feel we need to have it run on any new platforms > at first shipment, and support the neat features. Dream on! Here in ISD (Indigo2 land), we're working flat out just to get IRIX to run on any new platforms at first shipment, with all the neat features supported. I think you'll find the same is true of all the other product divisions. > One comment I would make here is that people really need to work out whether > we are a hardware or software company. I realise that this is probably > contentious (sp?), but my feeling is that we are a company who make hardware, > and the software is really a means to an end...selling more hardware. If this > is true, then people need to look at where we are going to get the greatest > number of hardware sales from....Irix or Linux. We need both I think to hit > different markets, and maybe we even need NT (don't want to get into that > argument!). Maybe we should be getting agreement from management for funding > based on sales, and I'll bet we can get a lot more mileage from the funding > than Irix will :-) We are neither a hardware company nor a software company. We are a *systems* company. We build the best computer systems on the planet through a combination of hardware and software working together. If we replaced IRIX with NT, we would have to cancel most of our high performance hardware projects, because NT will not support the new systems. As for Linux, when will it support true symmetric multiprocessing with fine-grained semaphore and mutex locking, and a fully preemptible kernel? At the San Diego Usenix earlier this year, Linus Torvalds thought that the probable answer was "not anytime soon". (By the way, in order to do this correctly, every device driver would have to be rewritten.) Linux would need this *at a minimum* before there is any hope that it would supplant IRIX on the current generation of hardware, let alone any future new platforms. -- Nigel Gamble "Are we going to push the edge of the envelope, Brain?" Silicon Graphics "No, Pinky, but we may get to the sticky part." nigel@sgi.com (415) 933-3109 From owner-linux@cthulhu.engr.sgi.com Fri Aug 2 16:55:31 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA19672; Fri, 2 Aug 1996 16:55:30 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA15732 for linux-list; Fri, 2 Aug 1996 23:54:10 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA15725 for ; Fri, 2 Aug 1996 16:54:09 -0700 Received: from neteng.engr.sgi.com (gate5-neteng.engr.sgi.com [150.166.61.33]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA13519 for ; Fri, 2 Aug 1996 16:52:32 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA19624; Fri, 2 Aug 1996 16:54:06 -0700 Date: Fri, 2 Aug 1996 16:54:06 -0700 Message-Id: <199608022354.QAA19624@neteng.engr.sgi.com> From: "David S. Miller" To: nigel@cthulhu.engr.sgi.com CC: alambie@wellington.sgi.com, ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com In-reply-to: <32028A3C.2781@engr.sgi.com> (message from Nigel Gamble on Fri, 02 Aug 1996 16:07:40 -0700) Subject: Re: Linux: the next step Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Fri, 02 Aug 1996 16:07:40 -0700 From: Nigel Gamble Dream on! Here in ISD (Indigo2 land), we're working flat out just to get IRIX to run on any new platforms at first shipment, with all the neat features supported. I think you'll find the same is true of all the other product divisions. I am one person, I am getting close to bootstrapping a complete Linux system on the INDY in the course of 3 months. The only way I could be dreaming is due to the fact that I have been hacking for 30 hours straight with no sleep at all and this isn't even flat out for me actually. We are neither a hardware company nor a software company. We are a *systems* company. Although this may be true, what ever sells your hardware could foot the purpose correct? The margin comes from the hardware, and as you say the software is there to make that hardware capable of doing something. If Linux could do this, and sell SGI hardware, SGI is doing the same thing it is today in my estimation. As for Linux, when will it support true symmetric multiprocessing with fine-grained semaphore and mutex locking, and a fully preemptible kernel? At the San Diego Usenix earlier this year, Linus Torvalds thought that the probable answer was "not anytime soon". Linus, myself, and some other key developers have come to the conclusion that the current way of doing SMP is no more than an intellectual curiosity and nothing more. What he had in the back of his mind when he made that statement at Usenix was really, "Linux is not going to scale it's SMP in that way." But being the person that he is, he decided not to put it that way until he had a cast in stone proof of concept that another way was indeed possible. With Linux, thankfully, we have the luxury of really thinking about how to correctly go about something like a scalable SMP kernel architecture without a deadline hovering over our heads. However, I will be frank, and say that no we do not have this SMP of all SMP figured out yet. But I do believe that we will come up with something not short of impressive and cutting edge. If I had to guess at how we'd go about it, generally? I would venture one of the following or a combination thereof perhaps: 1) Scale to 4 cpus and nothing more, cluster past that, run seperate kernels on each processor group of 4, which live in their own little world and do not have shared resources with the other cluster kernels. With the exception that clusters can pass processes between each other when load on one get much too high than the others. (I'm a bit sketchy on any of the real specifics on how we would pull this one off entirely) 2) Away with the locks completely, if you are going to do SMP then don't add a brick wall to the equation as a means to an end. Through numerous conversations with Linus I have deteremined that he and I agree that locks all over the place is not the way to go and neither is pre-emption. We believe that the purpose of locks can be replaced entirely with carefully designed data structures that are atomic via the way they are accessed. Again these are just off the top of my head, unfortunately I haven't had the opportunity to get into the zone and put all of my senses into getting these ideas out of perpetual beta. I was hoping that if I got the initial INDY port out of the way and functional very quickly I'd finally have a chance to think about these things and come up with something concrete I could actually implement and start playing with. This is along the lines of what I wanted my big contribution back to SGI to be for allowing me to have this internship, however it was obviously necessary to get a proof of concept Linux implementation out the door on a machine before I could start doing things like that. My real point is, yes we cannot scale very well on the type of machines you mention, we do not have fine grained SMP and kernel preemtion. The current view I propose is that this method of doing SMP is one of many oysters that could have been opened to satisfy the needs of the task at hand. However I feel that the oyster with the real pearl of an SMP implementation in it has yet to have been found. Putting Linux down because it cannot do what Solaris2.5, SVR4.2MP, and IRIX can do "today" on very high end hardware I would consider to be an oxy-moron. All of it's code has been written by contributors in their spare time and out of their own good hearts on the low end hardware they could only get their hands on. And even with those constraints, we have things which the other freely available operating systems simply do not have an probably will not for a very long time. But now all of this is slowly but surely going to change, as more and more people like myself get the opportunity to express their hacking talents on high end hardware (the systems where the capabilities you mention even matter) via contributions such as my internship and hardware loans to the various developers, this gap will get smaller and smaller especially if the current pace of Linux keeps up. This is one thing I can assure you of. Maybe the real issue is, now that I think about, we haven't put our efforts into crossing that bridge, because we have not gotten to it yet. When we do get there, it'll show time baby. dm@engr.sgi.com 'Ooohh.. "FreeBSD is faster over loopback, when compared to Linux over the wire". Film at 11.' -Linus From owner-linux@cthulhu.engr.sgi.com Fri Aug 2 17:14:15 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA19986; Fri, 2 Aug 1996 17:14:14 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA18041 for linux-list; Sat, 3 Aug 1996 00:12:54 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA18029 for ; Fri, 2 Aug 1996 17:12:52 -0700 Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA13570 for ; Fri, 2 Aug 1996 17:11:13 -0700 Received: by soyuz.wellington.sgi.com (951211.SGI.8.6.12.PATCH1042/940406.SGI) id MAA02013; Sat, 3 Aug 1996 12:12:32 +1200 From: alambie@wellington.sgi.com (Alistair Lambie) Message-Id: <199608030012.MAA02013@soyuz.wellington.sgi.com> Subject: Re: Linux: the next step To: nigel@cthulhu.engr.sgi.com (Nigel Gamble) Date: Sat, 3 Aug 1996 12:12:32 +1200 (NZT) Cc: alambie@wellington.sgi.com, ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com In-Reply-To: <32028A3C.2781@engr.sgi.com> from "Nigel Gamble" at Aug 2, 96 04:07:40 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 3870 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > > Alistair Lambie wrote: > > To > > emphasis this point I feel we need to have it run on any new platforms > > at first shipment, and support the neat features. > > Dream on! Here in ISD (Indigo2 land), we're working flat out just to > get IRIX to run on any new platforms at first shipment, with all > the neat features supported. I think you'll find the same > is true of all the other product divisions. > Yeah, I know!! This may be a dream, but I think it is to some degree achievable. The thing with IRIX is that EVERYTHING has to be integrated and commercial quality on first ship. What we really need to do in Linux is expose the interfaces to things. If we give enough info to people it will generally happen. I don't know what is involved to do this...maybe a skeleton driver or something. It doesn't really matter whether it is optimised, or even bug free, just as long as it gives those with the ability to write code like this enough info to work with. As for applications and things to use this stuff, thats up to the Linux community to do! > > One comment I would make here is that people really need to work out whether > > we are a hardware or software company. I realise that this is probably > > contentious (sp?), but my feeling is that we are a company who make hardware, > > and the software is really a means to an end...selling more hardware. If this > > is true, then people need to look at where we are going to get the greatest > > number of hardware sales from....Irix or Linux. We need both I think to hit > > different markets, and maybe we even need NT (don't want to get into that > > argument!). Maybe we should be getting agreement from management for funding > > based on sales, and I'll bet we can get a lot more mileage from the funding > > than Irix will :-) > > We are neither a hardware company nor a software company. > We are a *systems* company. We build the best computer systems > on the planet through a combination of hardware and software > working together. If we replaced IRIX with NT, we would have > to cancel most of our high performance hardware projects, because > NT will not support the new systems. As for Linux, > when will it support true symmetric multiprocessing with fine-grained > semaphore and mutex locking, and a fully preemptible kernel? > At the San Diego Usenix earlier this year, Linus Torvalds > thought that the probable answer was "not anytime soon". > (By the way, in order to do this correctly, every device driver would > have to be rewritten.) Linux would need this *at a minimum* before > there is any hope that it would supplant IRIX on the current > generation of hardware, let alone any future new platforms. > Yup, you're right, we are a systems company. I don't expect that Linux will replace IRIX even in the distant future. IRIX isn't going to stand still, but nor is Linux. One of the things I have noticed about Linux is that when someone shows the way, things happen fairly quickly. Probably Linus's comment about the symmetric multiprocessing was based on available resource, rather than a lack of desire to do it. Maybe this is an opportunity for SGI to provide some input into the Linux community...if we were to do some starter work on this (on one of our boxes of course!!) I'm sure that others would pretty soon catch on. The big thing with Linux is that we don't have to do all the work....a bit of work on an initial framework and a push in the right direction is often all that will be necessary. Let's take the ISDN port on the Indy....if we somehow show people how to use this, I'm sure it won't be long before someone outside of SGI gets it up and going! Same with audio. Let's not think in terms of supplanting IRIX, let's look at growing the number of boxes we ship. That's got ot be good for us!! Cheers, Alistair From owner-linux@cthulhu.engr.sgi.com Fri Aug 2 18:13:13 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA20537; Fri, 2 Aug 1996 18:13:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA29306 for linux-list; Sat, 3 Aug 1996 01:11:45 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA29301 for ; Fri, 2 Aug 1996 18:11:44 -0700 Received: from neteng.engr.sgi.com (gate5-neteng.engr.sgi.com [150.166.61.33]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA13659 for ; Fri, 2 Aug 1996 18:10:07 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id SAA20491; Fri, 2 Aug 1996 18:11:31 -0700 Message-Id: <199608030111.SAA20491@neteng.engr.sgi.com> To: Nigel Gamble From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: Alistair Lambie , ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: Linux: the next step Date: Fri, 02 Aug 1996 18:11:31 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : Dream on! Here in ISD (Indigo2 land), we're working flat out just to : get IRIX to run on any new platforms at first shipment, with all : the neat features supported. I think you'll find the same : is true of all the other product divisions. It's hard work. I know people are working hard to keep IRIX going. And there is a lot in IRIX that isn't in Linux. However, there's a lot in IRIX that shouldn't be in IRIX, let alone Linux. One of the cool things that David has done this summer was to keep the generic code free of #ifdef *_WAR stuff that is littered throughout the IRIX kernel. : We are neither a hardware company nor a software company. : We are a *systems* company. I agree. But answer these questions: . would anyone buy our hardware if we didn't put the software on it? . would anyone buy our software on some other hardware? I think that gives you an answer to what kind of comapny we really are. : As for Linux, : when will it support true symmetric multiprocessing with fine-grained : semaphore and mutex locking, and a fully preemptible kernel? The fine grained locking is a lose. It costs us way too much and what I am seeing is a trend backwards towards coarser grained locking. If this wasn't true, why did we build lego? Why are we building Nexus? Linux already has a RT kernel. I just reviewed a fantastic Usenix paper that added RT to Linux - fully preemptable, hard real time to < 100 usecs, and less than 3K lines of code change. Their test case was a 100Khz clock pulse on a parallel port; they got it every time, with less than 15usecs skew, while the system was tar-ing one file system to another, running netscape, and generally doing same old Unix stuff just like normal. It's really impressive and very uninvasive. : At the San Diego Usenix earlier this year, Linus Torvalds : thought that the probable answer was "not anytime soon". : (By the way, in order to do this correctly, every device driver would : have to be rewritten.) Almost none of the drivers need a rewrite for the RT stuff. That work was a good example of what I call "orthogonal thinking" or using a completely different approach to solve the problem. : Linux would need this *at a minimum* before : there is any hope that it would supplant IRIX on the current : generation of hardware, let alone any future new platforms. Linux isn't going to replace IRIX any time soon. However, Linux is going to show off MTI's chips and SGI's hardware in a somewhat more positive light. If all that happens is that people get psyched about the "hidden" performance in SGI hardware and get IRIX to show off that performance, then the paltry amount we've spent on Linux will be worth it. Finally, think about this: how many times have you had a "great idea" for better IRIX performance, gone off an prototyped it, only to find that it makes no difference? Linux lets you test out those ideas and see the real performance difference, unadulterated by any surrounding bloat. That's cool. We want that. From owner-linux@cthulhu.engr.sgi.com Sun Aug 4 00:54:21 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA26709; Sun, 4 Aug 1996 00:54:21 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA02098 for linux-list; Sun, 4 Aug 1996 07:53:51 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA02093 for ; Sun, 4 Aug 1996 00:53:50 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA26656; Sun, 4 Aug 1996 00:53:49 -0700 Date: Sun, 4 Aug 1996 00:53:49 -0700 Message-Id: <199608040753.AAA26656@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: more on real-time functionality for Linux Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Because Larry mentioned some things regarding real time under Linux just to other day, I thought the following text would be interesting to people. A Vision for Linux 2.2 -- POSIX.1b Compatibility and Real-Time Support ---------------------------------------------------------------------- Markus Kuhn -- 1996-07-22 [The latest version of this text can be found on .] Today, the Linux kernel and libc are quite well compatible with the POSIX.1 and POSIX.2 standards, which specify system calls, library functions and shell command compatibility for UNIX-style operating systems. Some Linux distributions have even passed POSIX.1 conformance tests. However, the POSIX.1 system calls and library functions define only a minimum core functionality required by anything that looks like UNIX. Many slightly more advanced functions like mmap(), fsync(), timers, modifiable scheduling algorithms, IPC, etc., which are essential for many real world applications, have not been standardized by POSIX.1 in 1990. The new POSIX.1b standard (now officially called IEEE Std 1003.1b-1993, ISBN 1-55937-375-X, during development of the standard, it was called POSIX.4) corrects this and I believe POSIX.1b contains a large number of useful ideas for further development on Linux. In the very short introduction below, I hope to rise your interest in POSIX.1b and in real-time problems in general and to stimulate some development work in this direction. Happy reading! The new POSIX extensions focus on the requirements of real-time applications and on applications which have to perform high performance I/O. Many applications like interactive video games, high performance database servers, multimedia players and control software for all kinds of hardware require more deterministic scheduling, paging, signaling, timing and inter process communication mechanisms than what is available on traditional UNIX systems like BSD4.3. The functionality of systems like BSD4.3 has been optimized with mainframe multi-user time-sharing scenarios in mind, while operating systems for personal computers should also support real-time applications in addition. On a personal computer, it is often acceptable and desired that for example interactive games or CPU and memory intensive multimedia applications are excluded from the normal paging and scheduling strategies that try to be as fair as possible to all users of a large mainframe. The lack of real-time capability in Linux 1.2 has so far been the main reason why still a number of interesting applications that run fine on MS-DOS were unimplementable as user processes under Linux. Some examples are for instance highly reliable audio recording/replay tools, control software for astronomical CCD cameras, real-time signal processing algorithms, serial port smartcard emulators, MIDI computer music tools, etc. With the recent addition of POSIX.1b memory locking and static priority scheduling functions to Linux 1.3, this starts to change now. A lot of things still have to be implemented and your contributions are very welcome! This text summarizes, what functions have not yet been implemented and which people have already started to work on some of these. Please contact them if you want to know the status of their work or if you want to contribute. Please let me know about any progress so that I can keep this text up-to-date. In order to use the first new POSIX.1b features that have recently been added to Linux, please install a recent kernel, libc-5.3.12, and man-pages-1.11 or newer as available via ftp from sunsite.unc.edu or tsx-11.mit.edu. The real-time-support is far from complete, but some interesting features are already available. POSIX.1b-1993 defines in addition to POSIX.1-1990 the following new concepts and functions: Improved Signals ---------------- POSIX.1b adds a new class of signals. These have the following new features: - there are much more user specified signals now, not only SIGUSR1 and SIGUSR2. - The additional POSIX.1b signals can now carry a little bit data (a pointer or an integer value) that can be used to transfer to the signal handler information about why the signal has been caused. - The new signals are queued, which means that if several signals of the same type arrive before the signal handler is called, all of them will be delivered. - POSIX.1b signals have a well-defined delivery order, i.e. you can work now with signal priorities. - A new function sigwaitinfo() allows to wait on signals and to continue quickly after the signal arrived with program execution without the overhead of calling a signal handler first. The new queued signals are a necessary prerequisite for the implementation of the POSIX.1b asynchronous I/O interface (see below). They might also provide a good interface for delivering hardware interrupts to user processes. New functions for signals are: sigwaitinfo(), sigtimedwait(), sigqueue(). Implementation status: not yet implemented. Kevin Tran has sent me a short note that he has started to do some work on POSIX.1b signals for Linux. Inter Process Communication (IPC) and memory mapped files --------------------------------------------------------- POSIX.1b now defines shared memory, messages, and semaphores. The functionality and design of these is similar or better than the System V IPC mechanisms which we have already in Linux. The major extensions compared to System V IPC are: - Strings (like filename paths) instead of integers are used now to identify IPC resources. This will allow to avoid IPC resource collisions much easier than in SysV IPC. The POSIX IPC name space should probably be made visible as a /proc/ipc subdirectory, such that the usual tools like ls and rm can be used to locate and remove stale persistent IPC resources. - Semaphores come in two flavors: kernel based semaphores (as in System V, which requires a system call for each P/V operation) and now also user memory based semaphores. Kernel based semaphores are sometimes necessary for security reasons, however they are a real pain if you want to build e.g. a high performance database: Suppose there are 20 server processes operating on a single huge B-tree in a memory mapped database file. Inserting a node with minimal blocking of concurrent accesses by the other 19 processes in a large B-tree can require around 100 semaphore operations, and this means currently 100 kernel calls :-(. With POSIX.1b's user memory based semaphores, you put all your semaphores in a piece of shared memory and the library accesses them with highly efficient test-and-set machine code. System calls will then only be necessary in the rare case of a blocking P operation. A high performance database programmer's dream and easy to implement! - In POSIX.1b, both memory mapped files and shared memory are done with the mmap() system call. The new functions for IPC are: mmap(), munmap(), shm_open(), shm_close(), shm_unlink(), ftruncate(), sem_init(), sem_destroy(), sem_open(), sem_close(), sem_unlink(), sem_wait(), sem_trywait(), sem_post(), sem_getvalue(), mq_open(), mq_close(), mq_mq_unlink(), mq_send(), mq_receive(), mq_notify(), mq_setattr(), mq_getattr(), mprotect(). Implementation status: POSIX IPC has not yet been implemented (although a part of the basic mechanisms is already available in the existing SysV IPC code). Since Linux 1.3, mmap() is fully implemented. Eric Dumas has written me that he has done some work on POSIX IPC, however there are no patches available, yet. Memory locking -------------- Four new functions mlock(), munlock(), mlockall() and munlockall() allow to disable paging for either specified memory regions (mlock()) or for all pages (code, stack, data, shared memory, mapped files, shared libraries) to which a process has access (mlockall()). This allows to guarantee that for instance small time-critical daemons stay in memory which can help to guarantee response time of these processes. Under Linux, this (like many other real-time related features) is only allowed for root processes in order to avoid abuse of this feature by normal users in large time-sharing systems. Another application of memory locking are cryptographic computer security programs. Using mlock(), these systems can ensure that an unencrypted secret key or a password which is temporarily stored in a small user space array will never get in contact with the swap device, where under rare circumstances, someone might find the secret bytes even many months later. For these applications, it would be desirable if Linux allowed even non-root processes a small number of mlock()ed pages (e.g. up to four locked pages per non-root process should be ok). Implementation status: Linus has now added full POSIX.1b memory locking support to Linux alpha test kernel version 1.3.43. There exist also libc support and manual pages. So you won't have to apply the POSIX.4_locking patch from Ralf Haller any more. Synchronous I/O --------------- Databases, e-mail systems, log daemons, etc. require to be sure that the written piece of data has actually reached the harddisk, because transaction protocols require that a system crash or power failure after the write command can not harm the data any more. POSIX.1b defines the fsync() and O_SYNC mechanisms which Linux 1.2 already has. In addition, there is a very useful new function fdatasync() which requires that the data block is flushed to disk, however which does NOT require that the inode with the latest access/modification time is also flushed each time. With fdatasync(), the inode has only to be written in case the file length, file owner, or permission bits have changed. In database applications with mostly constant file sizes, where you sometimes require an fsync() after each few written blocks, but where you don't care about whether the access times in the inodes on the disc are always 100% up-to-date, fdatasync() could easily double (!) the performance of your system. There is also an msync() function for flushing a range of pages from memory mapped files to the disk. Implementation status: fsync(), fdatasync(), msync(), and O_SYNC are already available. O_DSYNC has not yet been implemented. However fdatasync() in Linux 1.3.55 is currently only an alias for fsync() and therefore not yet any more efficient than fsync(). Timers ------ - Instead of the old BSD style gettimeofday()/settimeofday() calls, POSIX.1b defines clock_gettimer(), clock_settimer() and clock_getres(). They offer nanosecond resolution instead of microseconds as with the old BSD calls (at least on Pentiums, a timer resolution much than a microsecond is available). In addition, you can query now the actual resolution of the timer with clock_getres(). - A new function nanosleep() allows to sleep also for less than a second (the old sleep() had only second resolution). In addition, nanosleep won't interfere with SIGALRM and in case of EINTR, it returns the time left, so you can easily continue in a while loop. - POSIX.1b defines also itimers, however instead of what the existing BSD itimers provide, you now can deal with several timers (at least 32 per process) and you have again theoretically up to one nanosecond resolution. The old itimer functions can still easily be implemented in libc for compatibility reasons using new POSIX-style itimer system calls. Implementation status: The POSIX clock and itimers system calls have not not yet been implemented, although much of the functionality is already available in the form of the BSD timers and adding them should be quite easy. Queued signals have to be implemented first for itimers. Nanosleep() is already available in Linux, but at the moment it supports only 10 ms resolution and it can optionally perform short microsecond precision busy waits of up to 2 ms length. Scheduling ---------- Linux 1.2 has so far been optimized a lot as a time sharing system, where several people run application programs like editors, compilers, debuggers, X window servers, networking daemons, etc. and do word processing, software development, etc. However there are a lot of applications for which Linux is currently unusable and for which even die-hard Linux enthusiasts have to keep a stand-alone DOS version on their disk. For >90% of these applications, the fact that Linux is incapable of guaranteeing the response time of an application is the major problem. Software for controlling e.g. an EPROM programmer, a robot arm, or an astronomical CCD camera is not realizable under a classic Unix if there is no dedicated real-time controller present in the controlled device. A lot of commercially available hardware has been designed with the real-time "capability" of DOS in mind and has no own microcontroller for time-critical actions. A real-world example: I have myself spent a long frustrating time of trying to implement an interface to a pay-TV decoder for Linux (which emulates a chip card and allows you to watch pay-TV for free :-). In this application, you have to wait for an incoming byte on the serial port, then you have to wait for around 0.7 to 2 ms (never shorter, never longer, otherwise the TV decoder gets a timeout and stops!) before returning an answer byte. It is virtually impossible to implement a user process for this task under Linux 1.2, while it is trivial to do this under DOS. I am looking forward to the day when Linux provides enough real-time support for this application so that I can finally remove MS-DOS from my harddisk. For these and similar real-time applications, POSIX.1b specifies three different schedulers, each with static priorities: SCHED_FIFO A preemptive, priority based scheduler. Each process managed under this scheduling priority possesses the CPU as long as (a) it does not block itself and (b) there comes no interrupt which puts another process into a higher priority wait queue. There exists a FIFO queue for each priority level and every process which gets runnable again is inserted into the queue behind all other processes. This is the most popular scheduler used in typical real-time operating systems. Function sched_yield() allows the process to go to the end of the FIFO queue without blocking. SCHED_RR A preemptive, priority based round robin scheduling strategy with quanta. It is a very similar to SCHED_FIFO, however each process has a time quantum and the process becomes preempted and is inserted at the end of the FIFO for the same priority level if it runs longer than the time quantum and other processes of the same priority level are waiting in the queue. Processes of lower priorities will like in SCHED_FIFO never get the CPU as long as a higher level process is in a ready queue and if a higher priority process becomes ready to run, it also gets the CPU immediately. SCHED_OTHER This is any implementation defined scheduler. Under Linux it is the classic time-sharing scheduler with "nice" values, etc. Under Linux, all SCHED_OTHER processes share the common static priority value 0. For security reasons, only root processes should under Linux be allowed to get any static priority higher than the one for SCHED_OTHER, because if these real-time scheduling mechanisms are abused, the whole system can be blocked. If one is developing a real-time application, it is a very good idea to have a shell with a higher static priority somewhere open in order to be able to kill the tested application in case something goes wrong. You should be aware, that if you use X11, not only the shell, but also the X server, the window manager and xterm will require a higher static priority in order to stop processes blocking the rest of the system. Therefore, testing real-time software will usually better be done on the console. With this POSIX.1b functionality, it is possible to run real-time software under Linux by giving it root permissions and assigning it a SCHED_FIFO strategy and a higher static priority than all other classic SCHED_OTHER Linux processes. In addition, typical real-time application lock their pages with mlockall() into the memory in order to avoid being swapped out. This guarantees that the real-time application can react as soon as possible on any interrupts and that the response time will not be influenced by the complicated normal Linux time-sharing priority mechanisms or by paging. However, please read also the chapter on interrupt dispatch latency below! The new functions are here: sched_setparam(), sched_getparam(), sched_setscheduler(), sched_getscheduler(), sched_yield(), sched_get_priority_max(), sched_get_priority_min(), sched_rr_get_interval(). Implementation status: The sched_*() system calls are now available since Linux 1.3.55 (Markus Kuhn ). Although much testing, performance evaluation, and optimization with the real-time scheduler is necessary (especially with regard to "fast interrupt handling, see below), you can already use the sched_*() calls in order to get the processor exclusively. There are also libc and manual pages available. Some earlier work on this was done by David F. Carlson in his POSIX.4_scheduler patch against Linux 1.2 (still available on sunsite). Asynchronous I/O (aio) ---------------------- POSIX.1b defines a number of functions which allow to send a long list of read/write requests at various seek positions in various files to the kernel with one single lio_listio() system call. While the process continues to execute the next instructions, the kernel will asynchronously read or write the requested pages and will send signals when the task has been completed (if this is desired). This is very nice for a database which knows that it will require a lot of different blocks scattered on a file. It will simply pass a list of the blocks to the kernel, and the kernel can optimize the disk head movement before sending the requests to the device. In addition this minimizes the number of system calls and allows the database to do something else in the meantime (e.g. waiting for the client process sending an abort instruction in which case the database server can cancel the async i/o requests with aio_cancel()). Another important application of aio are multimedia systems like MPEG or sound file players and recorders. These programs want to preload the next few seconds of the data stream from harddisk into locked memory, but also want to continue showing the video on the screen at the same time without any interruptions caused by synchronous I/O. The POSIX.1b async I/O calls provide a nice way for such anticipatory loading. POSIX.1b also defines priorities for asynchronous I/O, i.e. there is a way to tell the kernel that the read request for the MPEG player is more important than the read request of gcc. On a future real-time Linux, you don't want to see any image distortions while watching MPEG video and compiling a kernel at the same time if you gave the MPEG player a higher static priority. New functions in this area are: aio_read(), aio_write(), lio_listio(), aio_suspend(), aio_cancel(), aio_error(), aio_return(), aio_fsync(). Implementation status: Not yet implemented. The aio functions are probably best implemented in libc using kernel threads and the normal synchronous I/O system calls. There has recently been some progress on implementing kernel threads in Linux 1.3 using the clone() system call. Adding priority I/O to Linux might be a more complicated job, because many device drivers would have to be extended by priority wait queues. Implemented options ------------------- As POSIX.1b conformance does not require the implementation of all these functions, macros have been specified for that indicate to application software which of the POSIX.1b functionality is available on this system. This way, portable software can be written that uses real-time features only when they are available. Under the latest Linux kernel and libc development versions, the following POSIX.1b macros have been defined and indicate implemented functions: _POSIX_FSYNC _POSIX_MAPPED_FILES _POSIX_MEMLOCK _POSIX_MEMLOCK_RANGE _POSIX_MEMORY_PROTECTION _POSIX_PRIORITY_SCHEDULING The POSIX.1b options indicated by the following macros have not yet been implemented under Linux: _POSIX_ASYNCHRONOUS_IO _POSIX_MESSAGE_PASSING _POSIX_PRIORITIZED_IO _POSIX_REALTIME_SIGNALS _POSIX_SEMAPHORES _POSIX_SHARED_MEMORY_OBJECTS _POSIX_SYNCHRONIZED_IO _POSIX_TIMERS General real-time problems -------------------------- Apart from implementing new POSIX.1b system calls, there are a number of other problems with the current Linux kernel that have to be solved in order to improve real-time performance. Problem 1: Interrupt dispatch latency A blocked process waiting for the end of some I/O request becomes runnable again when the CPU receives an interrupt from the I/O device that processed the request. The time that passes between the interrupt and the execution of the interrupt handler is called the "interrupt latency". The time that passes between the interrupt and the continuation of the execution of the blocked process is called the "interrupt dispatch latency". We are assuming that the blocked process is the process with the highest priority (the POSIX.1b scheduler system calls allow to ensure this). Many real-time applications require that the interrupt dispatch latency is as short as possible, some applications require even guarantees for the maximum interrupt dispatch latency (e.g. 20 microseconds). At the moment, Linux has basically two types of interrupt handlers: "fast" and "slow" ones. The "slow interrupt handlers" call the scheduler each time immediately after the interrupt has been handled. This guarantees that if the process has become runnable by handling the interrupt and has the highest priority, then it will directly get control over the CPU after the interrupt handler. This ensures a short interrupt dispatch latency, but the cost is that the scheduler is executed for each interrupt, which can cause a system performance degradation for devices with a high interrupt rate (e.g., network controllers). The slow interrupt handler do not disable other interrupts while they are being executed. This ensures a low interrupt latency, because other higher priority interrupts will not be blocked. The "slow" interrupt handler behavior is what you want for real-time applications. The "fast interrupt handlers" only mark in a bitmask that an interrupt has been handled for this device. The scheduler is NOT called after the fast interrupt handler and the process waiting on the interrupt may have to wait up to 1 s / HZ = 10 ms for the next timer interrupt which will call the scheduler again (because the timer interrupt is handled the "slow" way). "Fast" interrupt handlers are those which are installed by the driver by specifying the SA_INTERRUPT option when calling request_irq(). "Fast" interrupt handlers are the reason why for devices like the serial port, the interrupt dispatch latency can easily reach 10 ms and more. "Fast" interrupt handlers disable other interrupts while the handler is being executed. This increases interrupt latency. The Linux "fast" interrupt handlers cause very low interrupt handling overhead, but they can be the cause for a lot of headaches for real-time application developers. See linux/arch/i386/kernel/irq.c, linux/include/asm-i386/irq.h and linux/arch/i386/kernel/entry.S for implementation details of how fast and slow interrupts are handled in Linux. Examples for "slow" Linux 1.3 interrupt drivers with good interrupt dispatch latency are keyboard floppy disk timer sound cards mouse drivers some Ethernet cards Examples for "fast" interrupt drivers with bad interrupt dispatch latency are serial port some Ethernet cards most harddisk/SCSI drivers most CD-ROM drivers Especially for the serial port, it would be very nice to have a way to switch to low dispatch latency interrupt handling, such that an application can react as fast as possible on any incoming serial byte. Apart from the "fast" interrupt handler type, another important cause of latency in the serial port are the 16550 FIFO UARTs. At the moment, the UARTs are configured to trigger an interrupt (except for for bit rates < 2400 bit/s) only if the FIFO is filled with at least eight bytes or if an UART timeout has occured (this happens after four character transmission times). The 16550 chip can be configured to trigger limits 1, 4, 8, and 14, but Linux currently provides no ioctl() for this. For details about the FIFO UART, please consult the National Semiconductor PC16550D data sheet. For real-time applications, it would be very desirable to change the FIFO trigger limit to one byte so that incoming serial bytes are immediately delivered to the waiting process. Applications that depend heavily on minimum serial port interrupt dispatch latency are for example MIDI music systems, DCF77 reference time long-wave radio signal receivers in Europe, packet radio network interfaces, and ISO 7816 smartcard interfaces. Some existing work in this area: Stuart Cheshire has implemented a "smart" interrupt handler that can switch between the classic "fast" and "slow" alternatives (see for details). This way, you can get the real-time advantage of "slow" handling for the serial port without introducing a permanent system overhead even when no real-time application is active. Nick Simicich and Rik Faith have written a program called "cytune" which can change the FIFO thresholds for individual ports in the Cyclades async mux driver. Problem 2: Timer resolution On most Linux architectures, a timer interrupt occurs every 10 ms (HZ = 100). One exception is the Alpha architecture, where the timer interrupt comes every 1 ms (HZ = 1024). The macro HZ, which specifies the timer frequency, is defined in . At the moment, the kernel timer mechanism, on which the itimer and nanosleep implementation is based, checks after each timer interrupt whether a software timer has expired, makes the corresponding process runnable again, and calls the scheduler. This means that a highest priority real-time process can have to wait up to 2 * (1 s / HZ) = 20 ms longer than requested. An excellent solution would be to implement an interrupt-on-demand timer facility. The 8253 timer/counter chip in the PC would then have to be programmed such that it delivers an interrupt with microsecond precision exactly at the time when a software timer expires. This would increase the software timer precision by a factor of 10 000! As the 8253 timer would be programmed in a single shot mode, a lost interrupt might cause an accidental system halt. If this is problem, the CMOS battery clock, which can also be used to implement periodic interrupts, should be utilized to trigger periodic calls to the scheduler in order to ensure process preemption and kernel clock update. The time stamp counter (TSC) available in all Pentium processors is a 64-bit counter clocked at CPU frequency. It can be used on Pentium systems in order to get extremely precise timing information with theoretically close to nanosecond resolution and without overflow problems. Literature ---------- For those of you who have become interested in POSIX.1b, there exists a good book: Bill O. Gallmeister, POSIX.4 -- Programming for the Real World, O'Reilly & Associates, 1995, ISBN 1-56592-074-0. This book is not only a good introduction into POSIX.1b (which was originally called POSIX.4), it is also an easy reading nice way into the world of real-time operating systems for those developers who have so far been very UNIX and time-sharing oriented. You can order the POSIX.1b standard (officially called IEEE Std 1003.1b-1993; this book includes also all text of POSIX.1 and costs 114 USD) as well as the other POSIX standards directly from IEEE: phone: +1 908 981 1393 (TZ: eastern standard time) 1 800 678 4333 (from US+Canada only) fax: +1 908 981 9667 e-mail: stds.info@ieee.org Information about POSIX and other IEEE standards is also available on and , however unfortunately the full standard documents are only available as books or on CD-ROM, not on the Internet. Having access to the POSIX specs is certainly a good idea for any Linux kernel hacker. Here is a brief list of some of the POSIX standards: POSIX.1 Basic OS interface (C language) POSIX.1a Misc. extensions (symlinks, etc.) POSIX.1b Real-time and I/O extensions (was: POSIX.4) POSIX.1c Threads (was: POSIX.4a) POSIX.1d More real-time extensions (was: POSIX.4b) POSIX.1e Security extensions, ACLs (was: POSIX.6) POSIX.1f Transparent network file access (was: POSIX.8) POSIX.1g Protocol independent communication, sockets (was: POSIX.12) POSIX.1i Technical corrections to POSIX.1b POSIX.2 Shell and common utility programs (date, ln, ...) POSIX.3 Test methods POSIX.5 ADA binding to POSIX.1 POSIX.7 System administration POSIX.9 FORTRAN-77 binding to POSIX.1 POSIX.15 Supercomputing extensions (checkpoint/recovery, etc.) and a few others which are still in early draft stage. If you want to follow progress on POSIX standardization, you should read the announcements in the moderated USENET group comp.std.unix. The current status of POSIX drafts is summarized in . ISO has also published POSIX.1 as ISO/IEC 9945-1:1990. ISO and IEEE will soon publish the new revision of this standard: ISO/IEC 9945-1:1996. This will be the new 1996 revision of POSIX.1, which will contain in one single standard POSIX.1(1990), POSIX.1b(1993), POSIX.1c(1995), and POSIX.1i(1995) (perhaps also POSIX.1a(1996) if it gets ready in time). If you want to order the POSIX standard but are not in a hurry, may be it is a good idea to wait a few months until ISO/IEC 9945-1:1996 is available. All differences between POSIX.1(1990) and POSIX.1(1996) will be marked by bars at the page margins. This text just summarizes POSIX.1b and related work on Linux. Many people interested in POSIX.1b support seem also to be interested in POSIX.1c support (threads). Some information about POSIX.1c support is on and . There is now a production release package called "PCthreads (tm) POSIX threads for Linux" available from . It is maintained by Michael T. Peterson . A POSIX.1c package that provides real kernel-threads using the clone() system call is available from and has been developed by Xavier Leroy . From owner-linux@cthulhu.engr.sgi.com Mon Aug 5 17:00:31 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA09688; Mon, 5 Aug 1996 17:00:30 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA07267 for linux-list; Mon, 5 Aug 1996 23:51:20 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA07262 for ; Mon, 5 Aug 1996 16:51:19 -0700 Received: (from lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA07180 for linux; Mon, 5 Aug 1996 16:51:19 -0700 Date: Mon, 5 Aug 1996 16:51:19 -0700 From: lm@neteng.engr.sgi.com (Larry McVoy) Message-Id: <199608052351.QAA07180@neteng.engr.sgi.com> To: linux@neteng.engr.sgi.com Subject: coolness Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk For an unrelated-to-Linux project that I'm working on with some other folks over here, we needed a user level NFS server. So I stole David's GCC for IRIX compilation environment and built the Linux user level NFS server code on IRIX. I uninstalled NFS (which unfortunately also removes YP, that's a bummer, I had to copy over hosts) and started up Linux's version. You can play with it right now. Try % cd /hosts/fubar.engr % ls Pretty cool, huh? --lm --- Larry McVoy lm@sgi.com http://reality.sgi.com/lm (415) 933-1804 From owner-linux@cthulhu.engr.sgi.com Mon Aug 12 13:33:48 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA09604; Mon, 12 Aug 1996 13:33:48 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA15296 for linux-list; Mon, 12 Aug 1996 20:33:42 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA15286 for ; Mon, 12 Aug 1996 13:33:40 -0700 Received: from refugee.engr.sgi.com (refugee.engr.sgi.com [150.166.61.22]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA29529 for ; Mon, 12 Aug 1996 13:31:56 -0700 Received: from refugee.engr.sgi.com by refugee.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id NAA17431; Mon, 12 Aug 1996 13:32:01 -0700 Message-Id: <199608122032.NAA17431@refugee.engr.sgi.com> X-Mailer: exmh version 1.6.7 5/3/96 To: lm@gate1-neteng.engr.sgi.com (Larry McVoy) Cc: Nigel Gamble , Alistair Lambie , ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: Linux: the next step In-reply-to: Message from lm@gate1-neteng of 2 Aug 1996 18:11:31 PDT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Aug 1996 13:32:01 -0700 From: Steve Alexander Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk lm@gate1-neteng (Larry McVoy) writes: >The fine grained locking is a lose. It costs us way too much and what I >am seeing is a trend backwards towards coarser grained locking. If this >wasn't true, why did we build lego? Why are we building Nexus? I'd like to see some hard numbers for these assertions. All of the bottlenecks in ficus (that I am aware of) have to do with context-switching due to use of mutexes rather than spinlocks. The locking overhead itself isn't even on the map as far as I can tell. However, I agree that more locking is not the answer. Eliminating as much shared, global data as possible is the answer. Nexus doesn't really do anything towards that end that I can see. >Linux already has a RT kernel. I just reviewed a fantastic Usenix paper >that added RT to Linux - fully preemptable, hard real time to < 100 usecs, >and less than 3K lines of code change. Their test case was a 100Khz clock >pulse on a parallel port; they got it every time, with less than 15usecs >skew, while the system was tar-ing one file system to another, running >netscape, and generally doing same old Unix stuff just like normal. It's >really impressive and very uninvasive. I'd like to see that when it comes out. >Finally, think about this: how many times have you had a "great idea" >for better IRIX performance, gone off an prototyped it, only to find >that it makes no difference? Linux lets you test out those ideas and >see the real performance difference, unadulterated by any surrounding >bloat. That's cool. We want that. If it makes no difference, what difference does it make what platform you try it on? If it does make a difference, you would be able to measure it despite the underlying bloat, and again the underlying platform makes no difference. I'm in favor of some amount of Linux work on SGI gear, but this is a pretty weak argument. -- Steve From owner-linux@cthulhu.engr.sgi.com Mon Aug 12 13:53:19 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA10554; Mon, 12 Aug 1996 13:53:18 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA19246 for linux-list; Mon, 12 Aug 1996 20:53:13 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA19241 for ; Mon, 12 Aug 1996 13:53:12 -0700 Received: from ratliff.engr.sgi.com (ratliff.engr.sgi.com [150.166.42.14]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA29578 for ; Mon, 12 Aug 1996 13:51:27 -0700 Received: from localhost by ratliff.engr.sgi.com via SMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id NAA08696; Mon, 12 Aug 1996 13:52:47 -0700 Message-Id: <199608122052.NAA08696@ratliff.engr.sgi.com> To: Steve Alexander cc: lm@gate1-neteng.engr.sgi.com (Larry McVoy), Nigel Gamble , Alistair Lambie , ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: Linux: the next step In-reply-to: Your message of "Mon, 12 Aug 96 13:32:01 PDT." <199608122032.NAA17431@refugee.engr.sgi.com> Date: Mon, 12 Aug 96 13:52:47 -0700 From: Bob English Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk >lm@gate1-neteng (Larry McVoy) writes: >The fine grained locking is a lose. It costs us way too much and what I >am seeing is a trend backwards towards coarser grained locking... In message <199608122032.NAA17431@refugee.engr.sgi.com> you write: >I'd like to see some hard numbers for these assertions. All of the bottlenecks >in ficus (that I am aware of) have to do with context-switching due to use of >mutexes rather than spinlocks. The locking overhead itself isn't even on the >map as far as I can tell. If you look at larry's context switch and pipe benchmarks, you'll see that they run much faster on a single CPU than on two or more. A lot of the difference is due to fine-grained locking, which causes more dirty cache lines to thrash than is actually necessary for the operations involved. Pipe communication takes locks at the vnode and inode level. Context switches take locks on threads, accounting structures, and queues. It all adds up. >If it makes no difference, what difference does it make what platform you try >it on? If it does make a difference, you would be able to measure it despite >the underlying bloat, and again the underlying platform makes no difference. Back to the previous discussion. Getting rid of any one of those locks wouldn't make much difference. Getting rid of all of them would, but is a much taller order. --bob-- From owner-linux@cthulhu.engr.sgi.com Mon Aug 12 14:10:11 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA13409; Mon, 12 Aug 1996 14:10:11 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id VAA22942 for linux-list; Mon, 12 Aug 1996 21:10:06 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA22927 for ; Mon, 12 Aug 1996 14:10:04 -0700 Received: from neteng.engr.sgi.com (gate5-neteng.engr.sgi.com [150.166.61.33]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA29622 for ; Mon, 12 Aug 1996 14:08:20 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id OAA13322; Mon, 12 Aug 1996 14:09:39 -0700 Message-Id: <199608122109.OAA13322@neteng.engr.sgi.com> To: Steve Alexander From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: lm@neteng.engr.sgi.com, Nigel Gamble , Alistair Lambie , ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: Linux: the next step Date: Mon, 12 Aug 1996 14:09:39 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : However, I agree that more locking is not the answer. Eliminating as much : shared, global data as possible is the answer. Nexus doesn't really do : anything towards that end that I can see. Yeah. : >Linux already has a RT kernel. I just reviewed a fantastic Usenix paper : >that added RT to Linux - fully preemptable, hard real time to < 100 usecs, : >and less than 3K lines of code change. Their test case was a 100Khz clock : >pulse on a parallel port; they got it every time, with less than 15usecs : >skew, while the system was tar-ing one file system to another, running : >netscape, and generally doing same old Unix stuff just like normal. It's : >really impressive and very uninvasive. : : I'd like to see that when it comes out. You'll have to borrow my copy, Usenix rejected it. Fuckheads. : >Finally, think about this: how many times have you had a "great idea" : >for better IRIX performance, gone off an prototyped it, only to find : >that it makes no difference? Linux lets you test out those ideas and : >see the real performance difference, unadulterated by any surrounding : >bloat. That's cool. We want that. : : If it makes no difference, what difference does it make what platform you try : it on? If it does make a difference, you would be able to measure it despite : the underlying bloat, and again the underlying platform makes no difference. Suppose you are trying to reach some performance point, X. Whatever that is. You do some work that would, in theory, get you closer to point X. It doesn't, you can't see the difference. Just for the sake of argument, suppose that that work was indeed correctly focussed on something that needed to get fixed in order to get to point X. But the effects of that work were overshadowed by all of the surrounding bloat. That doesn't mean that the work was useless or wrong, it means that the bloat dominates. If the bloat wasn't there, you would need to do the work to get to X. A more concrete example: IRIX syscall entry is something like 15-30 usecs, if I remember correctly. On Linux, it's about .5 - 5 usecs. In the Linux world, optimizations that made a 100% difference would be lost in the bloat in IRIX. Does that mean that those optimizations are pointless? Not to me, it doesn't. I want a kernel that is fast enough that dropping into to diddle something and then popping back out is about a procedure call, no more. IRIX is miles from that, Linux is approaching it. From owner-linux@cthulhu.engr.sgi.com Mon Aug 12 14:20:22 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA13577; Mon, 12 Aug 1996 14:20:22 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id VAA24984 for linux-list; Mon, 12 Aug 1996 21:20:08 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA24960 for ; Mon, 12 Aug 1996 14:20:06 -0700 Received: from refugee.engr.sgi.com (refugee.engr.sgi.com [150.166.61.22]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA29660 for ; Mon, 12 Aug 1996 14:18:21 -0700 Received: from refugee.engr.sgi.com by refugee.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id OAA18053; Mon, 12 Aug 1996 14:18:18 -0700 Message-Id: <199608122118.OAA18053@refugee.engr.sgi.com> X-Mailer: exmh version 1.6.7 5/3/96 To: Bob English Cc: lm@gate1-neteng.engr.sgi.com (Larry McVoy), Nigel Gamble , Alistair Lambie , ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: Linux: the next step In-reply-to: Message from renglish@ratliff of 12 Aug 1996 13:52:47 PDT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Aug 1996 14:18:18 -0700 From: Steve Alexander Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Bob English writes: >If you look at larry's context switch and pipe benchmarks, you'll see >that they run much faster on a single CPU than on two or more. A lot of >the difference is due to fine-grained locking, which causes more dirty >cache lines to thrash than is actually necessary for the operations >involved. Pipe communication takes locks at the vnode and inode >level. Context switches take locks on threads, accounting structures, >and queues. If I look at those benchmarks, they'll probably run faster on Linux on an Indy than they do on IRIX on an Indy, so I doubt the locking is the big problem we need to be looking at. I don't have numbers from David to quote, so maybe I'm wrong. I'd like to be wrong. -- Steve From owner-linux@cthulhu.engr.sgi.com Mon Aug 12 14:22:32 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA13760; Mon, 12 Aug 1996 14:22:32 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id VAA25633 for linux-list; Mon, 12 Aug 1996 21:22:20 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA25618 for ; Mon, 12 Aug 1996 14:22:18 -0700 Received: from refugee.engr.sgi.com (refugee.engr.sgi.com [150.166.61.22]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA29714 for ; Mon, 12 Aug 1996 14:20:33 -0700 Received: from refugee.engr.sgi.com by refugee.engr.sgi.com via ESMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id OAA18080; Mon, 12 Aug 1996 14:20:39 -0700 Message-Id: <199608122120.OAA18080@refugee.engr.sgi.com> X-Mailer: exmh version 1.6.7 5/3/96 To: lm@gate1-neteng.engr.sgi.com (Larry McVoy) Cc: lm@neteng.engr.sgi.com, Nigel Gamble , Alistair Lambie , ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: Linux: the next step In-reply-to: Message from lm@gate1-neteng of 12 Aug 1996 14:09:39 PDT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Aug 1996 14:20:39 -0700 From: Steve Alexander Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk lm@gate1-neteng (Larry McVoy) writes: >You'll have to borrow my copy, Usenix rejected it. Fuckheads. No doubt to make room for some paper on TCL scripts or something. Feh. Yeah, if you can make me a copy or convince the authors to send me one I'd appreciate it. >A more concrete example: IRIX syscall entry is something like 15-30 usecs, >if I remember correctly. On Linux, it's about .5 - 5 usecs. In the >Linux world, optimizations that made a 100% difference would be lost in >the bloat in IRIX. Does that mean that those optimizations are pointless? To some degree, yes. This is why application developers often have a lot of platform-specific code; optimizations that work on one system won't necessarily work on all systems. I'm not saying this is good, mind you. -- Steve From owner-linux@cthulhu.engr.sgi.com Mon Aug 12 14:25:26 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA13804; Mon, 12 Aug 1996 14:25:26 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id VAA26341 for linux-list; Mon, 12 Aug 1996 21:25:22 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA26334 for ; Mon, 12 Aug 1996 14:25:20 -0700 Received: from ratliff.engr.sgi.com (ratliff.engr.sgi.com [150.166.42.14]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA29751 for ; Mon, 12 Aug 1996 14:23:35 -0700 Received: from localhost by ratliff.engr.sgi.com via SMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id OAA08877; Mon, 12 Aug 1996 14:24:15 -0700 Message-Id: <199608122124.OAA08877@ratliff.engr.sgi.com> To: Steve Alexander cc: Bob English , lm@gate1-neteng.engr.sgi.com (Larry McVoy), Nigel Gamble , Alistair Lambie , ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com, renglish@ratliff.engr.sgi.com Subject: Re: Linux: the next step In-reply-to: Your message of "Mon, 12 Aug 96 14:18:18 PDT." <199608122118.OAA18053@refugee.engr.sgi.com> Date: Mon, 12 Aug 96 14:24:15 -0700 From: Bob English Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk In message <199608122118.OAA18053@refugee.engr.sgi.com> you write: >If I look at those benchmarks, they'll probably run faster on Linux on an Indy >than they do on IRIX on an Indy, so I doubt the locking is the big problem we >need to be looking at. I don't have numbers from David to quote, so maybe I'm >wrong. I'd like to be wrong. I was comparing Irix MP times vs. Irix UP times, and the difference is both substantial and locking related. Of course, if Irix were as efficient on a UP as Linux, the difference might be a factor of 10 rather than a factor of 2 :-). --bob-- From owner-linux@cthulhu.engr.sgi.com Mon Aug 12 14:36:07 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA15199; Mon, 12 Aug 1996 14:36:07 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id VAA29439 for linux-list; Mon, 12 Aug 1996 21:36:01 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA29434 for ; Mon, 12 Aug 1996 14:36:00 -0700 Received: from surfdog.csd.sgi.com (surfdog.csd.sgi.com [150.166.145.79]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA29781 for ; Mon, 12 Aug 1996 14:34:15 -0700 Received: by surfdog.csd.sgi.com (940816.SGI.8.6.9/911001.SGI) id OAA05211; Mon, 12 Aug 1996 14:35:34 -0700 From: "Sandeep Cariapa" Message-Id: <9608121435.ZM5209@surfdog.csd.sgi.com> Date: Mon, 12 Aug 1996 14:35:34 -0700 In-Reply-To: Steve Alexander "Re: Linux: the next step" (Aug 12, 2:20pm) References: <199608122120.OAA18080@refugee.engr.sgi.com> X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: linux@yon.engr.sgi.com Subject: Re: Linux: the next step Cc: lm@neteng.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Aug 12, 2:20pm, Steve Alexander wrote: > Subject: Re: Linux: the next step > lm@gate1-neteng (Larry McVoy) writes: > >You'll have to borrow my copy, Usenix rejected it. Fuckheads. No, tell us what you really feel Larry; don't hold back :-) > No doubt to make room for some paper on TCL scripts or something. Feh. > Yeah, if you can make me a copy or convince the authors to send me one I'd > appreciate it. Larry, you might want to make this available to the entire Linux mailing list; I suspect a lot more people would be interested in it. (I am too) Regards, Sandeep >-- End of excerpt from Steve Alexander From owner-linux@cthulhu.engr.sgi.com Mon Aug 12 14:39:44 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA15284; Mon, 12 Aug 1996 14:39:44 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id VAA29929 for linux-list; Mon, 12 Aug 1996 21:39:40 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA29924 for ; Mon, 12 Aug 1996 14:39:39 -0700 Received: from machine.engr.sgi.com (fddi-machine.engr.sgi.com [192.26.75.22]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA29798 for ; Mon, 12 Aug 1996 14:37:54 -0700 Received: by machine.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) id OAA12095; Mon, 12 Aug 1996 14:39:21 -0700 From: jes@machine.engr.sgi.com (John E. Schimmel) Message-Id: <199608122139.OAA12095@machine.engr.sgi.com> Subject: Re: Linux: the next step To: sca@refugee.engr.sgi.com (Steve Alexander) Date: Mon, 12 Aug 1996 14:39:21 -0700 (PDT) Cc: lm@gate1-neteng.engr.sgi.com, lm@neteng.engr.sgi.com, nigel@cthulhu.engr.sgi.com, alambie@wellington.sgi.com, ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com In-Reply-To: <199608122120.OAA18080@refugee.engr.sgi.com> from "Steve Alexander" at Aug 12, 96 02:20:39 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 1012 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > > lm@gate1-neteng (Larry McVoy) writes: > >You'll have to borrow my copy, Usenix rejected it. Fuckheads. > > No doubt to make room for some paper on TCL scripts or something. Feh. > Yeah, if you can make me a copy or convince the authors to send me one I'd > appreciate it. Now wait a minute here. Read the paper before commenting. They create a "real-time" thread under Linux. That does not mean that it does anything, that the OS has real time support, etc. There was nothing particularly new about what it did. There is now a Linux conference which should showcase this sort of thing. Usenix is for new and interesting work that would be of interest to a large audience. > > -- Steve > > ------------------------------------------------------------ John E. Schimmel jes@sgi.com Silicon Graphics Inc. Voice: (415)933-4116 http://reality.sgi.com/employees/jes Fax: (415)967-8496 ------------------------------------------------------------ From owner-linux@cthulhu.engr.sgi.com Mon Aug 12 14:50:22 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA15492; Mon, 12 Aug 1996 14:50:22 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id VAA02665 for linux-list; Mon, 12 Aug 1996 21:50:07 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA02659 for ; Mon, 12 Aug 1996 14:50:05 -0700 Received: from neteng.engr.sgi.com (gate5-neteng.engr.sgi.com [150.166.61.33]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA29836 for ; Mon, 12 Aug 1996 14:48:17 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id OAA15461; Mon, 12 Aug 1996 14:49:45 -0700 Message-Id: <199608122149.OAA15461@neteng.engr.sgi.com> To: jes@machine.engr.sgi.com (John E. Schimmel) From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: sca@refugee.engr.sgi.com (Steve Alexander), lm@neteng.engr.sgi.com, nigel@cthulhu.engr.sgi.com, alambie@wellington.sgi.com, ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: Linux: the next step Date: Mon, 12 Aug 1996 14:49:45 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : > No doubt to make room for some paper on TCL scripts or something. Feh. : > Yeah, if you can make me a copy or convince the authors to send me one I'd : > appreciate it. : : Now wait a minute here. Read the paper before commenting. : They create a "real-time" thread under Linux. That does not : mean that it does anything, that the OS has real time support, : etc. There was nothing particularly new about what it did. Here's what they did: they took over control of interrupt disable/enable and dispatch. They run Linux as a thread and allow you to have 0 or more real time threads. If all you are doing is running Linux, it looked to me like there was minimal impact to the performance of the system. Real time threads run on the bare hardware, they have little integration with the OS, other than a pipe like communications device. The programming paradigm is you run two processes, one real time that gathers events and stuffs them in the "pipe", and one normal that reads events out of the pipe and does time _un_critical processing. They can guarentee real time response of 10Khz, with less than 15 usec variation. That was with Linux running a tar f - /usr | (cd /newusr; tar xf -) a web browser, X, etc, etc. Good luck doing that on IRIX up. Maybe MP. I thought the new work was the idea of *not* buggering up your entire OS to support real time. They give the real time guys ownership of the CPU with minimal impact on the rest of the system. And they had to do next to nothing to make this work, they just use Unix for everything except the lowest level of RT work. I dunno, maybe I'm projecting some pipe dream, but I think this is really cool work. Points for orthogonal thinking on their part. From owner-linux@cthulhu.engr.sgi.com Mon Aug 12 16:00:31 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA01324; Mon, 12 Aug 1996 16:00:30 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA16841 for linux-list; Mon, 12 Aug 1996 22:59:25 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA16829 for ; Mon, 12 Aug 1996 15:59:23 -0700 Received: from aa5b.engr.sgi.com (aa5b.engr.sgi.com [192.102.117.24]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA29987 for ; Mon, 12 Aug 1996 15:57:39 -0700 Received: (from nigel@localhost) by aa5b.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA28318; Mon, 12 Aug 1996 15:59:04 -0700 From: nigel@aa5b.engr.sgi.com (Nigel Gamble) Message-Id: <199608122259.PAA28318@aa5b.engr.sgi.com> Subject: Re: Linux: the next step To: lm@gate1-neteng.engr.sgi.com (Larry McVoy) Date: Mon, 12 Aug 1996 15:59:04 -0700 (PDT) Cc: jes@machine.engr.sgi.com, sca@refugee.engr.sgi.com, lm@neteng.engr.sgi.com, nigel@cthulhu.engr.sgi.com, alambie@wellington.sgi.com, ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com In-Reply-To: <199608122149.OAA15461@neteng.engr.sgi.com> from "Larry McVoy" at Aug 12, 96 02:49:45 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 2161 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > : Now wait a minute here. Read the paper before commenting. > : They create a "real-time" thread under Linux. That does not > : mean that it does anything, that the OS has real time support, > : etc. There was nothing particularly new about what it did. > > Here's what they did: they took over control of interrupt disable/enable > and dispatch. They run Linux as a thread and allow you to have 0 or more > real time threads. If all you are doing is running Linux, it looked > to me like there was minimal impact to the performance of the system. > > Real time threads run on the bare hardware, they have little > integration with the OS, other than a pipe like communications device. > The programming paradigm is you run two processes, one real time that > gathers events and stuffs them in the "pipe", and one normal that reads > events out of the pipe and does time _un_critical processing. That's fine for one class of real-time problems, but it's not going to help make the RealAudio player (raplayer) useable on Linux. RealAudio only has to produce AM radio quality audio from a 28.8kbps input stream, yet I only have to move my mouse into a new window to get audio drop-out. The RealAudio application, together with all the support that it is getting from the kernel in audio drivers, networking code etc., needs to run at a higher priority than most of the other stuff that might be going on. This is also a "real time problem", although a different one from the "get the O/S out of my way" hard real time crowd. How will Linux solve this type of problem? > They can guarentee real time response of 10Khz, with less than 15 usec > variation. That was with Linux running a > > tar f - /usr | (cd /newusr; tar xf -) > > a web browser, X, etc, etc. Good luck doing that on IRIX up. Maybe MP. We can already do this on MP with User Level Interrupts. As for UP, stay tuned :-) (Since this mailing list goes outside of SGI, I'm not going to say any more.) -- Nigel Gamble "Are we going to push the edge of the envelope, Brain?" Silicon Graphics "No, Pinky, but we may get to the sticky part." nigel@sgi.com (415) 933-3109 From owner-linux@cthulhu.engr.sgi.com Mon Aug 12 16:32:58 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA03109; Mon, 12 Aug 1996 16:32:58 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA23375 for linux-list; Mon, 12 Aug 1996 23:31:52 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA23367 for ; Mon, 12 Aug 1996 16:31:51 -0700 Received: from ratliff.engr.sgi.com (ratliff.engr.sgi.com [150.166.42.14]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA00094 for ; Mon, 12 Aug 1996 16:30:06 -0700 Received: from localhost by ratliff.engr.sgi.com via SMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id QAA09379; Mon, 12 Aug 1996 16:31:31 -0700 Message-Id: <199608122331.QAA09379@ratliff.engr.sgi.com> To: nigel@aa5b.engr.sgi.com (Nigel Gamble) cc: lm@gate1-neteng.engr.sgi.com (Larry McVoy), jes@machine.engr.sgi.com, sca@refugee.engr.sgi.com, lm@neteng.engr.sgi.com, alambie@wellington.sgi.com, ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com Subject: Re: Linux: the next step In-reply-to: Your message of "Mon, 12 Aug 96 15:59:04 PDT." <199608122259.PAA28318@aa5b.engr.sgi.com> Date: Mon, 12 Aug 96 16:31:30 -0700 From: Bob English Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk In message <199608122259.PAA28318@aa5b.engr.sgi.com> you write: >That's fine for one class of real-time problems, but it's not going >to help make the RealAudio player (raplayer) useable on Linux... >The RealAudio application, together with all the support that it is >getting from the kernel in audio drivers, networking code etc., needs >to run at a higher priority than most of the other stuff that might be >going on... > >How will Linux solve this type of problem? With mirrors. You run another copy of Linux on a high-priority RT thread. Full API, fast preemption, minimal performance and code impact. You work on linux-slow and run rt apps on linux-fast. You could even reboot linux-slow without losing your audio signal :-). --bob-- From owner-linux@cthulhu.engr.sgi.com Mon Aug 12 16:56:47 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA03662; Mon, 12 Aug 1996 16:56:47 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA27436 for linux-list; Mon, 12 Aug 1996 23:55:53 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA27431 for ; Mon, 12 Aug 1996 16:55:51 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA00152 for linux; Mon, 12 Aug 1996 16:54:07 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199608122354.QAA00152@yon.engr.sgi.com> Subject: Linux external vs. internal lists To: linux@yon.engr.sgi.com Date: Mon, 12 Aug 1996 16:54:06 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 750 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk [This is being sent to linux@engr.sgi.com only] Just to follow up on Nigel's last comment. Please note: linux@engr is strictly internal to sgi.com while: linuxmips@corp is unrestricted and subscribed to by Red Hat, Miguel de Icaza, ex SGI employees, and a few other interested parties. I once believed I'm allowing external addresses on linux@engr but it turned out that majordomo@engr silently rejects them. Feel free, at your discretion, to discuss internal stuff on linux@engr. Also: please continue to keep linuxmips@corp low-volume (it was originally intended only for significant announcements like "Linux now boots single user on Indy") I believe there was only one announcement on it since it was created. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Aug 13 04:46:11 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA01457; Tue, 13 Aug 1996 04:46:11 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id LAA02414 for linux-list; Tue, 13 Aug 1996 11:46:02 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA02407 for ; Tue, 13 Aug 1996 04:45:59 -0700 Received: from neteng.engr.sgi.com (gate5-neteng.engr.sgi.com [150.166.61.33]) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA00933 for ; Tue, 13 Aug 1996 04:44:15 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id EAA01442; Tue, 13 Aug 1996 04:45:56 -0700 Date: Tue, 13 Aug 1996 04:45:56 -0700 Message-Id: <199608131145.EAA01442@neteng.engr.sgi.com> From: "David S. Miller" To: nigel@aa5b.engr.sgi.com CC: lm@neteng.engr.sgi.com, jes@machine.engr.sgi.com, sca@refugee.engr.sgi.com, lm@neteng.engr.sgi.com, nigel@cthulhu.engr.sgi.com, alambie@wellington.sgi.com, ariel@cthulhu.engr.sgi.com, linux@yon.engr.sgi.com In-reply-to: <199608122259.PAA28318@aa5b.engr.sgi.com> (nigel@aa5b) Subject: Re: Linux: the next step Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: nigel@aa5b (Nigel Gamble) Date: Mon, 12 Aug 1996 15:59:04 -0700 (PDT) > They can guarentee real time response of 10Khz, with less than 15 usec > variation. That was with Linux running a > > tar f - /usr | (cd /newusr; tar xf -) > > a web browser, X, etc, etc. Good luck doing that on IRIX up. Maybe MP. We can already do this on MP with User Level Interrupts. I cannot wait to recompile all of my applications so that they can take advantage of ULI... The whole idea behind whatever approach linux will take to anything (using clone() for threads under Linux is a good example) is that you will not need to teach all of your "dumb" old programs (even ps!) about these special processes and or things a process can do. dm@engr.sgi.com 'Ooohh.. "FreeBSD is faster over loopback, when compared to Linux over the wire". Film at 11.' -Linus From owner-linux@cthulhu.engr.sgi.com Tue Aug 13 08:37:04 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id IAA05128; Tue, 13 Aug 1996 08:37:04 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA21898 for linux-list; Tue, 13 Aug 1996 15:36:38 GMT Received: from aa5b.engr.sgi.com (aa5b.engr.sgi.com [192.102.117.24]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id IAA21887 for ; Tue, 13 Aug 1996 08:36:36 -0700 Received: (from nigel@localhost) by aa5b.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id IAA29651; Tue, 13 Aug 1996 08:36:36 -0700 From: nigel@aa5b.engr.sgi.com (Nigel Gamble) Message-Id: <199608131536.IAA29651@aa5b.engr.sgi.com> Subject: Re: Linux: the next step To: dm@sgi.com Date: Tue, 13 Aug 1996 08:36:35 -0700 (PDT) Cc: linux@aa5b.engr.sgi.com In-Reply-To: <199608131145.EAA01442@neteng.engr.sgi.com> from "David S. Miller" at Aug 13, 96 04:45:56 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 2160 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > From: nigel@aa5b (Nigel Gamble) > Date: Mon, 12 Aug 1996 15:59:04 -0700 (PDT) > > > They can guarentee real time response of 10Khz, with less than 15 usec > > variation. That was with Linux running a > > > > tar f - /usr | (cd /newusr; tar xf -) > > > > a web browser, X, etc, etc. Good luck doing that on IRIX up. Maybe MP. > > We can already do this on MP with User Level Interrupts. > > I cannot wait to recompile all of my applications so that they can > take advantage of ULI... I think you missed my point. The real time approach that Larry described will only suit the hard real time programmers who want only to get the O/S out of the way and program the bare metal. The real time application code will have to be custom written and will get no support from Linux itself - you can't call Linux system calls from one of these real time threads. Forget POSIX real time APIs! IRIX's ULI mechanism already provides a similar facility for people who are willing to trade O/S support for performance, (since you can't execute IRIX system calls from a ULI, either). > The whole idea behind whatever approach linux will take to anything > (using clone() for threads under Linux is a good example) is that you > will not need to teach all of your "dumb" old programs (even ps!) > about these special processes and or things a process can do. The next release of IRIX will have real time support for user applications, even on a UP, with guarantees sufficient for digital media (audio and video). You won't need to recompile your application to take advantage of this environment. We already know what we need to do to achieve this, and have already implemented most of it. Our approach is based on a fully preemptible kernel, interrupts that have a thread context that can block, and making sure that interrupts are never disabled for more than 100us. I'm still waiting to hear "whatever approach linux will take" to solve this problem. -- Nigel Gamble "Are we going to push the edge of the envelope, Brain?" Silicon Graphics "No, Pinky, but we may get to the sticky part." nigel@sgi.com (415) 933-3109 From owner-linux@cthulhu.engr.sgi.com Tue Aug 13 09:46:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA08170; Tue, 13 Aug 1996 09:46:17 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA03191 for linux-list; Tue, 13 Aug 1996 16:45:59 GMT Received: from aa5b.engr.sgi.com (aa5b.engr.sgi.com [192.102.117.24]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA03117 for ; Tue, 13 Aug 1996 09:45:50 -0700 Received: from xtp.engr.sgi.com (xtp.engr.sgi.com [150.166.75.34]) by aa5b.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA29778; Tue, 13 Aug 1996 09:45:46 -0700 Received: by xtp.engr.sgi.com (940816.SGI.8.6.9/911001.SGI) id JAA07240; Tue, 13 Aug 1996 09:45:46 -0700 From: "Greg Chesson" Message-Id: <9608130945.ZM7238@xtp.engr.sgi.com> Date: Tue, 13 Aug 1996 09:45:44 -0700 In-Reply-To: nigel@aa5b (Nigel Gamble) "Re: Linux: the next step" (Aug 13, 8:36am) References: <199608131536.IAA29651@aa5b.engr.sgi.com> X-Mailer: Z-Mail (3.2.0 26oct94 MediaMail) To: nigel@aa5b.engr.sgi.com (Nigel Gamble), dm@sgi.com Subject: Re: Linux: the next step Cc: linux@aa5b.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk The new real-time facilities in Irix (Nawaf's scheduler) are superior to what has been available before in any Unix-like system that I know of. There are two areas of shortfall, but these are probably unavoidable given the design and its operating environment: 1. priority-based scheduling is often a poor substitute for deadline scheduling, although it is useful for many rt applications. 2. once a process gets scheduled via the rt facility, if it does any system calls you get Irix system call performance. Sometimes this will be an issue (by limiting the number of syscalls and rt apps), and other times it will not be so important. I believe that efforts to incorporate hard real-time scheduling into a full-function OS will satisfy the large majority of customers who have real-time applications. These customers do not want to run on the bare iron - they want their real-time and they want their OS also. The Linux-based hack that Larry described is indeed elegant - I had a look at the paper. However, if that hack were enough to support a wide range of real-time applications I think system hacks would have implemented it a long time ago. g From owner-linux@cthulhu.engr.sgi.com Wed Aug 14 15:58:52 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA01761; Wed, 14 Aug 1996 15:58:52 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA03869 for linux-list; Wed, 14 Aug 1996 22:58:41 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA03860 for ; Wed, 14 Aug 1996 15:58:39 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA01744; Wed, 14 Aug 1996 15:58:39 -0700 Date: Wed, 14 Aug 1996 15:58:39 -0700 Message-Id: <199608142258.PAA01744@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: bug in IRIX tftpd? Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Wonder if someone can help me fix this problem: Seems that the IRIX tftpd daemon will not respond correctly to requests in binary more. I can reproduce the problem at will and it happens every time. I can do the transfer just fine using ascii mode, but any attempt to use binary mode fails. What is funny is that TFTPD places a syslog entry that says: Aug 14 15:57:13 6D:tanya tftpd[1373]: sandra.engr.sgi.com: read request for /tftpboot/96A64B0F.SUN4C: success Yet tftpd does not send one packet back. It does not matter what machine I try to do this tftp transfer from. ASCII mode always works, binary mode always fails. dm@engr.sgi.com 'Ooohh.. "FreeBSD is faster over loopback, when compared to Linux over the wire". Film at 11.' -Linus From owner-linux@cthulhu.engr.sgi.com Wed Aug 14 16:46:28 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA02556; Wed, 14 Aug 1996 16:46:28 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA14812 for linux-list; Wed, 14 Aug 1996 23:46:18 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA14807 for ; Wed, 14 Aug 1996 16:46:17 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA02549; Wed, 14 Aug 1996 16:46:17 -0700 Date: Wed, 14 Aug 1996 16:46:17 -0700 Message-Id: <199608142346.QAA02549@neteng.engr.sgi.com> From: "David S. Miller" To: linux@neteng.engr.sgi.com Subject: ignore tftp bug report Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Duh, no one was answering tanya's ARP requests for sandra.engr dm@engr.sgi.com 'Ooohh.. "FreeBSD is faster over loopback, when compared to Linux over the wire". Film at 11.' -Linus From owner-linux@cthulhu.engr.sgi.com Sat Aug 24 16:29:57 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (8.7.5/960327.SGI.AUTOCF) via SMTP id QAA26392; Sat, 24 Aug 1996 16:29:57 -0700 (PDT) Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA18942 for linux-list; Sat, 24 Aug 1996 23:29:31 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA18931 for ; Sat, 24 Aug 1996 16:29:30 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA19238; Sat, 24 Aug 1996 16:27:35 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199608242327.QAA19238@yon.engr.sgi.com> Subject: Linux/MIPS: short update To: linux@yon.engr.sgi.com Date: Sat, 24 Aug 1996 16:27:35 -0700 (PDT) Cc: jcl@cthulhu.engr.sgi.com (John Loveall) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk a short update, As some of you know. David is going back to school (Aug 25). We wish the summer vacation was a little longer so he could really complete and stabilize the port but a lot of time was invested in major aggressive operations like replacing the Linux libc with the GNU libc and keep up with the latest GNU development tools. This should be seen as a good investment in a better Linux foundation for the future that will benefit all ports, not just the MIPS one. We are going to try and loan the two Indys to David so he could complete the port while at Rutgers. (The assets called stacey and tanya except for one monitor which was mine belong to John Loveall who generously loaned them to us for the summer.) David plans to: 1) Merge his work with Ralf (Germany MIPS port) so there will be only one Linux/MIPS port. 2) Clean rough edges, Stabilize the port, on both hardware families. 3) Try to roll the work into Linux before Linus releases 2.1 so that everything will be a part of 2.1 and available on the net. If this can happen we've achieved our first major goal: get Linux to run on SGI hardware and be widely available. I hope David can pull it off. Lastly, I'd like to thank David for an impressive well done job and strongly hope to see him at SGI next summer too. and to all of you who helped this happen (you know who you are), thanks as well. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Mon Sep 2 07:07:03 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via SMTP id HAA07981; Mon, 2 Sep 1996 07:07:03 -0700 (PDT) Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id OAA03474 for linux-list; Mon, 2 Sep 1996 14:06:29 GMT Received: from sgi.sgi.com (sgi.engr.sgi.com [192.26.80.37]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id HAA03468 for ; Mon, 2 Sep 1996 07:06:27 -0700 Received: from huahaga.rutgers.edu (huahaga.rutgers.edu [128.6.155.53]) by sgi.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id HAA27143 for ; Mon, 2 Sep 1996 07:06:26 -0700 Received: (from davem@localhost) by huahaga.rutgers.edu (8.7.5/8.7.3) id KAA27735; Mon, 2 Sep 1996 10:06:42 -0400 Date: Mon, 2 Sep 1996 10:06:42 -0400 Message-Id: <199609021406.KAA27735@huahaga.rutgers.edu> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: old IRIX5.3 INDY's Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Will they only boot ECOFF kernels off of local efs disks? All of the IRIX5 kernels on my machines are ECOFF, were ELF kernels not supported before IRIX6? What about when using bootp()? Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Sun Sep 8 15:42:33 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via ESMTP id PAA00150; Sun, 8 Sep 1996 15:42:33 -0700 (PDT) Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) id WAA28236 for linux-list; Sun, 8 Sep 1996 22:42:21 GMT Received: from sgi.sgi.com (sgi.engr.sgi.com [192.26.80.37]) by cthulhu.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via SMTP id PAA28230 for ; Sun, 8 Sep 1996 15:42:20 -0700 (PDT) Received: from caipfs.rutgers.edu (caipfs.rutgers.edu [128.6.19.100]) by sgi.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id PAA21832 for ; Sun, 8 Sep 1996 15:42:18 -0700 Received: from acappella.rutgers.edu (acappella.rutgers.edu [128.6.111.22]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id SAA27816 for ; Sun, 8 Sep 1996 18:38:32 -0400 Received: (davem@localhost) by acappella.rutgers.edu (8.6.12+CAIPFS_MAIL/8.6.9) id SAA00729; Sun, 8 Sep 1996 18:38:31 -0400 Date: Sun, 8 Sep 1996 18:38:31 -0400 Message-Id: <199609082238.SAA00729@acappella.rutgers.edu> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: favor Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk If any of you can get a copy of todays San Jose Mercury News, and FedEx it to me, I'd be extremely grateful. It contains an articile on computing inHelsinki, Finland and an interview with Linus Torvalds plus some other things on Linux in general. Thanks. Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Sun Sep 8 16:56:02 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via ESMTP id QAA01604; Sun, 8 Sep 1996 16:56:02 -0700 (PDT) Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) id XAA03300 for linux-list; Sun, 8 Sep 1996 23:55:52 GMT Received: from sgi.sgi.com (sgi.engr.sgi.com [192.26.80.37]) by cthulhu.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via SMTP id QAA03294 for ; Sun, 8 Sep 1996 16:55:51 -0700 (PDT) Received: from caipfs.rutgers.edu (caipfs.rutgers.edu [128.6.19.100]) by sgi.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id QAA29321 for ; Sun, 8 Sep 1996 16:55:50 -0700 Received: from acappella.rutgers.edu (acappella.rutgers.edu [128.6.111.22]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id TAA02339 for ; Sun, 8 Sep 1996 19:52:03 -0400 Received: (davem@localhost) by acappella.rutgers.edu (8.6.12+CAIPFS_MAIL/8.6.9) id TAA00791; Sun, 8 Sep 1996 19:52:02 -0400 Date: Sun, 8 Sep 1996 19:52:02 -0400 Message-Id: <199609082352.TAA00791@acappella.rutgers.edu> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: my prevsious mail Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk People can ignore my previous plee, someone has graciously acquired the paper for me. Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Mon Sep 9 10:42:25 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via ESMTP id KAA21516; Mon, 9 Sep 1996 10:42:25 -0700 (PDT) Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) id RAA24460 for linux-list; Mon, 9 Sep 1996 17:42:13 GMT Received: from heaven.newport.sgi.com (heaven.newport.sgi.com [169.238.102.134]) by cthulhu.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via SMTP id KAA24449 for ; Mon, 9 Sep 1996 10:42:10 -0700 (PDT) Received: by heaven.newport.sgi.com (940816.SGI.8.6.9/940406.SGI) id KAA29701; Mon, 9 Sep 1996 10:42:05 -0700 From: "Christopher W. Carlson" Message-Id: <9609091042.ZM29699@heaven.newport.sgi.com> Date: Mon, 9 Sep 1996 10:42:05 -0700 In-Reply-To: "David S. Miller" "favor" (Sep 8, 6:38pm) References: <199609082238.SAA00729@acappella.rutgers.edu> X-Mailer: Z-Mail-SGI (3.2S.2 10apr95 MediaMail) To: "David S. Miller" Subject: Re: favor Cc: linux@cthulhu.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Sep 8, 6:38pm, David S. Miller wrote: > Subject: favor > > If any of you can get a copy of todays San Jose Mercury News, and > FedEx it to me, I'd be extremely grateful. > > It contains an articile on computing inHelsinki, Finland and an > interview with Linus Torvalds plus some other things on Linux in > general. > > Thanks. > > Later, > David S. Miller > davem@caip.rutgers.edu >-- End of excerpt from David S. Miller David, Did you know that the article is online? You can get it through the www.sjmercury.com home page. I found it by clicking on "Finland" on the front page. If you want, I'll forward the text to you (presuming you have no or bad WWW access). -- Chris Carlson +------------------------------------------------------+ | Also, carlson@sgi.com | | Work: (714) 756-5976 SGI vmail: x5-8095 | | FAX: (714) 833-9503 | +------------------------------------------------------+ From owner-linux@cthulhu.engr.sgi.com Mon Sep 9 10:49:50 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via ESMTP id KAA21880; Mon, 9 Sep 1996 10:49:50 -0700 (PDT) Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) id RAA26715 for linux-list; Mon, 9 Sep 1996 17:49:44 GMT Received: from sgi.sgi.com (sgi.engr.sgi.com [192.26.80.37]) by cthulhu.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via SMTP id KAA26706 for ; Mon, 9 Sep 1996 10:49:42 -0700 (PDT) Received: from caipfs.rutgers.edu (caipfs.rutgers.edu [128.6.19.100]) by sgi.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA23712 for ; Mon, 9 Sep 1996 10:49:39 -0700 Received: from acappella.rutgers.edu (acappella.rutgers.edu [128.6.111.22]) by caipfs.rutgers.edu (8.6.9+bestmx+oldruq+newsunq+grosshack/8.6.9) with ESMTP id NAA24530; Mon, 9 Sep 1996 13:45:51 -0400 Received: (davem@localhost) by acappella.rutgers.edu (8.6.12+CAIPFS_MAIL/8.6.9) id NAA02053; Mon, 9 Sep 1996 13:45:50 -0400 Date: Mon, 9 Sep 1996 13:45:50 -0400 Message-Id: <199609091745.NAA02053@acappella.rutgers.edu> From: "David S. Miller" To: carlson@heaven.newport.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <9609091042.ZM29699@heaven.newport.sgi.com> (carlson@heaven.newport.sgi.com) Subject: Re: favor Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: "Christopher W. Carlson" Date: Mon, 9 Sep 1996 10:42:05 -0700 Did you know that the article is online? You can get it through the www.sjmercury.com home page. I found it by clicking on "Finland" on the front page. I realize this, my desire was to have the article hard copy. If you want, I'll forward the text to you (presuming you have no or bad WWW access). No need, as I posted later in the evening yesterday, someone has already sent the article, hardcopy, to me. Later, David S. Miller davem@caip.rutgers.edu From owner-linux@cthulhu.engr.sgi.com Thu Oct 3 22:22:58 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via SMTP id WAA19548; Thu, 3 Oct 1996 22:22:58 -0700 (PDT) Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA01402 for linux-list; Fri, 4 Oct 1996 05:22:49 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA01397 for ; Thu, 3 Oct 1996 22:22:48 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA22987 for linux@engr; Thu, 3 Oct 1996 22:20:13 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199610040520.WAA22987@yon.engr.sgi.com> Subject: Short update To: linux@cthulhu.engr.sgi.com Date: Thu, 3 Oct 1996 22:20:12 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hi All, I suspect by now you are all wondering whether our SGI/Linux adventure is dead and forgotten since David went back to school. Well, I have some good news. it seems the long hiatus is over. We shipped two Indys to David at Rutgers, they were DOA and we had some delay in getting them fixed. Today David emailed me that the two machines are in his office and working fine. He's is ready to give the port the final push to make it ready for prime-time. Thanks to Kim Vogt, Demetrio Pinto, Larry and Greg for their help in getting David going again. More good news (and only good news :-) as they develop. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Fri Oct 4 15:30:35 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via SMTP id PAA07633; Fri, 4 Oct 1996 15:30:35 -0700 (PDT) Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA19785 for linux-list; Fri, 4 Oct 1996 22:30:20 GMT Received: from yarmouth.engr.sgi.com (yarmouth.engr.sgi.com [198.29.64.22]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA19776 for ; Fri, 4 Oct 1996 15:30:18 -0700 Received: from yarmouth (localhost [127.0.0.1]) by yarmouth.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id PAA07692 for ; Fri, 4 Oct 1996 15:32:25 -0700 Message-ID: <32559078.41C6@engr.sgi.com> Date: Fri, 04 Oct 1996 15:32:24 -0700 From: Ken Rose X-Mailer: Mozilla 3.0GoldC-SGI (X11; I; IRIX 6.2 IP22) MIME-Version: 1.0 To: linux@cthulhu.engr.sgi.com Subject: Do you want the Linux Bible book? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I won a Linux book ("Linux Bible") at a bookstore, and I don't even have a home PC. So I have a bit of a dilemma, and I see 2 ways out. Solution (1) is to buy a PC ... solution (2) is to give away the book. I've elected solution (2), so I was hoping someone on this list would be able to use the book. If so, I will give the book to the first person to reply by mail asking for it; please do not phone. -- Ken -- Ken Rose Silicon Graphics Computer Systems email: kenr@engr.sgi.com M/S 2U-923 voice: (415) 933-2701 2011 N. Shoreline Boulevard fax: (415) 961-7849 Mountain View, CA 94039 http://reality.sgi.com/employees/kenr From owner-linux@cthulhu.engr.sgi.com Sat Oct 5 02:14:41 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via SMTP id CAA17377; Sat, 5 Oct 1996 02:14:40 -0700 (PDT) Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id JAA00984 for linux-list; Sat, 5 Oct 1996 09:13:06 GMT Received: from sgindia.newdelhi.sgi.com (sgindia.newdelhi.sgi.com [155.11.203.2]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA00976 for ; Sat, 5 Oct 1996 02:12:47 -0700 Received: from bhairavi.newdelhi.sgi.com by sgindia.newdelhi.sgi.com via ESMTP (940816.SGI.8.6.9/930416.SGI) for <@sgindia.newdelhi.sgi.com:linux@cthulhu.engr.sgi.com> id OAA28780; Sat, 5 Oct 1996 14:42:42 +0530 Received: (from raju@localhost) by bhairavi.newdelhi.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) id OAA01863; Sat, 5 Oct 1996 14:39:08 +0530 Date: Sat, 5 Oct 1996 14:39:08 +0530 Message-Id: <199610050909.OAA01863@bhairavi.newdelhi.sgi.com> From: Raj Mathur To: linux@cthulhu.engr.sgi.com Subject: Short update In-Reply-To: <199610040520.WAA22987@yon.engr.sgi.com> References: <199610040520.WAA22987@yon.engr.sgi.com> Reply-To: raju@bhairavi.newdelhi.sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk That Dave Miller is back at massaging Linux to work on the Indy is great news from Ariel -- Thanks, Ariel. One of the departments in one of India's premier Technical Institutes, the Indian Institute of Technology (IIT), New Delhi has decided to purchase hardware if and only if the vendor can demonstrate Linux running on it. I hope to meet the professor concerned (*) with this decision in the coming week (or the week after). Any ammo you can arm me with to face him and make him consider SGI would be very welcome. Thanks and regards, -- Raju -- Raj Mathur / Web Technical Support / Silicon Graphics / New Delhi raju@bhairavi.newdelhi.sgi.com / +91-11-6211354 / 5-5574 PGP: F2 D4 4A 21 27 B0 63 FF 15 97 9D AE 9D 40 BC B8 It is the mind that moves. (*) And good to see that there are a few right-minded people everywhere :-) From owner-linux@cthulhu.engr.sgi.com Mon Oct 21 14:35:40 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (8.7.6/960327.SGI.AUTOCF) via SMTP id OAA01571; Mon, 21 Oct 1996 14:35:40 -0700 (PDT) Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id VAA19898 for linux-list; Mon, 21 Oct 1996 21:35:27 GMT Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA19857 for ; Mon, 21 Oct 1996 14:35:21 -0700 Received: from windy.wellington.sgi.com by soyuz.wellington.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/940406.SGI) for id KAA01917; Tue, 22 Oct 1996 10:35:10 +1300 Received: (alambie@localhost) by windy.wellington.sgi.com (950413.SGI.8.6.12/8.6.9) id KAA03178 for linux@engr; Tue, 22 Oct 1996 10:35:10 +1300 From: "Alistair Lambie" Message-Id: <9610221035.ZM3176@windy.wellington.sgi.com> Date: Tue, 22 Oct 1996 10:35:10 +0000 X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: linux@cthulhu.engr.sgi.com Subject: New porting platform??? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hey, Ariel's won himself the right ot purchase a Nintendo 64!!! If I remember correctly he once said that if he won an Indy he would donate it to the cause. Does this win mean that we will be moving the porting effort to Nintendo 64? :-) Cheers, Alistair (Well, the list does need just a little bit of traffic every now and then!! ) -- Alistair Lambie alambie@wellington.sgi.com Silicon Graphics New Zealand SGI Voicemail: 56791 Level 5, Walsh Wrightson Tower, Ph: +64-4-802 1455 94-96 Dixon St, Wellington, NZ Fax: +64-4-802 1459 From owner-linux@cthulhu.engr.sgi.com Fri Nov 8 10:05:30 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (8.8.2/960327.SGI.AUTOCF) via SMTP id KAA14525; Fri, 8 Nov 1996 10:05:30 -0800 (PST) Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA09140 for linux-list; Fri, 8 Nov 1996 18:04:54 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA09132 for ; Fri, 8 Nov 1996 10:04:52 -0800 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA16246 for linux; Fri, 8 Nov 1996 10:03:37 -0800 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199611081803.KAA16246@yon.engr.sgi.com> Subject: Linus move to the U.S. To: linux@yon.engr.sgi.com Date: Fri, 8 Nov 1996 10:03:37 -0800 (PST) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk My reference.com news filter just caught this. While some of you may have known about this for quite a while here's a confirmation from the horse's mouth. ----- Forwarded message from User-Services@Reference.COM ----- Hit-Number: 1 Article-ID: 11_1996&992840 Score: 98 Subject: Re: Linux and Transmeta From: torvalds@linux.cs.Helsinki.FI (Linus Torvalds) Date: Thu, 7 Nov 1996 05:32:50 -0800 Message-ID: <55soe2$1i0@linux.cs.Helsinki.FI> Newsgroups: comp.os.linux.advocacy In article , Bob Nelson wrote: >Comments from anyone about Linus' move to the United States and his >employment by Transmeta (to start in 1Q 1997)? [Refer to SSC's web >site for a brief story on this]. What implications do you think it >may have for the OS? I'll comment on this myself, I think. Right now it looks like we'll be moving some time in February next year. That will probably involve me being partially off the net for a few weeks, which in itself isn't really anything unheard of (that tends to happen a few times a year just when I'm taking a vacation or just going abroad for a longer conference). That will be one of the things people will notice immediately. And even after I get connected there will probably be a delay until I get "up to speed" again. The other thing that I'll probably do at the same time is just to start filtering my email: I've been thinking of that for a long time (independently of any move), and the fact that my email setup changes anyway just gives me a possibility of changing it all at one time. But aside from those kinds of details, there probably won't be all that large changes in how the OS is developed: there will be a new site for new kernel images (but the old ones here in Finland will probably also continue to work). In short, I'll be able to continue doing Linux even at Transmeta. Linus ----- End of forwarded message from User-Services@Reference.COM ----- -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Nov 26 21:45:41 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (8.8.3/960327.SGI.AUTOCF) via SMTP id VAA14169; Tue, 26 Nov 1996 21:45:41 -0800 (PST) Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA04811 for linux-list; Wed, 27 Nov 1996 05:45:22 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id VAA04805 for ; Tue, 26 Nov 1996 21:45:21 -0800 Received: from linux.engr.sgi.com (linux.engr.sgi.com [150.166.75.42]) by neteng.engr.sgi.com (8.8.3/960327.SGI.AUTOCF) via ESMTP id VAA14165 for ; Tue, 26 Nov 1996 21:45:20 -0800 (PST) Received: (from lm@localhost) by linux.engr.sgi.com (8.7.6/8.7.3) id VAA00321 for linux@neteng; Thu, 28 Nov 1996 21:45:35 -0800 Date: Thu, 28 Nov 1996 21:45:35 -0800 From: Larry McVoy Message-Id: <199611290545.VAA00321@linux.engr.sgi.com> To: linux@neteng.engr.sgi.com Subject: linux up and running in engr domain again. Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I have a PC running linux for your use, if you need it. It's linux.engr, you can log in as guest, there is no password but you have to type at the password prompt. --lm .