From owner-freebsd-hackers Sun Mar 18 4:39:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 203B037B718 for ; Sun, 18 Mar 2001 04:39:26 -0800 (PST) (envelope-from roam@orbitel.bg) Received: (qmail 69058 invoked by uid 1000); 18 Mar 2001 12:38:22 -0000 Date: Sun, 18 Mar 2001 14:38:22 +0200 From: Peter Pentchev To: Dag-Erling Smorgrav Cc: Tony Finch , Duncan Barclay , Kris Kennaway , hackers@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: httpfs Message-ID: <20010318143822.F49603@ringworld.oblivion.bg> Mail-Followup-To: Dag-Erling Smorgrav , Tony Finch , Duncan Barclay , Kris Kennaway , hackers@FreeBSD.ORG, fs@FreeBSD.ORG References: <20010310031515.A8998@mollari.cthul.hu> <20010315095533.C12432@ringworld.oblivion.bg> <000d01c0ad3c$0ed83fb0$d26020c2@Cadence.COM> <000d01c0ad3c$0ed83fb0$d26020c2@Cadence.COM> <20010315124244.A442@ringworld.oblivion.bg> <20010316054649.F385@hand.dotat.at> <20010316174424.A428@ringworld.oblivion.bg> <20010317180055.A486@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from des@ofug.org on Sat, Mar 17, 2001 at 05:03:42PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 17, 2001 at 05:03:42PM +0100, Dag-Erling Smorgrav wrote: > Peter Pentchev writes: > > On Sat, Mar 17, 2001 at 04:53:34PM +0100, Dag-Erling Smorgrav wrote: > > > Peter Pentchev writes: > > > > There was at the time - socketpair(2) had totally slipped my mind ;) > > > Umm, you want pipe(2), not socketpair(2). > > Actually, I want socketpair(2). pipe(2) was what I used before, > > and that's the reason I had a read-only file descriptor - the portalfs > > architecture allows for only one fd to be returned, and pipe(2) > > provides a one-way pipe. > > Not in FreeBSD. Oops. OK. I RTFM'd, and fixed it. Thanks to everyone who pointed that out :) G'luck, Peter -- This sentence no verb. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 18 11:38:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ghs.ssd.k12.wa.us (locutus.ghs.ssd.k12.wa.us [216.186.55.25]) by hub.freebsd.org (Postfix) with ESMTP id 0ED1337B71A for ; Sun, 18 Mar 2001 11:38:36 -0800 (PST) (envelope-from protozoa@ghs.ssd.k12.wa.us) Received: from localhost (protozoa@localhost) by ghs.ssd.k12.wa.us (8.9.3/8.9.3) with ESMTP id LAA71659; Sun, 18 Mar 2001 11:38:20 -0800 (PST) (envelope-from protozoa@ghs.ssd.k12.wa.us) Date: Sun, 18 Mar 2001 11:38:20 -0800 (PST) From: Dan Feldman To: Paul Saab Cc: Thierry Herbelot , Rohit Rakshe , freebsd-hackers@FreeBSD.ORG Subject: Re: Remote boot, but not diskless operation In-Reply-To: <20010316141918.A46855@elvis.mu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For more docs, check out http://matt.simerson.net/computing/freebsd.netboot.shtml . It clarifies a great deal. - dan feldman student, garfield high school, seattle On Fri, 16 Mar 2001, Paul Saab wrote: > Thierry Herbelot (thierry@herbelot.com) wrote: > > Hi, > > > > One way to boot the kernel over the network is to use PXE (if your > > machine is recent enough to support it *well* : that is with a recent > > version of the PXE firmware) > > > > there is no real document on PXE booting > > you can read a note by Alfred Perlstein on > > , the manpage for pxeboot, > > the code in rc.diskless{1,2}, the configuration of the boot server with > > dhcp and tftp/nfs (you may have to tweak /etc/fstab in order to mount a > > root partition which was not used to load /kernel ?) > > > > there is also somme documentation on Intel's web site > > > > I'm trying to use PXE, but it's not completly reliable (sometimes > > pxeboot just crashes) > > Upgrade the PXE rom > http://people.freebsd.org/~ps/pxeroms/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 18 12:51:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id B3BD737B71F; Sun, 18 Mar 2001 12:51:43 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2IKp4g01900; Sun, 18 Mar 2001 12:51:04 -0800 (PST) (envelope-from dillon) Date: Sun, 18 Mar 2001 12:51:04 -0800 (PST) From: Matt Dillon Message-Id: <200103182051.f2IKp4g01900@earth.backplane.com> To: "Duncan Barclay" Cc: "Peter Pentchev" , "Kris Kennaway" , , Subject: Re: httpfs References: <20010310031515.A8998@mollari.cthul.hu> <20010315095533.C12432@ringworld.oblivion.bg> <000d01c0ad3c$0ed83fb0$d26020c2@Cadence.COM> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I don't really think that portalfs is the right thing to use to build :an httpfs with, but I would like to see how you managed to get your example :to work. Are you using stdout to create an anonymous file handle? What happens :if two processes concurrently read from /p/http/*? : :Duncan : :-- :_____________________________________________________________ :Duncan Barclay | God smiles upon the little children, You could certainly write a program to sit in the middle and cache the request to handle that case. The problem with portalfs is that you can't 'cd' into it or do directory operations on it, and filesystem operations such as lseek, fstat, and so forth cannot be intercepted. It would be the ultimate coolness if you could. We need a better solution then faking an NFS mount to be able to run *real* filesystems in user space. But, that aside, portalfs works just dandy for getting simple file handles from a path. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 18 13: 5: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id 5E9D637B71F for ; Sun, 18 Mar 2001 13:04:47 -0800 (PST) (envelope-from danfe@inet.ssc.nsu.ru) Received: (qmail 25894 invoked from network); 18 Mar 2001 21:04:43 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 18 Mar 2001 21:04:43 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id CAA07380 for ; Mon, 19 Mar 2001 02:16:23 +0600 Date: Mon, 19 Mar 2001 02:16:23 +0600 (NOVT) From: Alexey Dokuchaev To: freebsd-hackers@freebsd.org Subject: Some PCI-related programming things Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello there, Under linux, PCI stuff is generally done thru set of pci* functions, while under FreeBSD there are ioctls provided by pci driver. I've been doing some code migration from linux to FreeBSD, and got thru most of it, except for things like this one: . . . pcibios_read_config_dword(bus_id, func_id, PCI_BASE_ADDRESS_0, &addr_0); addr_0 &= PCI_BASE_ADDRESS_IO_MASK; pcibios_read_config_dword(bus_id, func_id, PCI_BASE_ADDRESS_1, &addr_1); addr_1 &= PCI_BASE_ADDRESS_MEM_MASK; . . . I am not quite sure how to code the same thing under FreeBSD, particulary: pi.pi_width = 4; pi.pi_reg = ioctl(fd, PCIOCREAD, &pi); Could anyone give me an example for both addr_0 and addr_1 (that is, translation of the linux code I cited above?) I will really appreciate any help with regard to this. Thanks in advance. -- Alexey. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 18 13:18:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 8280137B71F for ; Sun, 18 Mar 2001 13:18:40 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2ILJBL01279; Sun, 18 Mar 2001 13:19:12 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103182119.f2ILJBL01279@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexey Dokuchaev Cc: freebsd-hackers@freebsd.org Subject: Re: Some PCI-related programming things In-reply-to: Your message of "Mon, 19 Mar 2001 02:16:23 +0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 18 Mar 2001 13:19:11 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello there, > > Under linux, PCI stuff is generally done thru set of pci* functions, while > under FreeBSD there are ioctls provided by pci driver. I've been doing > some code migration from linux to FreeBSD, and got thru most of it, except > for things like this one: You are probably doing something very wrong here, but rather than try to convince you to do it, right, I'll just answer your question. 8) > > . . . > pcibios_read_config_dword(bus_id, func_id, PCI_BASE_ADDRESS_0, &addr_0); > addr_0 &= PCI_BASE_ADDRESS_IO_MASK; > pcibios_read_config_dword(bus_id, func_id, PCI_BASE_ADDRESS_1, &addr_1); > addr_1 &= PCI_BASE_ADDRESS_MEM_MASK; > . . . > > > I am not quite sure how to code the same thing under FreeBSD, particulary: > > pi.pi_width = 4; > pi.pi_reg = > ioctl(fd, PCIOCREAD, &pi); You put PCI_BASE_ADDRESS_0, or PCIR_MAPS if you're using our headers. PCI_BASE_ADDRESS_1 is typically PCIR_MAPS + 4 > Could anyone give me an example for both addr_0 and addr_1 (that is, > translation of the linux code I cited above?) Er, you don't. You'll get the value you've read in pi.pi_data. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 18 14:10:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 6258337B718; Sun, 18 Mar 2001 14:10:27 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f2ILRVh47947; Sun, 18 Mar 2001 16:27:31 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 18 Mar 2001 16:27:30 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Matt Dillon Cc: Duncan Barclay , Peter Pentchev , Kris Kennaway , hackers@FreeBSD.ORG, fs@FreeBSD.ORG Subject: Re: httpfs In-Reply-To: <200103182051.f2IKp4g01900@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Mar 2001, Matt Dillon wrote: > You could certainly write a program to sit in the middle and cache > the request to handle that case. > > The problem with portalfs is that you can't 'cd' into it or do > directory operations on it, and filesystem operations such as lseek, > fstat, and so forth cannot be intercepted. It would be the ultimate > coolness if you could. > > We need a better solution then faking an NFS mount to be able to run > *real* filesystems in user space. > > But, that aside, portalfs works just dandy for getting simple file handles > from a path. Take a look at the XFS module included with Arla, and the Coda kernel module. They're both targetted at the idea that a userspace daemon will deal with open/close/directory requests, providing container vnodes for the actual files on demand, allowing the kernel to efficiently provide them to consumers. It's easy to imagine an HTTP backend daemon for them. The Arla kernel module is probably a bit more mature and better maintained; on the other hand, the Coda module is in our sys/ tree already. The OpenBSD folk have actually imported Arla into their distribution, which is actually not a bad idea now that OpenAFS is around... (Of course, we still need someone to port OpenAFS so that we have a free server -- with IFS on the server side, we should be able to exhibit a substantially simpler implementation with the same perform benefits as the AFS iopen() stuff :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 18 14:10:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id AB1CC37B719 for ; Sun, 18 Mar 2001 14:10:31 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [127.0.0.1] (helo=softweyr.com ident=7d1de65d6429943d04538a58e39e3fc2) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14elNR-0000DW-00; Sun, 18 Mar 2001 15:10:18 -0700 Message-ID: <3AB53249.E8C3F2E3@softweyr.com> Date: Sun, 18 Mar 2001 15:10:17 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Farooq Mela , FreeBSD-Hackers@FreeBSD.ORG Subject: Re: GCC Upgrade? References: <3AB310DF.A43A8BC@sm.socccd.cc.ca.us> <20010317104642.Y29888@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > You're too optimistic. _Every_ gcc release is supposed to "fix > some bugs in the optimizer". And _every_ gcc release introduces a few others. That's the nature of a complicated software system. > David will sync our compiler with > the latest version when he feels that it's ready for FreeBSD. And when FreeBSD is ready to have the compiler stood on it's ear for a few days. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 18 14:58:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id 4112A37B718; Sun, 18 Mar 2001 14:58:02 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id f2ILk3R38652; Sun, 18 Mar 2001 22:46:03 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.2/8.11.0) id f2ILjrS04690; Sun, 18 Mar 2001 22:45:53 +0100 (CET) (envelope-from asmodai) From: Jeroen Ruigrok van der Werven Date: Sun, 18 Mar 2001 22:45:53 +0100 To: petro Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Can't install FreeBSD 4.1 Message-ID: <20010318224553.A4420@daemon.ninth-circle.org> Reply-To: freebsd-questions@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Fdrom: Jeroen Ruigrok/Asmodai In-Reply-To: ; from petro@She.wertep.com on Sat, Mar 17, 2001 at 06:21:00PM +0200 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [follow-up set to freebsd-questions, net/hackers bcc:'d] [please don't only reply to me alone] -On [20010317 17:30], petro (petro@She.wertep.com) wrote: >I try to install FreeBSD 4.1 >when the proces of copying begin, (near 20% of /bin copied) >I receive such error > >panic: general protection fault >syncing disks ...... 99.. 99 99 99 >automatic reboot in 15 seconds, press any key to abort. Have you tried 4.2-RELEASE yet? It might be that this particular fault has already been correct since. Have you checked the errata? Have you monitored the interactive debug screen on vty2? -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 The administration of justice is the firmest pillar of government... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Mar 18 23:54: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sonic.kks.net (sonic.kks.net [213.161.0.18]) by hub.freebsd.org (Postfix) with ESMTP id 52AAF37B718 for ; Sun, 18 Mar 2001 23:54:02 -0800 (PST) (envelope-from matjazp@doyen.si) Received: from ninja (7-194.ro.cable.kks.net [213.161.7.194]) by sonic.kks.net (Postfix) with SMTP id F2ADF175 for ; Mon, 19 Mar 2001 08:58:17 +0100 (CET) Message-ID: <004001c0b048$fdd20fb0$c207a1d5@cable.kks.net> From: "matjaz" To: Subject: 3com-isdn problem Date: Mon, 19 Mar 2001 08:48:30 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003D_01C0B051.5F85AED0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_003D_01C0B051.5F85AED0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable I have made a user ppp gateway on an ISDN line.When i connect a ASUSCOM = device, averything works just fine. I tried it with a 3COM-USR device and I get no connection through to my = ISP.When i work my way through log files, it shows as if the modem is somehow trying CHAP authentication (ISP has = PAP). Is there somebody with expirience with 3Com ISDN devices.I know there is = nothing wrong with ppp configuration,because with other devices it works perfect.Perhaps i could configure the device to = negotiate PAP,i just dont know how matjaz pahor ------=_NextPart_000_003D_01C0B051.5F85AED0 Content-Type: text/html; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable
I have made a user ppp gateway on an = ISDN line.When=20 i connect a ASUSCOM device, averything works just fine.
I tried it with a 3COM-USR device and I = get no=20 connection through to my ISP.When i work my way through log = files,
it shows as if the modem is somehow = trying CHAP=20 authentication (ISP has PAP).
Is there somebody with expirience with = 3Com ISDN=20 devices.I know there is nothing wrong with ppp configuration,because=20 with
other devices it works perfect.Perhaps = i could=20 configure the device to negotiate PAP,i just dont know how
 
 
matjaz pahor
------=_NextPart_000_003D_01C0B051.5F85AED0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 0:39:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ajax1.sovam.com (ajax1.sovam.com [194.67.1.172]) by hub.freebsd.org (Postfix) with ESMTP id CF05837B718 for ; Mon, 19 Mar 2001 00:39:20 -0800 (PST) (envelope-from avn@any.ru) Received: from ts11-a1.dial.sovam.com ([195.239.68.1]:1040 "EHLO ts11-a1.dial.sovam.com" ident: "avn" whoson: "-unregistered-" smtp-auth: TLS-CIPHER: TLS-PEER: ) by ajax1.sovam.com with ESMTP id ; Mon, 19 Mar 2001 11:38:47 +0300 Date: Mon, 19 Mar 2001 11:42:25 +0300 (MSK) From: avn X-X-Sender: To: Alexander Langer Cc: Subject: Re: device driver dev. book In-Reply-To: <20010317153934.A2243@cichlids.cichlids.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Sat, 17 Mar 2001, Alexander Langer wrote: >A "Developers Handbook", which will also cover device driver and >kernel module programming is in work under the leadership of Jeroen >Ruigrok van der Werven . Once it has more >content I can imagine a print version of this. Is there URL for work in progress? :) # Alexey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 2:24:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id 6257B37B718 for ; Mon, 19 Mar 2001 02:24:29 -0800 (PST) (envelope-from danfe@inet.ssc.nsu.ru) Received: (qmail 7970 invoked from network); 19 Mar 2001 10:23:58 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 19 Mar 2001 10:23:58 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id QAA14476; Mon, 19 Mar 2001 16:23:36 +0600 Date: Mon, 19 Mar 2001 16:23:35 +0600 (NOVT) From: Alexey Dokuchaev To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: Some PCI-related programming things In-Reply-To: <200103182119.f2ILJBL01279@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Mar 2001, Mike Smith wrote: > > Hello there, > > > > Under linux, PCI stuff is generally done thru set of pci* functions, while > > under FreeBSD there are ioctls provided by pci driver. I've been doing > > some code migration from linux to FreeBSD, and got thru most of it, except > > for things like this one: > > You are probably doing something very wrong here, but rather than try to > convince you to do it, right, I'll just answer your question. 8) > Hey, that's not fair :-) I'd like to know how to do things the rigth way. 10x -- Alexey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 6: 4:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by hub.freebsd.org (Postfix) with ESMTP id CBB4E37B719 for ; Mon, 19 Mar 2001 06:04:54 -0800 (PST) (envelope-from titus@pleach.de) Received: from fwd03.sul.t-online.com by mailout05.sul.t-online.com with smtp id 14f0HB-0002wv-01; Mon, 19 Mar 2001 15:04:49 +0100 Received: from mail.net (340050866639-0001@[217.80.10.3]) by fmrl03.sul.t-online.com with esmtp id 14f0Gk-0o4YADC; Mon, 19 Mar 2001 15:04:22 +0100 Received: from schweinkram.pleach-hamburg.de (localhost [127.0.0.1]) by mail.net (8.11.1/8.9.2) with ESMTP id f2JE1px48130 for ; Mon, 19 Mar 2001 15:01:51 +0100 (CET) (envelope-from titus@pleach-hamburg.de) Received: from pleach-hamburg.de (titus.pleach-hamburg.de [192.168.1.16]) by schweinkram.pleach-hamburg.de (8.11.1/8.11.1) with ESMTP id f2JDpnv48033 for ; Mon, 19 Mar 2001 14:51:49 +0100 (CET) (envelope-from titus@pleach-hamburg.de) Message-ID: <3AB60FAC.DB181706@pleach-hamburg.de> Date: Mon, 19 Mar 2001 14:54:52 +0100 From: Titus von Boxberg X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: GCC Upgrade? References: <3AB310DF.A43A8BC@sm.socccd.cc.ca.us> <20010317104642.Y29888@fw.wintelcom.net> <20010317203506.A57756@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: 340050866639-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > Monday. GCC 2.95.3 will hi 4-STABLE after April 1st. Heck, April 1st > might actually be the best day to do it. So if RELENG_4 is unfrozen by > then, that's when I'll MFC it. ;) Hi, I just posted the question in another thread: Since at least aug. 2000 (according to the mailing list archives) the exception handling in base system g++ is broken (at least for multithreaded programs) My questions were: What causes the bug in exception handling? Why does the packaged g++ work? And: will the next release of freebsd be ok? regards titus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 6: 6:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cubitus.net2one.com (chewbacca.net2one.com [193.178.140.3]) by hub.freebsd.org (Postfix) with ESMTP id 1D5E137B718 for ; Mon, 19 Mar 2001 06:06:54 -0800 (PST) (envelope-from NDeslions@net2one.com) Received: from meteor.net2one.loc by cubitus.net2one.com with ESMTP for ; œMon, 19 Mar 2001 15:06:58 +0100 Received: by METEOR with Internet Mail Service (5.5.2653.19) id ; Mon, 19 Mar 2001 15:06:50 +0100 Message-ID: From: Deslions Nicolas To: "'freebsd-hackers@FreeBSD.ORG'" Subject: mfs limits Date: Mon, 19 Mar 2001 15:06:49 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, i'm trying to setup a 850Mb ramdrive but MFS seems limited ... i didn't found any way to do something bigger than 500Mb Any idea ? Thanks. Nicolas Deslions System, network and security admin Net2one.com, France 20 rue du Sentier 75002 Paris Mail: ndeslions@net2one.com http://www.net2one.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 6:11:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from melusine.cuivre.fr.eu.org (ppp14-net1-idf3-bas1.isdnet.net [195.154.52.14]) by hub.freebsd.org (Postfix) with ESMTP id 2E87737B71A for ; Mon, 19 Mar 2001 06:11:45 -0800 (PST) (envelope-from thomas@cuivre.fr.eu.org) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id B578124D02; Mon, 19 Mar 2001 15:11:34 +0100 (CET) Date: Mon, 19 Mar 2001 15:11:34 +0100 From: Thomas Quinot To: freebsd-hackers@freebsd.org Subject: SCSI-over-* hacks Message-ID: <20010319151134.A89803@melusine.cuivre.fr.eu.org> Reply-To: thomas@cuivre.fr.eu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi hackers, Has anyone implemented/thought of implementing: - a CAM transport for ATAPI devices; - a CAM transport for USB scanners; - the Linux SCSI generic device (/dev/sg*)? I would be interested in any experience in these fields... And I'd rather not start implementing from scratch if someone has already given it a try. Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 6:25:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from list.framfab.se (list.framfab.se [195.54.96.202]) by hub.freebsd.org (Postfix) with ESMTP id ABD7F37B718 for ; Mon, 19 Mar 2001 06:25:54 -0800 (PST) (envelope-from Marten.Wikstrom@framfab.se) Received: from stoent001.framfab.se (mail.sto.framfab.se [172.16.200.241]) by list.framfab.se (8.9.3/8.9.3) with ESMTP id QAA02638 for ; Mon, 19 Mar 2001 16:19:18 +0100 Received: by STOENT001 with Internet Mail Service (5.5.2653.19) id ; Mon, 19 Mar 2001 15:23:00 +0100 Message-ID: From: =?iso-8859-1?Q?M=E5rten_Wikstr=F6m?= To: "'freebsd-hackers@freebsd.org'" Subject: Routing latency Date: Mon, 19 Mar 2001 15:22:56 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've performed a routing test between a FreeBSD box and a Linux box. I measured the latency and the result was not what I had expected. Both systems had the peak at 100 us (microseconds), but whereas the Linux = box had _no_ packet over 200 us, the FreeBSD box delayed some packets up to 2 = ms! Looking at the time series, it seems that the packets are delayed at = regular intervals, about every second. My guess is that some timer interrupt triggers every second and steals too much cpu. So my question is, how = can I decrease this routing delay? Test info: I used two identical boxes, each equipped with a Pentium Pro 200Mhz and = 64Mb mem. RedHat 7.0 with 2.4 kernel in one and FreeBSD 4.2-RELEASE in the = other. I used two DEC 100Mbit ethernet cards (21140 I think). I measured the latency with a SmartBits instrument. Fastforwarding was disabled. Three UDP streams was sent from the SmartBits to one of the ethernet cards in the box, which routed the streams to the other = interface, which in turn was connected back to the SmartBits. I had not made any changes to the standard kernel configuration. No = other processes was running in the background, apart from those necessary to perform the test. The ARP table was set statically, so no ARP traffic = would disturb. I would at least want to know what is causing the extra delays. /M=E5rten To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 7:47:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tintagel.pdl.cs.cmu.edu (TINTAGEL.PDL.CS.CMU.EDU [128.2.189.2]) by hub.freebsd.org (Postfix) with ESMTP id 99EA437B719 for ; Mon, 19 Mar 2001 07:47:44 -0800 (PST) (envelope-from magus@tintagel.pdl.cs.cmu.edu) Received: (from magus@localhost) by tintagel.pdl.cs.cmu.edu (8.11.2/8.11.1) id f2JFlPw53275; Mon, 19 Mar 2001 10:47:25 -0500 (EST) (envelope-from magus) To: thomas@cuivre.fr.eu.org Cc: freebsd-hackers@freebsd.org Subject: Re: SCSI-over-* hacks References: <20010319151134.A89803@melusine.cuivre.fr.eu.org> From: Nat Lanza Date: 19 Mar 2001 10:47:25 -0500 In-Reply-To: <20010319151134.A89803@melusine.cuivre.fr.eu.org> Message-ID: Lines: 24 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Quinot writes: > Has anyone implemented/thought of implementing: > - a CAM transport for ATAPI devices; > - a CAM transport for USB scanners; > - the Linux SCSI generic device (/dev/sg*)? FreeBSD already has an equivalent to the SCSI generic device -- take a look at pass(4). The only major feature of sg that's currently missing in pass is asynchronous commands. I have a set of patches that adds that support in, but I've been too busy recently with changing jobs to clean them up and submit them. As far as ATAPI-over-CAM, there's been some discussion of having ATA become part of CAM, but I don't remember what the result of it was. You might want to check the list archives. --nat -- nat lanza -------------------------------------- there are no whole truths; magus@cs.cmu.edu ------------------------------- all truths are half-truths http://www.cs.cmu.edu/~magus/ ------------------ -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 7:56:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from melusine.cuivre.fr.eu.org (ppp14-net1-idf3-bas1.isdnet.net [195.154.52.14]) by hub.freebsd.org (Postfix) with ESMTP id 0503D37B71A for ; Mon, 19 Mar 2001 07:56:06 -0800 (PST) (envelope-from thomas@cuivre.fr.eu.org) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id E463F24D02; Mon, 19 Mar 2001 16:56:03 +0100 (CET) Date: Mon, 19 Mar 2001 16:56:03 +0100 From: Thomas Quinot To: Nat Lanza Cc: thomas@cuivre.fr.eu.org, freebsd-hackers@freebsd.org Subject: Re: SCSI-over-* hacks Message-ID: <20010319165603.A95194@melusine.cuivre.fr.eu.org> Reply-To: thomas@cuivre.fr.eu.org References: <20010319151134.A89803@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: ; from magus@cs.cmu.edu on Mon, Mar 19, 2001 at 10:47:25AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Le 2001-03-19, Nat Lanza écrivait : > FreeBSD already has an equivalent to the SCSI generic device -- take a > look at pass(4). Yep, I am aware of pass(4), but some closed-source software that comes only as Linux binaries insist on having a /dev/sg device (which, under FreeBSD, would most likely be implemented as a wrapper around pass.) > As far as ATAPI-over-CAM, there's been some discussion of having ATA > become part of CAM, but I don't remember what the result of it > was. You might want to check the list archives. Thanks, I'll do that. Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 8:39:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from unity.agava.ru (unity.agava.ru [213.59.3.227]) by hub.freebsd.org (Postfix) with ESMTP id AD3A537B719 for ; Mon, 19 Mar 2001 08:39:47 -0800 (PST) (envelope-from frank@agava.com) Received: from relay2.agava.net.ru (unknown [193.125.142.2]) by unity.agava.ru (Postfix) with ESMTP id 2530F27E9A5; Mon, 19 Mar 2001 19:39:45 +0300 (MSK) Received: from gw.office.agava.ru (2.oivt.mipt.ru [193.125.142.2]) by relay2.agava.net.ru (Postfix) with ESMTP id B93FF43734; Mon, 19 Mar 2001 19:38:29 +0300 (MSK) Received: from hellbell.domain (hellbell.domain [192.168.1.12]) by gw.office.agava.ru (Postfix) with ESMTP id 4C75F5EA4; Mon, 19 Mar 2001 19:38:24 +0300 (MSK) Received: from localhost (localhost [127.0.0.1]) by hellbell.domain (Postfix) with ESMTP id 04BB8CD1A; Mon, 19 Mar 2001 19:38:24 +0300 (MSK) Date: Mon, 19 Mar 2001 19:38:24 +0300 (MSK) From: Alexey Zakirov X-X-Sender: To: Deslions Nicolas Cc: "'freebsd-hackers@FreeBSD.ORG'" Subject: Re: mfs limits In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Mar 2001, Deslions Nicolas wrote: > Hi, > > i'm trying to setup a 850Mb ramdrive but MFS seems limited ... i didn't > found any way to do something bigger than 500Mb > > Any idea ? You should increase "options MAXDSIZ=" in your kernel config file. See LINT for further description. *** WBR, Alexey Zakirov (frank@agava.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 10:51: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 5EA2837B71A for ; Mon, 19 Mar 2001 10:50:58 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2JIoqR65550; Mon, 19 Mar 2001 10:50:52 -0800 (PST) (envelope-from obrien) Date: Mon, 19 Mar 2001 10:50:46 -0800 From: "David O'Brien" To: Titus von Boxberg Cc: hackers@FreeBSD.ORG Subject: Re: GCC Upgrade? Message-ID: <20010319105046.A64519@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <3AB310DF.A43A8BC@sm.socccd.cc.ca.us> <20010317104642.Y29888@fw.wintelcom.net> <20010317203506.A57756@dragon.nuxi.com> <3AB60FAC.DB181706@pleach-hamburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AB60FAC.DB181706@pleach-hamburg.de>; from titus@pleach.de on Mon, Mar 19, 2001 at 02:54:52PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 19, 2001 at 02:54:52PM +0100, Titus von Boxberg wrote: > Since at least aug. 2000 (according to the mailing list > archives) the exception handling in base system g++ is broken > (at least for multithreaded programs) I am not aware of exception handling being broken (more so than in 4.x). Can you point me to a PR, or send me a _small_ sample program? -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 11:33: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (s014.dhcp212-24.cybercable.fr [212.198.24.14]) by hub.freebsd.org (Postfix) with ESMTP id DC45037B719 for ; Mon, 19 Mar 2001 11:32:59 -0800 (PST) (envelope-from thierry@herbelot.com) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id UAA61747; Mon, 19 Mar 2001 20:32:26 +0100 (CET) (envelope-from thierry@herbelot.com) Message-ID: <3AB65EC9.4D969490@herbelot.com> Date: Mon, 19 Mar 2001 20:32:25 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?M=E5rten=20Wikstr=F6m?= Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: Routing latency References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, the FreeBSD TCP/IP stack uses the "system tick timer" for some delay (maybe only for TCP). you may want to use a HZ=1000 option (see the LINT config file) in a recompiled kernel and see if things go better. (moreover, the dc(4) driver which is used for your NIC has some interesting performance improvements in the forthcoming 4.3-Release) TfH Mårten Wikström wrote: > > I've performed a routing test between a FreeBSD box and a Linux box. I > measured the latency and the result was not what I had expected. Both > systems had the peak at 100 us (microseconds), but whereas the Linux box had > _no_ packet over 200 us, the FreeBSD box delayed some packets up to 2 ms! > Looking at the time series, it seems that the packets are delayed at regular > intervals, about every second. My guess is that some timer interrupt > triggers every second and steals too much cpu. So my question is, how can I > decrease this routing delay? > > Test info: > I used two identical boxes, each equipped with a Pentium Pro 200Mhz and 64Mb > mem. RedHat 7.0 with 2.4 kernel in one and FreeBSD 4.2-RELEASE in the other. > I used two DEC 100Mbit ethernet cards (21140 I think). > I measured the latency with a SmartBits instrument. Fastforwarding was > disabled. Three UDP streams was sent from the SmartBits to one of the > ethernet cards in the box, which routed the streams to the other interface, > which in turn was connected back to the SmartBits. > I had not made any changes to the standard kernel configuration. No other > processes was running in the background, apart from those necessary to > perform the test. The ARP table was set statically, so no ARP traffic would > disturb. > > I would at least want to know what is causing the extra delays. > > /Mårten > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 11:43:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (s014.dhcp212-24.cybercable.fr [212.198.24.14]) by hub.freebsd.org (Postfix) with ESMTP id 14A5237B71E for ; Mon, 19 Mar 2001 11:43:38 -0800 (PST) (envelope-from thierry@herbelot.com) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id UAA61758 for ; Mon, 19 Mar 2001 20:43:35 +0100 (CET) (envelope-from thierry@herbelot.com) Message-ID: <3AB66167.7DE93AB2@herbelot.com> Date: Mon, 19 Mar 2001 20:43:35 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: scheduling frequency for threaded applications ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm developping a network benchmark application ("packet blaster"). The current version uses many processes, to send and receive packets, and collate statistics. when I look at top(1), I see most of the time taken is in the "system" category. I assume this is due to the many context switches between the collaborating processes. If I want to get rid of this system overhead, one solution is to use threads (all sharing the same address space, thus no more context switching). My question is : how otfen are the threads rescheduled ? (all threads are mainly always blocked until an event arrives, either a timeout with select() or a packet with recevmsg()) I've had a quick look a TFM, but I don't see anything applicable (pthread_setschedparam(3) for example does not speak of scheduling frequency) -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 11:46:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E28F137B71A for ; Mon, 19 Mar 2001 11:46:27 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2JJkPF05677; Mon, 19 Mar 2001 11:46:25 -0800 (PST) Date: Mon, 19 Mar 2001 11:46:25 -0800 From: Alfred Perlstein To: Thierry Herbelot Cc: hackers@FreeBSD.ORG Subject: Re: scheduling frequency for threaded applications ? Message-ID: <20010319114625.Z29888@fw.wintelcom.net> References: <3AB66167.7DE93AB2@herbelot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AB66167.7DE93AB2@herbelot.com>; from thierry@herbelot.com on Mon, Mar 19, 2001 at 08:43:35PM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Thierry Herbelot [010319 11:43] wrote: > Hello, > > I'm developping a network benchmark application ("packet blaster"). > > The current version uses many processes, to send and receive packets, > and collate statistics. > when I look at top(1), I see most of the time taken is in the "system" > category. I assume this is due to the many context switches between the > collaborating processes. You're incorrect. System means just about any time spent inside the kernel (except interrupts), so basically syscalls count towards this meaning that your application is driving the kernel pretty hard. This is easy for a team of processes, but nearly impossible with a thread based approach. You don't want to use threads. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 11:47:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from altrade.nijmegen.inter.nl.net (altrade.nijmegen.inter.nl.net [193.67.237.6]) by hub.freebsd.org (Postfix) with ESMTP id C31A137B719; Mon, 19 Mar 2001 11:47:32 -0800 (PST) (envelope-from Peter.Blok@inter.NL.net) Received: from ntpc by altrade.nijmegen.inter.nl.net via 1Cust224.tnt6.rtm1.nl.uu.net [213.116.106.224] with SMTP id UAA25344 (8.8.8/1.3); Mon, 19 Mar 2001 20:47:29 +0100 (MET) Reply-To: From: "Peter Blok" To: "'Bill Paul'" , "'Archie Cobbs'" Cc: , Subject: RE: call for testers: port aggregation netgraph module Date: Mon, 19 Mar 2001 20:45:02 +0100 Message-ID: <000001c0b0ad$17b36f00$8a02a8c0@ntpc> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <20010212025610.F37C937B401@hub.freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill, I have tested the port aggregation module on a BayStack 450-12, although I'm not sure the BayStack trunking is compatible with Etherchannel. I'm using a four port Adaptec in my FreeBSD 4.3-BETA system. After some attempts (I have never configured trunking on a BayStack) I had two links up, but without doing anything they went up and down repeatedly. I will continue with it, unless it is clear trunking and EtherChannel are imcompatible. Peter -----Original Message----- From: owner-freebsd-net@FreeBSD.ORG [mailto:owner-freebsd-net@FreeBSD.ORG]On Behalf Of Bill Paul Sent: Monday, February 12, 2001 03:56 To: Archie Cobbs Cc: hackers@FreeBSD.ORG; net@FreeBSD.ORG Subject: Re: call for testers: port aggregation netgraph module > Bill Paul writes: > > http://www.freebsd.org/~wpaul/FEC/4.x/fec.tar.gz > > http://www.freebsd.org/~wpaul/FEC/5.x/fec.tar.gz > > > > This is a call for testers for a netgraph module that can be used to > > aggregate 2 or 4 ethernet interfaces into a single interface. Basically, > > it lets you do things like the following: You know, so far I've gotten close to a dozen replies to this e-mail, but none of contain the one thing I really wanted, namely test results. Look. I said this was a call for *testers*. Not kibitzers, not criticizers, not commenters, not lamers -- *testers*. I want you to try out the code and tell me if it works or not, and if not, describe the bugs so I can fix them. I don't want to hear anything else. If your e-mail concerns any other topic, it will be summarily ignored. Got it people? Good. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 11:59:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (s014.dhcp212-24.cybercable.fr [212.198.24.14]) by hub.freebsd.org (Postfix) with ESMTP id 8C8A237B718 for ; Mon, 19 Mar 2001 11:59:07 -0800 (PST) (envelope-from thierry@herbelot.com) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id UAA61771; Mon, 19 Mar 2001 20:58:54 +0100 (CET) (envelope-from thierry@herbelot.com) Message-ID: <3AB664FE.32CD18CD@herbelot.com> Date: Mon, 19 Mar 2001 20:58:54 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: hackers@FreeBSD.ORG Subject: Re: scheduling frequency for threaded applications ? References: <3AB66167.7DE93AB2@herbelot.com> <20010319114625.Z29888@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > * Thierry Herbelot [010319 11:43] wrote: > > Hello, > > > > I'm developping a network benchmark application ("packet blaster"). > > > > The current version uses many processes, to send and receive packets, > > and collate statistics. > > when I look at top(1), I see most of the time taken is in the "system" > > category. I assume this is due to the many context switches between the > > collaborating processes. > > You're incorrect. System means just about any time spent inside the > kernel (except interrupts), so basically syscalls count towards this > meaning that your application is driving the kernel pretty hard. > > This is easy for a team of processes, but nearly impossible with > a thread based approach. could you please elaborate ? (indeed, if you could also shed some light on the first question : how frequently are threads rescheduled ?) > > You don't want to use threads. > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] PS : the TI-RPC commit was a nice one ! -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 12: 6:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9317837B71D for ; Mon, 19 Mar 2001 12:06:03 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2JK62x06552; Mon, 19 Mar 2001 12:06:02 -0800 (PST) Date: Mon, 19 Mar 2001 12:06:02 -0800 From: Alfred Perlstein To: Thierry Herbelot Cc: hackers@FreeBSD.ORG Subject: Re: scheduling frequency for threaded applications ? Message-ID: <20010319120601.A29888@fw.wintelcom.net> References: <3AB66167.7DE93AB2@herbelot.com> <20010319114625.Z29888@fw.wintelcom.net> <3AB664FE.32CD18CD@herbelot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AB664FE.32CD18CD@herbelot.com>; from thierry@herbelot.com on Mon, Mar 19, 2001 at 08:58:54PM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Thierry Herbelot [010319 11:59] wrote: > Alfred Perlstein wrote: > > > > * Thierry Herbelot [010319 11:43] wrote: > > > Hello, > > > > > > I'm developping a network benchmark application ("packet blaster"). > > > > > > The current version uses many processes, to send and receive packets, > > > and collate statistics. > > > when I look at top(1), I see most of the time taken is in the "system" > > > category. I assume this is due to the many context switches between the > > > collaborating processes. > > > > You're incorrect. System means just about any time spent inside the > > kernel (except interrupts), so basically syscalls count towards this > > meaning that your application is driving the kernel pretty hard. > > > > This is easy for a team of processes, but nearly impossible with > > a thread based approach. > > could you please elaborate ? (indeed, if you could also shed some light > on the first question : how frequently are threads rescheduled ?) I really have no idea how frequently threads are rescheduled. the point is this: In FreeBSD a threaded application has a single process context, meaning that the kernel schedules all threads as a single entity. In effect you limit the parallelness(?) by using threads. Now if you want kernel threads, then use the linux-threads port, however you're back to normal process scheduling because afaik linux-threads (at least when run on FreeBSD) are implemented with processes. I don't think you understand that the overhead you're seeing is most likely _not_ because of any scheduler issue, but more likely because you're asking the kernel to do a signifigant amount of work for you. This is about as far as I'm going to go on the issue, basically once you make your "write()" syscall, you enter into 'system' time because you're having the kernel do work for you. The getrusage() manpage might be a good place to look for more answers. > PS : the TI-RPC commit was a nice one ! There's still a few kinks to work out, hope to have it fixed within the next couple of days. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 12:31:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from moutvdom00.kundenserver.de (moutvdom00.kundenserver.de [195.20.224.149]) by hub.freebsd.org (Postfix) with ESMTP id 1EBEB37B71B for ; Mon, 19 Mar 2001 12:31:04 -0800 (PST) (envelope-from volker@thalreit.de) Received: from [195.20.224.220] (helo=mrvdom04.kundenserver.de) by moutvdom00.kundenserver.de with esmtp (Exim 2.12 #2) id 14f6Ix-0003sC-00; Mon, 19 Mar 2001 21:31:03 +0100 Received: from p3e9b810a.dip.t-dialin.net ([62.155.129.10] helo=ikarus.thalreit) by mrvdom04.kundenserver.de with esmtp (Exim 2.12 #2) id 14f6In-0001M5-00; Mon, 19 Mar 2001 21:30:54 +0100 Received: (from volker@localhost) by ikarus.thalreit (8.10.2/8.10.2/SuSE Linux 8.10.0-0.3) id f2JKUuE00907; Mon, 19 Mar 2001 21:30:56 +0100 Date: Mon, 19 Mar 2001 21:30:55 +0100 From: Volker Jahns To: hackers@freebsd.org Cc: Volker.Jahns@dpma.de Subject: Serial port open Message-ID: <20010319213055.A881@ikarus.thalreit> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I do have a small problem w/ serial IO. I have attached code to 1. open a serial line, 2. set terminal attributes, 3. close the serial port, 4. iterate thru 1.-3. a second time. /* serial test */ /* FreeBSD 3 second */ #include #include #include #include #include #include #include #define BENCHMARK 2 int main (int argc, char **argv) { int err, rfd, tset, i, j; struct termios tp, op; /* test loop to check how long it takes to open/close the port */ for ( j = 0; j < BENCHMARK; j++) { rfd = open("/dev/ttyd0", O_RDWR | O_NOCTTY | O_NONBLOCK | O_NDELAY); printf("open\t\t: errno %d\n", errno); if (rfd == -1) { perror("open: couldn't open /dev/ttyd0"); } else { fcntl(rfd, F_SETFL, 0); } /* get terminal attributes */ tcgetattr(rfd, &op); tcgetattr(rfd, &tp); /* set terminal attr */ cfsetispeed(&tp, 9600); cfsetospeed(&tp, 9600); tp.c_iflag = 0; tp.c_oflag = 0; tp.c_cflag = 0; tp.c_lflag = 0; for ( i = 0; i < NCCS; i++) { tp.c_cc[i] = 0; } tp.c_iflag &= (IXON | IXOFF | IXANY); tp.c_cflag |= PARENB; tp.c_cflag &= ~PARODD; tp.c_cflag |= CLOCAL; tp.c_cflag |= CREAD; tp.c_cflag |= CS8; tp.c_cflag |= CSTOPB; tp.c_cflag |= CSIZE; tp.c_lflag &= ~(ICANON | ECHO | ECHOE | ISIG); tp.c_cc[VMIN]=0; tp.c_cc[VTIME]=1; /* set terminal attributes */ tcsetattr(rfd, TCSANOW, &tp); /* reset terminal attributes */ tcsetattr(rfd, TCSANOW, &op); close(rfd); /* 2nd service */ } } between the 1st call to close and the 2nd call to open the system spends some 3 (three !) seconds. volker@nemo testing > time ./io_fbsd-2 open : errno 0 open : errno 0 real 0m2.998s user 0m0.000s sys 0m0.004s I am running FreeBSD nemo.zvr.dpma.de 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Thu Mar 15 12:58:51 CET 2001 but happens also w/ 4.1. What is actually wrong about the code? What is it I am missing? If this is the incorrect list to consider the problem, could you please redirect? for case anybody wants to know, here is the relevant output of kdump 21753 io_fbsd-2 985009390.419433 RET close 0 21753 io_fbsd-2 985009390.419451 CALL open(0x80488a0,0x8006,0xbfbff6a0) 21753 io_fbsd-2 985009390.419467 NAMI "/dev/ttyd0" 21753 io_fbsd-2 985009393.411359 RET open 3 21753 io_fbsd-2 985009393.411426 CALL write(0x1,0x804b000,0x10) It shows, that it takes approx 3 seconds between the call to open and the return of the call. This is actually is striped down version of code to read out data of a serially connected weatherstation. -- Volker Jahns, Thalreit/DE, +49 80 35 69 25, mailto:Volker.Jahns@thalreit.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 12:46: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mw2.texas.net (mw2.texas.net [206.127.30.12]) by hub.freebsd.org (Postfix) with ESMTP id 99D6A37B726 for ; Mon, 19 Mar 2001 12:45:59 -0800 (PST) (envelope-from hackthis@texas.net) Received: from hackthis (tcnet07-051.sat.texas.net [209.99.119.177]) by mw2.texas.net (8.11.1/8.11.1) with SMTP id f2JKjuU01727 for ; Mon, 19 Mar 2001 14:45:57 -0600 (CST) Message-ID: <005401c0b0b8$1e7f3ca0$6346a8c0@hackthis> From: "hackthis" To: Subject: gcc and exceptions and frame.c Date: Mon, 19 Mar 2001 15:03:57 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0051_01C0B085.D2B83380" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0051_01C0B085.D2B83380 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Freebsd-hackers: Been trying to debug a program of mine and keep running into these = errors. I was wondering if there is a problem with exceptions and gccor with freebsd in = general?? I think frame.c has to do with exceptions. What do you all think about all those cannot access memory errors. Thanks for any help, c.r.g. # gdb /a.out ./a.out.core GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you = are welcome to change it and/or distribute copies of it under certain = conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for = details. This GDB was configured as "i386-unknown-freebsd"... Core was generated by `a.out'. Program terminated with signal 6, Abort trap. Cannot access memory at address 0x280f0e3c. #0 0x2815c530 in ?? ()Cannot access memory at address 0x280f0e3c. (gdb) bt #0 0x2815c530 in ?? ()Cannot access memory at address 0x280f0e3c. #2 0x2816a55f in ?? ()Cannot access memory at address 0x280f0e3c. #3 0x28169fc3 in ?? ()Cannot access memory at address 0x280f0e3c. #4 0x28169d71 in ?? ()Cannot access memory at address 0x280f0e3c. #5 0xbfbfdfcc in ?? ()Cannot access memory at address 0x280f0e3c. #6 0x80a3aa7 in frame_init (ob=3D0x8119cc8) at ./frame.c:626 626 ./frame.c: No such file or directory. Current language: auto; currently c #7 0x80a3afa in find_fde (pc=3D0x80a2e46) at ./frame.c:626 626 in ./frame.c #8 0x80a3ffc in __frame_state_for (pc_target=3D0x80a2e46, = state_in=3D0x819cbc0) at ./frame.c:627 627 in ./frame.c #9 0x80a2e57 in __throw ()Cannot access memory at address 0x280f0e3c. #10 0x80a4337 in __builtin_new (sz=3D356) Cannot access memory at address 0x280f0e3c. Current language: auto; currently c++ #16 0x28139b3a in ?? ()Cannot access memory at address 0x280f0e3c. #17 0x0 in ?? ()Cannot access memory at address 0x280f0e3c. Initial frame selected; you cannot go up. (gdb) info threads * 1 process 8373 0x0 in ?? ()Cannot access memory at address = 0x280f0e3c. warning: Couldn't restore frame in current thread, at frame 0 0x0 in ?? ()Cannot access memory at address 0x280f0e3c. compiling with=20 $ g++295 -v Reading specs from = /usr/local/lib/gcc-lib/i386-portbld-freebsd3.4/2.95.2/specs gcc version 2.95.2 19991024 (release) ------=_NextPart_000_0051_01C0B085.D2B83380 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Freebsd-hackers:
 
Been trying to debug a program of mine = and keep=20 running into these errors.  I was wondering
if there is a problem with exceptions = and gccor=20 with freebsd in general??  I think frame.c has to do with=20 exceptions.
What do you all think about all those = cannot access=20 memory errors.
 
Thanks for any help,
c.r.g.
 
# gdb /a.out ./a.out.core
GNU gdb=20 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free = software,=20 covered by the GNU General Public License, and you are
welcome to = change it=20 and/or distribute copies of it under certain conditions.
Type "show = copying"=20 to see the conditions.
There is absolutely no warranty for GDB.  = Type=20 "show warranty" for details.
This GDB was configured as=20 "i386-unknown-freebsd"...
Core was generated by `a.out'.
Program=20 terminated with signal 6, Abort trap.
Cannot access memory at address = 0x280f0e3c.
#0  0x2815c530 in ?? ()Cannot access memory at = address=20 0x280f0e3c.
(gdb) bt
#0  0x2815c530 in ?? ()Cannot access = memory at=20 address 0x280f0e3c.
#2  0x2816a55f in ?? ()Cannot access memory = at=20 address 0x280f0e3c.
#3  0x28169fc3 in ?? ()Cannot access memory = at=20 address 0x280f0e3c.
#4  0x28169d71 in ?? ()Cannot access memory = at=20 address 0x280f0e3c.
#5  0xbfbfdfcc in ?? ()Cannot access memory = at=20 address 0x280f0e3c.
#6  0x80a3aa7 in frame_init (ob=3D0x8119cc8) = at=20 ./frame.c:626
626     ./frame.c: No such file or=20 directory.
Current language:  auto; currently c
#7  = 0x80a3afa in=20 find_fde (pc=3D0x80a2e46) at = ./frame.c:626
626     in=20 ./frame.c
#8  0x80a3ffc in __frame_state_for = (pc_target=3D0x80a2e46,=20 state_in=3D0x819cbc0)
    at=20 ./frame.c:627
627     in ./frame.c
#9  = 0x80a2e57=20 in __throw ()Cannot access memory at address 0x280f0e3c.
#10 = 0x80a4337 in=20 __builtin_new (sz=3D356)
Cannot access memory at address = 0x280f0e3c.
Current=20 language:  auto; currently c++
#16 0x28139b3a in ?? ()Cannot = access=20 memory at address 0x280f0e3c.
#17 0x0 in ?? ()Cannot access memory at = address=20 0x280f0e3c.
Initial frame selected; you cannot go up.

(gdb) = info=20 threads
* 1 process 8373  0x0 in ?? ()Cannot access memory at = address=20 0x280f0e3c.
warning: Couldn't restore frame in current thread, at = frame=20 0
0x0 in ?? ()Cannot access memory at address=20 0x280f0e3c.



compiling with
$ g++295 -v
Reading = specs from=20 /usr/local/lib/gcc-lib/i386-portbld-freebsd3.4/2.95.2/specs
gcc = version=20 2.95.2 19991024 (release)
------=_NextPart_000_0051_01C0B085.D2B83380-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 13:33: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id D913737B724 for ; Mon, 19 Mar 2001 13:32:58 -0800 (PST) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.11.3/8.11.3) id f2JLWa467799; Mon, 19 Mar 2001 16:32:36 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.7p2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 In-Reply-To: <005401c0b0b8$1e7f3ca0$6346a8c0@hackthis> Date: Mon, 19 Mar 2001 16:32:36 -0500 (EST) Organization: Verizon Laboratories Inc. From: "Alexander N. Kabaev" To: hackthis Subject: RE: gcc and exceptions and frame.c Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The stack trace looks pretty useless because of all these "cannot access memory" messages. Anyway, it seems like your program is dying because of unhandled exception. Either you did not provide the suitable try {} catch construct or bug in GCC or your code prevents DWARF unwinder from finding suitable handler for the exception. It there any particular reason why you are using gcc295 from ports instea= d of FreeBSD stock compiler? Stock compiler does not use DWARF and is supposed t= o handle exceptions correctly, so unless there are some really good reasons, I would recommend you to use the stock compiler. It is hard to say what exactly goes wrong without seeing actual code of you= r program. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 15:48:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com [194.25.134.81]) by hub.freebsd.org (Postfix) with ESMTP id DE8D137B71B; Mon, 19 Mar 2001 15:48:52 -0800 (PST) (envelope-from titus@pleach.de) Received: from fwd03.sul.t-online.com by mailout03.sul.t-online.com with smtp id 14f9Jd-0001CD-04; Tue, 20 Mar 2001 00:43:57 +0100 Received: from mail.net (340050866639-0001@[62.155.189.229]) by fmrl03.sul.t-online.com with esmtp id 14f9Ja-2BxaFsC; Tue, 20 Mar 2001 00:43:54 +0100 Received: from schweinkram.pleach-hamburg.de (localhost [127.0.0.1]) by mail.net (8.11.1/8.9.2) with ESMTP id f2JNfIx53018; Tue, 20 Mar 2001 00:41:18 +0100 (CET) (envelope-from titus@pleach-hamburg.de) Received: from pleach-hamburg.de (dialin01.pleachconn.de [192.168.2.10]) by schweinkram.pleach-hamburg.de (8.11.1/8.11.1) with ESMTP id f2JNY1v52954; Tue, 20 Mar 2001 00:34:02 +0100 (CET) (envelope-from titus@pleach-hamburg.de) Message-ID: <3AB697F1.4BF23D6E@pleach-hamburg.de> Date: Tue, 20 Mar 2001 00:36:17 +0100 From: Titus von Boxberg X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: de-DE,en MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: hackers@FreeBSD.ORG Subject: Re: GCC Upgrade? References: <3AB310DF.A43A8BC@sm.socccd.cc.ca.us> <20010317104642.Y29888@fw.wintelcom.net> <20010317203506.A57756@dragon.nuxi.com> <3AB60FAC.DB181706@pleach-hamburg.de> <20010319105046.A64519@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: 340050866639-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Mon, Mar 19, 2001 at 02:54:52PM +0100, Titus von Boxberg wrote: > > Since at least aug. 2000 (according to the mailing list > > archives) the exception handling in base system g++ is broken > > (at least for multithreaded programs) > > I am not aware of exception handling being broken (more so than in 4.x). g++ in the base is nok, as the package it's ok. > Can you point me to a PR, or send me a _small_ sample program? Sorry, I don't have yet isolated the problem. But this link seems to describe exactly the same problem. "http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=298763+300854+ /usr/local/www/db/text/2000/freebsd-hackers/20000716.freebsd-hackers" you can search for "DWARF AND exception"; then you'll find the links. I'm using omniORB, and on their home page you can find a hint in the docs describing the same thing (but with g++ on a AIX/RS6000). Before end of april I cannot investigate the problem any further. please let me know by then if I may help you with that problem. regards titus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 15:59: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id DEAE137B71B for ; Mon, 19 Mar 2001 15:58:59 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id AAA88607; Tue, 20 Mar 2001 00:55:20 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103192355.AAA88607@info.iet.unipi.it> Subject: Re: Routing latency In-Reply-To: <3AB65EC9.4D969490@herbelot.com> from Thierry Herbelot at "Mar 19, 2001 08:32:25 pm" To: Thierry Herbelot Date: Tue, 20 Mar 2001 00:55:19 +0100 (CET) Cc: "[M_rten Wikstr_m]" , "'freebsd-hackers@freebsd.org'" X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > (moreover, the dc(4) > driver which is used for your NIC has some interesting performance > improvements in the forthcoming 4.3-Release) like what ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 16: 2: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 34B9C37B71C for ; Mon, 19 Mar 2001 16:01:59 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id SAA03869; Mon, 19 Mar 2001 18:59:10 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010319191312.03fd65d0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Mon, 19 Mar 2001 19:14:54 -0500 To: Thierry Herbelot , =?iso-8859-1?Q?M=E5rten?= =?iso-8859-1?Q?_Wikstr=F6m?= From: Dennis Subject: Re: Routing latency Cc: "'freebsd-hackers@freebsd.org'" In-Reply-To: <3AB65EC9.4D969490@herbelot.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:32 PM 03/19/2001, Thierry Herbelot wrote: >Hello, > >the FreeBSD TCP/IP stack uses the "system tick timer" for some delay >(maybe only for TCP). > >you may want to use a HZ=1000 option (see the LINT config file) in a >recompiled kernel and see if things go better. (moreover, the dc(4) >driver which is used for your NIC has some interesting performance >improvements in the forthcoming 4.3-Release) > > TfH Cool. Is the 21143 now started in store-and-forward mode and has the mandatory watchdog timeout been fixed? Im getting tired of hacking it every release. DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 16:12:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id C380837B721 for ; Mon, 19 Mar 2001 16:12:21 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id TAA03923; Mon, 19 Mar 2001 19:11:29 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010319191529.03fd6a90@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Mon, 19 Mar 2001 19:27:13 -0500 To: =?iso-8859-1?Q?M=E5rten?= =?iso-8859-1?Q?_Wikstr=F6m?= , "'freebsd-hackers@freebsd.org'" From: Dennis Subject: Re: Routing latency In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:22 AM 03/19/2001, M=E5rten Wikstr=F6m wrote: >I've performed a routing test between a FreeBSD box and a Linux box. I >measured the latency and the result was not what I had expected. Both >systems had the peak at 100 us (microseconds), but whereas the Linux box= had >_no_ packet over 200 us, the FreeBSD box delayed some packets up to 2 ms! >Looking at the time series, it seems that the packets are delayed at= regular >intervals, about every second. My guess is that some timer interrupt >triggers every second and steals too much cpu. So my question is, how can I >decrease this routing delay? Were you loading the interface, or just passing nominal streams? What pps=20 did you pass through the box? Most likely the "delays" are only seen when=20 the machine is close to capacity (the slow CPU you are using doesnt help). Latency under load and general latency are very different. Differing=20 methods of handling backup conditions may have different goals; the proper= =20 goal is overall stability and NOT packet efficiency. It doesnt matter how=20 fast a man runs if he doesnt finish the race. The problem with LINUX is that it works to a point and then chokes, while=20 freebsd works up to higher thresholds. You cant evaluate a subsystem with=20 one somewhat bogus test, without looking at the system as a whole. If you are using the dc driver, make certain it is operating in=20 store-and-forward mode, the default configuration starts in a mode that=20 only works on 10mb/s connections. dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 16:17:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ohm.physics.purdue.edu (ohm.physics.purdue.edu [128.210.146.32]) by hub.freebsd.org (Postfix) with ESMTP id 63E8D37B71C for ; Mon, 19 Mar 2001 16:17:44 -0800 (PST) (envelope-from will@physics.purdue.edu) Received: (from will@localhost) by ohm.physics.purdue.edu (8.11.2/8.9.3) id f2K0KTD97949; Mon, 19 Mar 2001 19:20:29 -0500 (EST) (envelope-from will@physics.purdue.edu) X-Authentication-Warning: ohm.physics.purdue.edu: will set sender to will@physics.purdue.edu using -f Date: Mon, 19 Mar 2001 19:20:29 -0500 From: Will Andrews To: Dennis Cc: Thierry Herbelot , =?iso-8859-1?Q?M=E5rten_Wikstr=F6m?= , "'freebsd-hackers@freebsd.org'" Subject: Re: Routing latency Message-ID: <20010319192029.O61859@ohm.physics.purdue.edu> Reply-To: Will Andrews References: <3AB65EC9.4D969490@herbelot.com> <5.0.0.25.0.20010319191312.03fd65d0@mail.etinc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="5R+hlb4DVXk9Au0e" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.0.25.0.20010319191312.03fd65d0@mail.etinc.com>; from dennis@etinc.com on Mon, Mar 19, 2001 at 07:14:54PM -0500 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --5R+hlb4DVXk9Au0e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 19, 2001 at 07:14:54PM -0500, Dennis wrote: > Cool. Is the 21143 now started in store-and-forward mode and has the=20 > mandatory watchdog timeout been fixed? Im getting tired of hacking it eve= ry=20 > release. Submit a PR to fix the problem? --=20 wca --5R+hlb4DVXk9Au0e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6tqJNF47idPgWcsURAtIvAJ9DrwRvYZCMggk3vVVODFwWwgDrywCfefr9 ncWP/uy+w5FeUsEh1UbYnh8= =GcF8 -----END PGP SIGNATURE----- --5R+hlb4DVXk9Au0e-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 16:30:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id BE0BC37B724 for ; Mon, 19 Mar 2001 16:30:24 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id TAA04016; Mon, 19 Mar 2001 19:31:08 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010319194401.040862b0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Mon, 19 Mar 2001 19:46:53 -0500 To: Will Andrews From: Dennis Subject: Re: Routing latency Cc: Thierry Herbelot , =?iso-8859-1?Q?M=E5rten?= =?iso-8859-1?Q?_Wikstr=F6m?= , "'freebsd-hackers@freebsd.org'" In-Reply-To: <20010319192029.O61859@ohm.physics.purdue.edu> References: <5.0.0.25.0.20010319191312.03fd65d0@mail.etinc.com> <3AB65EC9.4D969490@herbelot.com> <5.0.0.25.0.20010319191312.03fd65d0@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:20 PM 03/19/2001, Will Andrews wrote: >On Mon, Mar 19, 2001 at 07:14:54PM -0500, Dennis wrote: > > Cool. Is the 21143 now started in store-and-forward mode and has the > > mandatory watchdog timeout been fixed? Im getting tired of hacking it > every > > release. > >Submit a PR to fix the problem? I never got an answer (as usual) from bill paul when I made the suggestions, and noone seemed interested in getting it fixed. He seems to get insulted when I infer that he did something wrong. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 16:32:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ohm.physics.purdue.edu (ohm.physics.purdue.edu [128.210.146.32]) by hub.freebsd.org (Postfix) with ESMTP id DCD5737B728 for ; Mon, 19 Mar 2001 16:32:31 -0800 (PST) (envelope-from will@physics.purdue.edu) Received: (from will@localhost) by ohm.physics.purdue.edu (8.11.2/8.9.3) id f2K0a4p98072; Mon, 19 Mar 2001 19:36:04 -0500 (EST) (envelope-from will@physics.purdue.edu) X-Authentication-Warning: ohm.physics.purdue.edu: will set sender to will@physics.purdue.edu using -f Date: Mon, 19 Mar 2001 19:36:04 -0500 From: Will Andrews To: Dennis Cc: Will Andrews , Thierry Herbelot , =?iso-8859-1?Q?M=E5rten_Wikstr=F6m?= , "'freebsd-hackers@freebsd.org'" Subject: Re: Routing latency Message-ID: <20010319193604.Q61859@ohm.physics.purdue.edu> Reply-To: Will Andrews References: <5.0.0.25.0.20010319191312.03fd65d0@mail.etinc.com> <3AB65EC9.4D969490@herbelot.com> <5.0.0.25.0.20010319191312.03fd65d0@mail.etinc.com> <20010319192029.O61859@ohm.physics.purdue.edu> <5.0.0.25.0.20010319194401.040862b0@mail.etinc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="H07tSIYKgb2dW+3H" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.0.25.0.20010319194401.040862b0@mail.etinc.com>; from dennis@etinc.com on Mon, Mar 19, 2001 at 07:46:53PM -0500 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --H07tSIYKgb2dW+3H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 19, 2001 at 07:46:53PM -0500, Dennis wrote: > I never got an answer (as usual) from bill paul when I made the=20 > suggestions, and noone seemed interested in getting it fixed. He seems to= =20 > get insulted when I infer that he did something wrong. It's like they say: "money talks". Similarly, "patches talk". Suggestions don't really do that. --=20 wca --H07tSIYKgb2dW+3H Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6tqXzF47idPgWcsURApwNAJ0UDlhy53lMQ8gShp8q112AliPQ7wCeLFJ+ 1JnqYBoUMLNBItl7CLEWu40= =evFF -----END PGP SIGNATURE----- --H07tSIYKgb2dW+3H-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 16:54:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 9B1F137B739 for ; Mon, 19 Mar 2001 16:54:14 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2K0obe71895; Mon, 19 Mar 2001 16:50:37 -0800 (PST) (envelope-from obrien) Date: Mon, 19 Mar 2001 16:50:28 -0800 From: "David O'Brien" To: "Alexander N. Kabaev" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: gcc and exceptions and frame.c Message-ID: <20010319165028.A71827@dragon.nuxi.com> Reply-To: freebsd-hackers@FreeBSD.ORG References: <005401c0b0b8$1e7f3ca0$6346a8c0@hackthis> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ak03@gte.com on Mon, Mar 19, 2001 at 04:32:36PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 19, 2001 at 04:32:36PM -0500, Alexander N. Kabaev wrote: > It there any particular reason why you are using gcc295 from ports > instead of FreeBSD stock compiler? I would assume because he has a 3.4 box: $ g++295 -v specs from /usr/local/lib/gcc-lib/i386-portbld-freebsd3.4/2.95.2/specs and the stock compiler there is 2.7.2.3. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 17:12:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx7.port.ru (mx7.port.ru [194.67.23.44]) by hub.freebsd.org (Postfix) with ESMTP id 1BF5C37B73F; Mon, 19 Mar 2001 17:12:27 -0800 (PST) (envelope-from kabaev@mail.ru) Received: from adsl-141-154-120-34.bostma.adsl.bellatlantic.net ([141.154.120.34] helo=kan.dnsalias.net) by mx7.port.ru with esmtp (Exim 3.14 #15) id 14fAhB-0005KQ-00; Tue, 20 Mar 2001 04:12:22 +0300 Received: (from kan@localhost) by kan.dnsalias.net (8.11.3/8.11.3) id f2K1CJM09332; Mon, 19 Mar 2001 20:12:19 -0500 (EST) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.7p2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3AB697F1.4BF23D6E@pleach-hamburg.de> Date: Mon, 19 Mar 2001 20:12:18 -0500 (EST) From: "Alexander N. Kabaev" To: Titus von Boxberg Subject: Re: GCC Upgrade? Cc: hackers@FreeBSD.ORG, obrien@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Mar-2001 Titus von Boxberg wrote: > David O'Brien wrote: >> >> On Mon, Mar 19, 2001 at 02:54:52PM +0100, Titus von Boxberg wrote: >> > Since at least aug. 2000 (according to the mailing list >> > archives) the exception handling in base system g++ is broken >> > (at least for multithreaded programs) The problem you are talking about has nothing to do with threads. Rather, the problem was with the way in which GCC handles inline function expansions. > > Sorry, I don't have yet isolated the problem. > But this link seems to describe exactly the same problem. > "http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=298763+300854+ > /usr/local/www/db/text/2000/freebsd-hackers/20000716.freebsd-hackers" I thought GCC 2.95.3 has this problem fixed, but it turns out I was wrong. I've had patches to fix this particular breakage for ages now and I even offered them to David O'Brien on more than one occasion. The fix has been posted on the gcc-devel mailing list and Berndt Schmidt even included it into some of GCC 2.95.3-testXX release. And that time I decided that my job is done, but apparently Berndt managed to revert (most likely, by mistake) before release. I think my relative unrelated changes have been killed as part of the bigger sjlj exceptions rewrite by Mike Henderson :( > you can search for "DWARF AND exception"; then you'll find the links. > > I'm using omniORB, and on their home page you can find a > hint in the docs describing the same thing (but with g++ on a AIX/RS6000). > Yet another problem I have patches for. GCC does not handle PIC register correctly when handling exceptions thrown across shared library boundaries. Additionally, the shared libraries in AIX make the challenge of sharing exception context state among all shared libraries in the executable very interesting. I was unable to get these fixes into official CVS source - FSF guys apparently decided that the problem cannot be fixed. They even seriously tried to convince me that my patch could not work except by coincidence without even taking a sigle look at the patch itself - even though that 'coincidence' reliably works for me in multithreaded CORBA server written using omniORB :) I basically gave up on them. Drop me a line if you need help getting GCC 2.95.3 work properly on AIX 4.x. > Before end of april I cannot investigate the problem any further. > please let me know by then if I may help you with that problem. > > regards > titus > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message ---------------------------------- E-Mail: Alexander N. Kabaev Date: 19-Mar-2001 Time: 19:05:53 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 17:33:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id B1F1237B71B for ; Mon, 19 Mar 2001 17:33:22 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2K1UTu72447; Mon, 19 Mar 2001 17:30:29 -0800 (PST) (envelope-from obrien) Date: Mon, 19 Mar 2001 17:30:28 -0800 From: "David O'Brien" To: "Alexander N. Kabaev" Cc: Titus von Boxberg , hackers@FreeBSD.ORG Subject: Re: GCC Upgrade? Message-ID: <20010319173028.A72327@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <3AB697F1.4BF23D6E@pleach-hamburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from kabaev@mail.ru on Mon, Mar 19, 2001 at 08:12:18PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Mar 19, 2001 at 08:12:18PM -0500, Alexander N. Kabaev wrote: > The fix has been posted on the gcc-devel mailing list and Berndt > Schmidt even included it into some of GCC 2.95.3-testXX release. And > that time I decided that my job is done, but apparently Berndt managed > to revert (most likely, by mistake) before release. I think my > relative unrelated changes have been killed as part of the bigger sjlj > exceptions rewrite by Mike Henderson :( From: Bernd Schmidt Subject: 2.95.4 plans Date: Fri, 16 Mar 2001 16:18:03 +0000 (GMT) To: Now that 2.95.3 is out, I'll again accept suggestions what to include in 2.95.4, so please send candidate patches and bug reports. One major item that needs fixing is the sjlj eh problem; the fix for this had to be taken out of the 2.95.3 release since it introduced too many other problems. I would bring up the issue again with Bernd. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 18:32: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.tgd.net (rand.tgd.net [64.81.67.117]) by hub.freebsd.org (Postfix) with SMTP id 0D57537B732 for ; Mon, 19 Mar 2001 18:32:01 -0800 (PST) (envelope-from sean@mailhost.tgd.net) Received: (qmail 84702 invoked by uid 1001); 20 Mar 2001 02:31:35 -0000 Date: Mon, 19 Mar 2001 18:31:35 -0800 From: sean-freebsd-hackers@chittenden.org To: freebsd-hackers@freebsd.org Subject: Easy way to compute memory stats? (procfs?) Message-ID: <20010319183135.B84536@rand.tgd.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mxv5cy4qt+RJ9ypb" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Key: 0x1EDDFAAD X-PGP-Fingerprint: C665 A17F 9A56 286C 5CFB 1DEA 9F4F 5CEF 1EDD FAAD X-Web-Homepage: http://sean.chittenden.org/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --mxv5cy4qt+RJ9ypb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Is there an easy way (from script ideally) to get the following stats: free physical mem (avail ram) free swap total avail mem any two of the three would be great. If such a beast doesn't exist, what are the easiest calls to use to get at them so I could write some programs that would output this info. -sc --=20 Sean Chittenden sean@chittenden.org --mxv5cy4qt+RJ9ypb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: For info see http://www.gnupg.org iEYEARECAAYFAjq2wQcACgkQn09c7x7d+q0aIgCg1ZbV39PG825qKvL9o0wboMDB awUAn3Bv+ctInQIjAQJcqBFgAPerKail =ybAj -----END PGP SIGNATURE----- --mxv5cy4qt+RJ9ypb-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 18:35:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ohm.physics.purdue.edu (ohm.physics.purdue.edu [128.210.146.32]) by hub.freebsd.org (Postfix) with ESMTP id 4B50337B737 for ; Mon, 19 Mar 2001 18:35:43 -0800 (PST) (envelope-from will@physics.purdue.edu) Received: (from will@localhost) by ohm.physics.purdue.edu (8.11.2/8.9.3) id f2K2cqK98441; Mon, 19 Mar 2001 21:38:52 -0500 (EST) (envelope-from will@physics.purdue.edu) X-Authentication-Warning: ohm.physics.purdue.edu: will set sender to will@physics.purdue.edu using -f Date: Mon, 19 Mar 2001 21:38:52 -0500 From: Will Andrews To: Devin Butterfield Cc: Will Andrews , Dennis , Thierry Herbelot , =?iso-8859-1?Q?M=E5rten_Wikstr=F6m?= , "'freebsd-hackers@freebsd.org'" Subject: Re: Routing latency Message-ID: <20010319213852.V61859@ohm.physics.purdue.edu> Reply-To: Will Andrews References: <5.0.0.25.0.20010319191312.03fd65d0@mail.etinc.com> <5.0.0.25.0.20010319194401.040862b0@mail.etinc.com> <20010319193604.Q61859@ohm.physics.purdue.edu> <01031918115500.51096@dbm.wireless.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="DA/nJAuSA+D6vj14" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01031918115500.51096@dbm.wireless.net>; from dbutter@wireless.net on Mon, Mar 19, 2001 at 06:11:55PM -0800 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --DA/nJAuSA+D6vj14 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 19, 2001 at 06:11:55PM -0800, Devin Butterfield wrote: > I'm not defending Dennis here, but this statement infers that nothing get= s=20 > done unless maintainers are >=20 > a) paid >=20 > or=20 >=20 > b) someone else does the work for them. >=20 > I certainly hope this is not the case. No, it is not. My statement is an attack on his complaint that he has to "re hack a fix in every release", a problem he could solve by submitting his patches. It is pointless to complain about having to do something if you don't consider simple avenues to solve the problem. --=20 wca --DA/nJAuSA+D6vj14 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6tsK7F47idPgWcsURAnjgAJwOEmfHTRHmsnRvCeh8s3iImXfP8gCfVbfR +EZuRJpK+pVquA8rT/oLbGg= =0H9t -----END PGP SIGNATURE----- --DA/nJAuSA+D6vj14-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 19:43:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 2982137B730 for ; Mon, 19 Mar 2001 19:43:21 -0800 (PST) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id 483403E09 for ; Mon, 19 Mar 2001 19:43:20 -0800 (PST) To: hackers@freebsd.org Subject: Minor (cosmetic) ps(1) fixes Date: Mon, 19 Mar 2001 19:43:20 -0800 From: Dima Dorfman Message-Id: <20010320034320.483403E09@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello -hackers When the kinfo_proc structure was introduced, the ps(1) manual page was not updated. Thus, it still talks about keywords that don't exist. Also, one line in ps.c was forgotten. The latter results in an annoying warning when using ps(1) with the -j flag: dd@ref5% ps -j ps: sess: keyword not found [ normal ps(1) output follows ] Attached is a patch that fixes this bug, and updates the man page. Comments? If this is okay, could someone please commit at least the source part? Thanks Dima Dorfman dima@unixfreak.org Index: ps.1 =================================================================== RCS file: /st/src/FreeBSD/src/bin/ps/ps.1,v retrieving revision 1.30 diff -u -r1.30 ps.1 --- ps.1 2001/02/01 16:24:50 1.30 +++ ps.1 2001/03/20 03:34:55 @@ -99,7 +99,7 @@ header per page of information. .It Fl j Print information associated with the following keywords: -user, pid, ppid, pgid, sess, jobc, state, tt, time and command. +user, pid, ppid, pgid, jobc, state, tt, time and command. .It Fl L List the set of available keywords. .It Fl l @@ -367,8 +367,6 @@ job control count .It ktrace tracing flags -.It ktracep -tracing vnode .It lim memoryuse limit .It logname @@ -400,8 +398,6 @@ wait channel (as an address) .It oublk total blocks written (alias oublock) -.It p_ru -resource usage (valid only for zombie) .It paddr swap address .It pagein @@ -427,8 +423,6 @@ reverse link on run queue, or 0 .It rss resident set size -.It rsz -resident set size + (text size / text use count) (alias rssize) .It rtprio realtime priority (101 = not a realtime process) .It ruid @@ -436,8 +430,6 @@ .Tn ID .It ruser user name (from ruid) -.It sess -session pointer .It sig pending signals (alias pending) .It sigcatch Index: ps.c =================================================================== RCS file: /st/src/FreeBSD/src/bin/ps/ps.c,v retrieving revision 1.36 diff -u -r1.36 ps.c --- ps.c 2001/03/03 01:46:58 1.36 +++ ps.c 2001/03/20 03:34:55 @@ -104,7 +104,7 @@ static uid_t *getuids(const char *, int *); char dfmt[] = "pid tt state time command"; -char jfmt[] = "user pid ppid pgid sess jobc state tt time command"; +char jfmt[] = "user pid ppid pgid jobc state tt time command"; char lfmt[] = "uid pid ppid cpu pri nice vsz rss wchan state tt time command"; char o1[] = "pid"; char o2[] = "tt state time command"; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 21: 3:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id CE6A837B729 for ; Mon, 19 Mar 2001 21:02:56 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id PAA11475; Tue, 20 Mar 2001 15:32:22 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010319183135.B84536@rand.tgd.net> Date: Tue, 20 Mar 2001 15:32:22 +1030 (CST) From: "Daniel O'Connor" To: sean-freebsd-hackers@chittenden.org Subject: RE: Easy way to compute memory stats? (procfs?) Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Mar-01 sean-freebsd-hackers@chittenden.org wrote: > Is there an easy way (from script ideally) to get the following > stats: > > free physical mem (avail ram) > free swap > total avail mem > > any two of the three would be great. If such a beast doesn't > exist, what are the easiest calls to use to get at them so I could > write some programs that would output this info. -sc I think you can get some of these from sysctl.. Unfortunatly I don't know the MIB's to use :) Try browsing sysctl -a You could also try calling vmstat, and/or iostat. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 21:38:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (s014.dhcp212-24.cybercable.fr [212.198.24.14]) by hub.freebsd.org (Postfix) with ESMTP id 8304B37B740 for ; Mon, 19 Mar 2001 21:38:32 -0800 (PST) (envelope-from thierry@herbelot.com) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id GAA62458; Tue, 20 Mar 2001 06:37:09 +0100 (CET) (envelope-from thierry@herbelot.com) Message-ID: <3AB6EC81.3A781C46@herbelot.com> Date: Tue, 20 Mar 2001 06:37:05 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Gilbert Gong Cc: hackers@freebsd.org Subject: Re: Routing latency References: <3AB65EC9.4D969490@herbelot.com> <001c01c0b0cd$61df43e0$190f000a@ggongws> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gilbert Gong wrote: > > Is this HZ option present in 4.2-STABLE? yes, but I don't know why it does not appear in LINT. This is what I've got in my home box kernel config file : options HZ=1000 TfH > > >From sources update about a week ago: > c106 - ggong@ggong:/usr/src/sys/i386/conf>ls -l LINT > -rw-r--r-- 1 root wheel 88928 Mar 11 21:14 LINT > c107 - ggong@ggong:/usr/src/sys/i386/conf>date > Mon Mar 19 15:34:51 PST 2001 > c108 - ggong@ggong:/usr/src/sys/i386/conf>grep HZ LINT > c109 - ggong@ggong:/usr/src/sys/i386/conf> > -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 21:38:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 09F0637B741 for ; Mon, 19 Mar 2001 21:38:34 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id GAA93693; Tue, 20 Mar 2001 06:37:57 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103200537.GAA93693@info.iet.unipi.it> Subject: any decently supported scanner around ? To: hackers@freebsd.org Date: Tue, 20 Mar 2001 06:37:57 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, is there any scanner (USB i presume by now) which is decently supported by FreeBSD, perhaps something that can be driven using a command line interface rather than SANE or some other huge piece of software ? In the past i have been using with success the Scanjet5p (SCSI interface, but crappy hardware), and, with quite a bit of hacking, the Artec AS6E (parallel port, very slow and low quality), but now i'd really like to get something that does not require me to spend time in writing a driver... cheers luigi ----------------------------------+----------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone (510) 666 2927 . ----------------------------------+----------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 21:45:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (s014.dhcp212-24.cybercable.fr [212.198.24.14]) by hub.freebsd.org (Postfix) with ESMTP id 0346337B71D for ; Mon, 19 Mar 2001 21:45:18 -0800 (PST) (envelope-from thierry@herbelot.com) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id GAA62465; Tue, 20 Mar 2001 06:40:03 +0100 (CET) (envelope-from thierry@herbelot.com) Message-ID: <3AB6ED32.2A8DED32@herbelot.com> Date: Tue, 20 Mar 2001 06:40:02 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Dennis Cc: =?iso-8859-1?Q?M=E5rten=20Wikstr=F6m?= , "'freebsd-hackers@freebsd.org'" Subject: Re: Routing latency References: <5.0.0.25.0.20010319191529.03fd6a90@mail.etinc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dennis wrote: > [SNIP] > > If you are using the dc driver, make certain it is operating in > store-and-forward mode, the default configuration starts in a mode that > only works on 10mb/s connections. patches ? > > dennis -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 21:47:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 8DBCC37B71C for ; Mon, 19 Mar 2001 21:47:14 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA12411; Tue, 20 Mar 2001 16:15:15 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200103200537.GAA93693@info.iet.unipi.it> Date: Tue, 20 Mar 2001 16:15:15 +1030 (CST) From: "Daniel O'Connor" To: Luigi Rizzo Subject: RE: any decently supported scanner around ? Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Mar-01 Luigi Rizzo wrote: > is there any scanner (USB i presume by now) which is decently > supported by FreeBSD, perhaps something that can be driven > using a command line interface rather than SANE or some > other huge piece of software ? Well, sane does have a command line tool :) I have a HP ScanJet 5400C which works pretty well. Admittedly SANE is pretty big, but I don't think it is intolerably slow.. Network scanning is pretty sexy IMHO :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 22:13:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 4A12E37B71D for ; Mon, 19 Mar 2001 22:13:37 -0800 (PST) (envelope-from dscheidt@tumbolia.com) Received: from shell-2.enteract.com (shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.11.1/8.11.2) with ESMTP id f2K6BjG69141; Tue, 20 Mar 2001 00:11:46 -0600 (CST) (envelope-from dscheidt@tumbolia.com) Date: Tue, 20 Mar 2001 00:11:45 -0600 (CST) From: David Scheidt X-Sender: dscheidt@shell-2.enteract.com To: sean-freebsd-hackers@chittenden.org Cc: freebsd-hackers@freebsd.org Subject: Re: Easy way to compute memory stats? (procfs?) In-Reply-To: <20010319183135.B84536@rand.tgd.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Mar 2001 sean-freebsd-hackers@chittenden.org wrote: : Is there an easy way (from script ideally) to get the following :stats: : :free physical mem (avail ram) This is going to be quite small on any busy machine, or machine that has a reasonable uptime. The VM system will cache things unless there's a demand for memory. vm.stats.vm.v_free_count has the value in it, but quite often will be quite a bit lower than the amount of memory that would be available if the system were under memory pressure. If you look at top's output, there is a value labled cache. The pages in this queue are clean, and can be discarded without needing to write them to backing store. The number the system tells you isn't very useful without knowing what the system is doing. :free swap pstat(8) will tell you this :total avail mem Do you mean physical memory, in which case the value of hw.physmem will tellyou. -- dscheidt@tumbolia.com Bipedalism is only a fad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 22:33:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.tgd.net (rand.tgd.net [64.81.67.117]) by hub.freebsd.org (Postfix) with SMTP id 9DFB737B728 for ; Mon, 19 Mar 2001 22:33:14 -0800 (PST) (envelope-from sean@mailhost.tgd.net) Received: (qmail 85286 invoked by uid 1001); 20 Mar 2001 06:33:03 -0000 Date: Mon, 19 Mar 2001 22:33:03 -0800 From: sean-freebsd-hackers@chittenden.org To: David Scheidt Cc: freebsd-hackers@freebsd.org Subject: Re: Easy way to compute memory stats? (procfs?) Message-ID: <20010319223303.K84536@rand.tgd.net> References: <20010319183135.B84536@rand.tgd.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="81JctsDUVPekGcy+" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from "dscheidt@tumbolia.com" on Tue, Mar 20, 2001 at = 12:11:45AM X-PGP-Key: 0x1EDDFAAD X-PGP-Fingerprint: C665 A17F 9A56 286C 5CFB 1DEA 9F4F 5CEF 1EDD FAAD X-Web-Homepage: http://sean.chittenden.org/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --81JctsDUVPekGcy+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > : Is there an easy way (from script ideally) to get the following > :stats: > : > :free physical mem (avail ram) >=20 > This is going to be quite small on any busy machine, or machine that > has a reasonable uptime. The VM system will cache things unless > there's a demand for memory. vm.stats.vm.v_free_count has the value > in it, but quite often will be quite a bit lower than the amount of > memory that would be available if the system were under memory > pressure. If you look at top's output, there is a value labled > cache. The pages in this queue are clean, and can be discarded > without needing to write them to backing store. The number the > system tells you isn't very useful without knowing what the system > is doing. Drat. I was hoping to arrive at a number similar to top's Free column. Right now the vm stat from sysctl is about 25% of what top's reporting (256MB physical). At the same time... the free pages may be a good value for me to toss around given that I'm also including the load and some statistics of the host's past. > :free swap >=20 > pstat(8) will tell you this Duh, thanks. > :total avail mem >=20 > Do you mean physical memory, in which case the value of hw.physmem will > tellyou. =20 Phys mem + swap, which I think I can calc pretty easily now that I have swap. -sc --=20 Sean Chittenden sean@chittenden.org --81JctsDUVPekGcy+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: For info see http://www.gnupg.org iEYEARECAAYFAjq2+Z8ACgkQn09c7x7d+q0cqgCffzZ2WFOVZvtgG0owL2FZ9ZKS nxIAn2VM+D9RPW6o6h6fnDM8B7WYokLn =u8t3 -----END PGP SIGNATURE----- --81JctsDUVPekGcy+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 23: 4:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from list.framfab.se (list.framfab.se [195.54.96.202]) by hub.freebsd.org (Postfix) with ESMTP id 7C39337B718 for ; Mon, 19 Mar 2001 23:04:48 -0800 (PST) (envelope-from Marten.Wikstrom@framfab.se) Received: from stoent001.framfab.se (mail.sto.framfab.se [172.16.200.241]) by list.framfab.se (8.9.3/8.9.3) with ESMTP id IAA06398; Tue, 20 Mar 2001 08:58:10 +0100 Received: by STOENT001 with Internet Mail Service (5.5.2653.19) id ; Tue, 20 Mar 2001 08:04:38 +0100 Message-ID: From: =?iso-8859-1?Q?M=E5rten_Wikstr=F6m?= To: "'Dennis'" Cc: "'freebsd-hackers@freebsd.org'" Subject: RE: Routing latency Date: Tue, 20 Mar 2001 08:04:27 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snip] > >triggers every second and steals too much cpu. So my=20 > question is, how can I > >decrease this routing delay? > Were you loading the interface, or just passing nominal=20 > streams? What pps=20 > did you pass through the box? Most likely the "delays" are=20 > only seen when=20 > the machine is close to capacity (the slow CPU you are using=20 > doesnt help). I sent 20000 packets/s, three UDP streams with 60, 200 and 1000 bytes = sized packets respectively. I also tried just one stream with 60 bytes = packets and the same behaviour occured. > Latency under load and general latency are very different. Differing=20 > methods of handling backup conditions may have different=20 > goals; the proper=20 > goal is overall stability and NOT packet efficiency. It=20 > doesnt matter how=20 > fast a man runs if he doesnt finish the race. =20 > The problem with LINUX is that it works to a point and then=20 > chokes, while=20 > freebsd works up to higher thresholds. You cant evaluate a=20 > subsystem with=20 > one somewhat bogus test, without looking at the system as a whole. Yep, that is exactly what my test showed when I tested the packet = throughput capacity. Linux choked at 27000 pps and then the output rate = _decreased_ with higher input rate, whereas the FreeBSD box started to drop packets = at 19000 packets/s but the throughput did still increase up untill approximately 40000 pps. (output rate). The input rate was then 70000 = pps. > If you are using the dc driver, make certain it is operating in=20 > store-and-forward mode, the default configuration starts in a=20 > mode that=20 > only works on 10mb/s connections. I'm using the de driver. Alas, the NICs seems quite old. They are = 21140's. I've only got one 21143. I think there is a 3COM 3c905b in the lab too. Would it be better to use the 21143 + 3com than two 21140s? /M=E5rten To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 23:33:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from herbelot.dyndns.org (s014.dhcp212-24.cybercable.fr [212.198.24.14]) by hub.freebsd.org (Postfix) with ESMTP id 79C1437B718 for ; Mon, 19 Mar 2001 23:33:28 -0800 (PST) (envelope-from thierry@herbelot.com) Received: from herbelot.com (multi.herbelot.nom [192.168.1.2]) by herbelot.dyndns.org (8.9.3/8.9.3) with ESMTP id IAA62581; Tue, 20 Mar 2001 08:32:10 +0100 (CET) (envelope-from thierry@herbelot.com) Message-ID: <3AB7077A.543522F0@herbelot.com> Date: Tue, 20 Mar 2001 08:32:10 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: =?iso-8859-1?Q?M=E5rten=20Wikstr=F6m?= Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: Routing latency References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mårten Wikström wrote: > [SNIP] > > I'm using the de driver. Alas, the NICs seems quite old. They are 21140's. > I've only got one 21143. I think there is a 3COM 3c905b in the lab too. > Would it be better to use the 21143 + 3com than two 21140s? definitely : in my packet blaster, I get an order of magnitude less packet drops with a 3c905 than with a dc NIC (which is on a multi-port NIC : the PCI-PCI bridge may be a hindrance there) TfH > > /Mårten -- Thierry Herbelot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Mar 19 23:44:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 1D0B637B718 for ; Mon, 19 Mar 2001 23:44:45 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id IAA94631; Tue, 20 Mar 2001 08:43:46 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103200743.IAA94631@info.iet.unipi.it> Subject: Re: Routing latency In-Reply-To: <3AB7077A.543522F0@herbelot.com> from Thierry Herbelot at "Mar 20, 2001 08:32:10 am" To: Thierry Herbelot Date: Tue, 20 Mar 2001 08:43:45 +0100 (CET) Cc: "[M_rten Wikstr_m]" , "'freebsd-hackers@freebsd.org'" X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm using the de driver. Alas, the NICs seems quite old. They are 21140's. > > I've only got one 21143. I think there is a 3COM 3c905b in the lab too. > > Would it be better to use the 21143 + 3com than two 21140s? > > definitely : in my packet blaster, I get an order of magnitude less > packet drops with a 3c905 than with a dc NIC (which is on a multi-port > NIC : the PCI-PCI bridge may be a hindrance there) not my experience -- with the 21143 i can blast 140kpacket/s and receive them with no problems. For sure the "de" driver might have its own problems, but i think a lot of packet drops also depend on the card not being properly set for full duplex (which can cause collisions and lots of drops). cheers luigi > TfH > > > > /M_rten > > -- > Thierry Herbelot > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 0: 6:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id E0F0737B729 for ; Tue, 20 Mar 2001 00:06:14 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2K84hg15939; Tue, 20 Mar 2001 00:04:44 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103200804.f2K84hg15939@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: sean-freebsd-hackers@chittenden.org Cc: David Scheidt , freebsd-hackers@freebsd.org Subject: Re: Easy way to compute memory stats? (procfs?) In-reply-to: Your message of "Mon, 19 Mar 2001 22:33:03 PST." <20010319223303.K84536@rand.tgd.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Mar 2001 00:04:43 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > :total avail mem > > > > Do you mean physical memory, in which case the value of hw.physmem will > > tellyou. > > Phys mem + swap, which I think I can calc pretty easily now > that I have swap. -sc That's not actually a useful number either. 8) Bear in mind, for example, that program text segments are effectively backed by their on-disk file, so whilst they're paged into memory while being executed, they don't occupy swap so they wouldn't "use memory" in the case you're looking at. A lot of programs also mmap various things which results in these things being paged into memory while being touched, but not being backed by swap. The real bottom line here is simply that you can't look at a FreeBSD system and think of the way it uses memory as though it were a DOS system; it just doesn't work like that, and you need to adjust the way think accordingly. Not to say that you can't measure the things you want to measure, just that you have to use different numbers to do so. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 0:49:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id 12FA837B719; Tue, 20 Mar 2001 00:49:27 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id f2K8llk51871; Tue, 20 Mar 2001 09:47:47 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.2/8.11.0) id f2K8lbE23892; Tue, 20 Mar 2001 09:47:37 +0100 (CET) (envelope-from asmodai) Date: Tue, 20 Mar 2001 09:47:37 +0100 From: Jeroen Ruigrok/Asmodai To: Gurpratap Virdi Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Debuging kernel crashes Message-ID: <20010320094737.A22505@daemon.ninth-circle.org> Reply-To: freebsd-hackers@FreeBSD.ORG References: <20010320055052.20711.qmail@venus.postmark.net> <20010319213936.F29888@fw.wintelcom.net> <001101c0b102$977d8310$050101c0@dhgfhcpps5nhe1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <001101c0b102$977d8310$050101c0@dhgfhcpps5nhe1>; from gvirdi@gvirdi.com on Mon, Mar 19, 2001 at 11:57:03PM -0600 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moved to hackers, since it is more appropriate there than in -net] [net bcc:'d] -On [20010320 07:00], Gurpratap Virdi (gvirdi@gvirdi.com) wrote: >I modified the FreeBSD 4.2 kernel and occasionally the kernel crashes. How >can I determine the line of code that caused the crash? I tried addr2line >with the fault address but that didn't work. Thanks in advance!! Please see http://www.freebsd.org/handbook/kerneldebug.html If you find any problems with that let us know in -doc and we'll fix the docs. -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Sweet taste of vindication, It turns to ashes in your mouth... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 8:13:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from amsmta05-svc.chello.nl (mail-out.chello.nl [213.46.240.7]) by hub.freebsd.org (Postfix) with ESMTP id 997FD37B718 for ; Tue, 20 Mar 2001 08:13:50 -0800 (PST) (envelope-from wvengen@stack.nl) Received: from stack.nl ([213.46.110.240]) by amsmta05-svc.chello.nl (InterMail vK.4.03.02.00 201-232-124 license 9a0f3c09abb1b740b3b0b1917e20d81c) with ESMTP id <20010320155348.NRQN6194.amsmta05-svc@stack.nl> for ; Tue, 20 Mar 2001 16:53:48 +0100 Message-ID: <3AB77C31.8213C158@stack.nl> Date: Tue, 20 Mar 2001 16:50:09 +0100 From: Willem van Engen X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: driver: probe not called when smbus child Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to write a module which should be a child of the smbus. When I make the driver a child of the isa bus, identify, probe, and attach functions are properly called. I use the following code to do that: DRIVER_MODULE(my, isa, my_driver, my_devclass, 0, 0); But when I put it on the smbus using DRIVER_MODULE(my, smbus, my_driver, my_devclass, 0, 0); only identify is called. The identify function is as follows: static void my_identify(driver_t *driver, device_t parent) { devclass_t dc; device_t child; printf("my: my_identify called\n"); dc = devclass_find("my"); if (devclass_get_device(dc, 0)==NULL) { child = BUS_ADD_CHILD(parent, 0, "my", -1); } } The driver only uses smbus calls, so I think the best parent would be smbus. And when I do a smbus_request_bus, the call waits forever as it seems. That seems sensible to me, because it asks the parent for the bus and the isa bus can't grant requests for the smbus. So I think the driver has to be a child of the smbus. Looking in the kernel sources, I see that the only smbus child I can find, smb, (if there are others, I'm certainly interested) is attached in the smbus code itself. So the next question rises: Is it possible to have an smbus child in a dynamically loadable module (I can't find smbus.ko in /modules, so loading the child first and then smbus isn't an option I guess) ? - Willem van Engen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 8:29:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 03AE937B718 for ; Tue, 20 Mar 2001 08:29:48 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id LAA06987 for ; Tue, 20 Mar 2001 11:30:43 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010320114353.03bbc6f0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Tue, 20 Mar 2001 11:46:15 -0500 To: hackers@FreeBSD.ORG From: Dennis Subject: Re: Routing latency In-Reply-To: <200103200743.IAA94631@info.iet.unipi.it> References: <3AB7077A.543522F0@herbelot.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:43 AM 03/20/2001, you wrote: > > > I'm using the de driver. Alas, the NICs seems quite old. They are > 21140's. > > > I've only got one 21143. I think there is a 3COM 3c905b in the lab too. > > > Would it be better to use the 21143 + 3com than two 21140s? > > > > definitely : in my packet blaster, I get an order of magnitude less > > packet drops with a 3c905 than with a dc NIC (which is on a multi-port > > NIC : the PCI-PCI bridge may be a hindrance there) > >not my experience -- with the 21143 i can blast 140kpacket/s >and receive them with no problems. >For sure the "de" driver might have its own problems, >but i think a lot of packet drops also depend on the card >not being properly set for full duplex (which can >cause collisions and lots of drops). You should initially test mono-directional in a controlled environment to avoid "collisions" to compare the true efficiency of the driver. dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 8:34:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id ACDA537B719 for ; Tue, 20 Mar 2001 08:34:33 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id LAA07017; Tue, 20 Mar 2001 11:35:22 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010320114644.01e961c0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Tue, 20 Mar 2001 11:50:53 -0500 To: =?iso-8859-1?Q?M=E5rten?= =?iso-8859-1?Q?_Wikstr=F6m?= From: Dennis Subject: RE: Routing latency Cc: "'freebsd-hackers@freebsd.org'" In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:04 AM 03/20/2001, M=E5rten Wikstr=F6m wrote: >[snip] > > >triggers every second and steals too much cpu. So my > > question is, how can I > > >decrease this routing delay? > > Were you loading the interface, or just passing nominal > > streams? What pps > > did you pass through the box? Most likely the "delays" are > > only seen when > > the machine is close to capacity (the slow CPU you are using > > doesnt help). > >I sent 20000 packets/s, three UDP streams with 60, 200 and 1000 bytes sized >packets respectively. I also tried just one stream with 60 bytes packets= and >the same behaviour occured. 20k pps is probably beyond the capacity of a 200Mhz PPRO machine to forward= =20 on an ongoing basis (ie if other processes are running at the machine). the way the machine behaves over capacity is not as important as its=20 abiltiy to continue running. How it works during normal operations its what= =20 is important. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 8:38:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from list.framfab.se (list.framfab.se [195.54.96.202]) by hub.freebsd.org (Postfix) with ESMTP id C2CDF37B719 for ; Tue, 20 Mar 2001 08:38:12 -0800 (PST) (envelope-from Marten.Wikstrom@framfab.se) Received: from stoent001.framfab.se (mail.sto.framfab.se [172.16.200.241]) by list.framfab.se (8.9.3/8.9.3) with ESMTP id SAA24465; Tue, 20 Mar 2001 18:31:31 +0100 Received: by STOENT001 with Internet Mail Service (5.5.2653.19) id ; Tue, 20 Mar 2001 17:38:00 +0100 Message-ID: From: =?iso-8859-1?Q?M=E5rten_Wikstr=F6m?= To: "'Dennis'" , hackers@FreeBSD.ORG Subject: RE: Routing latency Date: Tue, 20 Mar 2001 17:37:58 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snip] > >For sure the "de" driver might have its own problems, > >but i think a lot of packet drops also depend on the card > >not being properly set for full duplex (which can > >cause collisions and lots of drops). >=20 >=20 > You should initially test mono-directional in a controlled=20 > environment to=20 > avoid "collisions" to compare the true efficiency of the driver. Yes, that is what I have tested. One card just receiving and one card = just outputting. Thats why I thought it would be good to have two identical cards. But the question is, will there be a significant improvement by using = 3c905 + 21143 instead of 21140 + 21140? /M=E5rten To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 9: 6: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id D685937B719 for ; Tue, 20 Mar 2001 09:06:01 -0800 (PST) (envelope-from dscheidt@tumbolia.com) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.11.1/8.11.2) with ESMTP id f2KH5tG40547; Tue, 20 Mar 2001 11:05:55 -0600 (CST) (envelope-from dscheidt@tumbolia.com) Date: Tue, 20 Mar 2001 11:05:54 -0600 (CST) From: David Scheidt X-Sender: dscheidt@shell-2.enteract.com To: sean-freebsd-hackers@chittenden.org Cc: freebsd-hackers@freebsd.org Subject: Re: Easy way to compute memory stats? (procfs?) In-Reply-To: <20010319223303.K84536@rand.tgd.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 19 Mar 2001 sean-freebsd-hackers@chittenden.org wrote: :> : Is there an easy way (from script ideally) to get the following :> :stats: :> : :> :free physical mem (avail ram) :> :> has a reasonable uptime. The VM system will cache things unless :> there's a demand for memory. vm.stats.vm.v_free_count has the value : : Drat. I was hoping to arrive at a number similar to top's :Free column. Right now the vm stat from sysctl is about 25% of what :top's reporting (256MB physical). At the same time... the free pages :may be a good value for me to toss around given that I'm also :including the load and some statistics of the host's past. The sysctl MIB vm.stats.vm.v_free_count has the same value as top's Free Column. (In pages) It's just not a very useful number. The machine I'm sitting at has 213 pages free, but it's not in any danger of running out of memory. The only times there will be lots of free memory are at system startup, when the memory has never been used, and if a large process exits, freeing its memory. (Quiting Netscape brought my free pages to 13139) : :> :free swap :> :> pstat(8) will tell you this : : Duh, thanks. : :> :total avail mem :> :> Do you mean physical memory, in which case the value of hw.physmem will :> tellyou. : : Phys mem + swap, which I think I can calc pretty easily now :that I have swap. -sc Well, not all memory is swapable, nor is all memory swap backed. Exectuable text sections are backed by the disk file, as it's much faster to just throw them away, reading them from disk if they're needed again, then it is to write them to swap and read them back from there. The same thing is true of files that have been mmaped -- the memory used is backed by the disk file, not swap. The available memory is higher than physical memory + swap. The usable memory is often less than physical memory + swap, as well. This box has 256MB RAM, and 756MB swap. Most of the time, if swap is being touched at all, there's something broken, and the machine is not very useable. However, if I've got something like a huge Netscape process, that's idle, and then start working with something else that uses masses of memory, the idle Netscape can get swapped out, and have 150MB of swapped used, and a box that is its normal zippy self. -- dscheidt@tumbolia.com Bipedalism is only a fad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 9: 7: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from vetnet5.vetorialnet.com.br (vetnet5.vetorialnet.com.br [200.248.179.9]) by hub.freebsd.org (Postfix) with ESMTP id ABCD337B719 for ; Tue, 20 Mar 2001 09:07:01 -0800 (PST) (envelope-from thiago_vet@vetnet5.vetorialnet.com.br) Received: from localhost (thiago_vet@localhost) by vetnet5.vetorialnet.com.br (8.11.1/8.11.1) with ESMTP id f2KH9UI37164 for ; Tue, 20 Mar 2001 14:09:31 -0300 (BRT) (envelope-from thiago_vet@vetnet5.vetorialnet.com.br) Date: Tue, 20 Mar 2001 14:09:30 -0300 (BRT) From: Thiago Pinto Damas To: freebsd-hackers@freebsd.org Subject: kernel panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look!! GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... IdlePTD 2736128 initial pcb at 223580 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0xb1c06500 fault code = supervisor read, page not present instruction pointer = 0x8:0xc014ba0c stack pointer = 0x10:0xc020a29c frame pointer = 0x10:0xc020a2a8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle current process = Idle interrupt mask = net trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc019134c stack pointer = 0x10:0xc020a0d0 frame pointer = 0x10:0xc020a0d4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net bio cam trap number = 12 panic: page fault Uptime: 14h24m50s dumping to dev #ad/0x20001, offset 542752 dump ata0: resetting devices .. done 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 --- #0 0xc0130bee in dumpsys () (kgdb) What is it?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 9:11:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 3D78437B71C; Tue, 20 Mar 2001 09:11:45 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id 6A9ED59283; Tue, 20 Mar 2001 11:11:44 -0600 (CST) Date: Tue, 20 Mar 2001 11:11:44 -0600 From: "Michael C . Wu" To: dillon@freebsd.org, grog@freebsd.org, fs@freebsd.org, hackers@freebsd.org Subject: tuning a VERY heavily (30.0) loaded server Message-ID: <20010320111144.A51924@peorth.iteration.net> Reply-To: "Michael C . Wu" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Lengthy email, bear with me please, it is quite interesting. This box averages 30.0 load with no problems.] system stats at http://zoo.ee.ntu.edu.tw/~keichii/ Hello Everyone, I have a friend who admins a very heavily loaded BBS server. (In Taiwan, BBS'es are still very popular, because they are the primary form of scholastic communication in colleges/universities. And FreeBSD runs on most of the university systems in Taiwan ;) ) This box is rather a FreeBSD advocacate itself, as you will see why. It runs an self-wrote PERL SMTP daemon. (Sendmail and Postfix croaks) SMTPD pipes the mail to "bbsmail" that delivers the mail to BBS users. SMTPd averages about BBSd averages about 3000 users at any given time of the day, Peak usage is about 4300 users before the box dies. Each user averages 4-5KB/sec bandwidth. BBSd is an in-house modification of a popular BBSD in Taiwan. There is an innd backend to BBSd that gets a full feed of tw.bbs.* and many other local newsgroups. Average file size is about 4K. /home/bbsusers* is on a vinum stripe'd volume with 3 Ultra160 9G 10000RPM drives on sym0 at stripe size 256K, Greg: I know this should be a prime number, can we safely use <150K stripe sizes? CPU time is not a problem. The other parts of the system rest on 3*Ultra160 9g 10K RPM on AHC0 at stripe size 256K. Physical memory is 2.5 GB. We do MFS and it croaks/crashes at midnight, our peak load time. We do md0, it croaks before peak time. Dual PIII-750 CPU's Due to the structure of BBS's, we cannot split the load across different servers. We also think that we probably cannot get more performance out of hardware upgrades that we can afford. (i.e. Please don't tell us to buy a Starfire 4500 :-) We are all volunteer werkers at El Cheapo university budgets.) We average around 30.0 server load with no noticeable delays for users. Peak load is up to 50.0. Average process count is around 4000 to 5000. We have followed Alfred's advice to do sysctl -w vfs.vmioenable=1 It allows us to survive the peak load a little longer than before. And we are putting our logs of sockstat, iostat 5, vmstat 5, netstat 5, dmesg, uname -a on the following URL. http://zoo.ee.ntu.edu.tw/~keichii/ *DRUM ROLL* What do you think we can do to make this server survive the peak load of around 5000 users? :) * How should we setup our IPFW? * What should be the optimal newfs and tunefs configurations for our filesystems? * What should we try as vinum stripe sizes? * What is possibly the bottleneck that we have for load 30.0? (since we are not CPU-bound nor memory bound) * Is there any VM tweaks that we can do? * Anything else we can do? Thanks, Michael -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 9:15:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id F00C037B720 for ; Tue, 20 Mar 2001 09:15:22 -0800 (PST) (envelope-from roam@orbitel.bg) Received: (qmail 25656 invoked by uid 1000); 20 Mar 2001 17:14:35 -0000 Date: Tue, 20 Mar 2001 19:14:35 +0200 From: Peter Pentchev To: Thiago Pinto Damas Cc: freebsd-hackers@freebsd.org Subject: Re: kernel panic Message-ID: <20010320191434.C21416@ringworld.oblivion.bg> Mail-Followup-To: Thiago Pinto Damas , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from thiago_vet@vetnet5.vetorialnet.com.br on Tue, Mar 20, 2001 at 02:09:30PM -0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You could take a look at www.FreeBSD.org/handbook/kerneldebug.html and provide a bit more details about that crash; at the very least, a 'where' or 'bt' would be useful. After we've seen the 'where' results, it would be easier to isolate the function that caused the panic; then you could use 'up' and 'info locals' to gather more info about the offending function. G'luck, Peter -- When you are not looking at it, this sentence is in Spanish. On Tue, Mar 20, 2001 at 02:09:30PM -0300, Thiago Pinto Damas wrote: > Look!! > GNU gdb 4.18 > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i386-unknown-freebsd"... > (no debugging symbols found)... > IdlePTD 2736128 > initial pcb at 223580 > panicstr: page fault > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xb1c06500 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc014ba0c > stack pointer = 0x10:0xc020a29c > frame pointer = 0x10:0xc020a2a8 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = Idle > current process = Idle > interrupt mask = net > trap number = 12 > panic: page fault > > syncing disks... > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x30 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc019134c > stack pointer = 0x10:0xc020a0d0 > frame pointer = 0x10:0xc020a0d4 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = Idle > interrupt mask = net bio cam > trap number = 12 > panic: page fault > Uptime: 14h24m50s > > dumping to dev #ad/0x20001, offset 542752 > dump ata0: resetting devices .. done > 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 > 236 235 > --- > #0 0xc0130bee in dumpsys () > (kgdb) > > > > What is it?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 9:22:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 10FEF37B728; Tue, 20 Mar 2001 09:22:41 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id 76F3B59283; Tue, 20 Mar 2001 11:22:40 -0600 (CST) Date: Tue, 20 Mar 2001 11:22:40 -0600 From: "Michael C . Wu" To: izero@ms26.hinet.net Cc: dillon@freebsd.org, grog@freebsd.org, fs@freebsd.org, hackers@freebsd.org Subject: Re: tuning a VERY heavily (30.0) loaded server Message-ID: <20010320112239.A52424@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20010320111144.A51924@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010320111144.A51924@peorth.iteration.net>; from keichii@iteration.net on Tue, Mar 20, 2001 at 11:11:44AM -0600 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 11:11:44AM -0600, Michael C . Wu scribbled: | system stats at | http://zoo.ee.ntu.edu.tw/~keichii/ | It runs an self-wrote PERL SMTP daemon. (Sendmail and Postfix croaks) | SMTPD pipes the mail to "bbsmail" that delivers the mail to | BBS users. SMTPd averages about $ mailq |wc -l 2694 $ gzcat maillog.0.gz |wc -l 14407 $ gzcat maillog.2.gz |wc -l 52413 -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 9:27:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4942337B729; Tue, 20 Mar 2001 09:27:19 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2KHRHg21496; Tue, 20 Mar 2001 09:27:17 -0800 (PST) Date: Tue, 20 Mar 2001 09:27:17 -0800 From: Alfred Perlstein To: "Michael C . Wu" Cc: dillon@FreeBSD.ORG, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server Message-ID: <20010320092717.R29888@fw.wintelcom.net> References: <20010320111144.A51924@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010320111144.A51924@peorth.iteration.net>; from keichii@iteration.net on Tue, Mar 20, 2001 at 11:11:44AM -0600 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Michael C . Wu [010320 09:11] wrote: > [Lengthy email, bear with me please, it is quite interesting. > This box averages 30.0 load with no problems.] cool.. > system stats at > http://zoo.ee.ntu.edu.tw/~keichii/ Where's the crashdump/traceback? > Physical memory is 2.5 GB. We do MFS and it croaks/crashes > at midnight, our peak load time. We do md0, it croaks before > peak time. Explain the crash. What is md0/MFS being used for? Why do you need it? > Due to the structure of BBS's, we cannot split the load across > different servers. We also think that we probably cannot > get more performance out of hardware upgrades that we can afford. > (i.e. Please don't tell us to buy a Starfire 4500 :-) We are all volunteer > werkers at El Cheapo university budgets.) Well, getting hardware RAID is always a nice thing and really not too expensive. > We have followed Alfred's advice to do sysctl -w vfs.vmioenable=1 > It allows us to survive the peak load a little longer than before. cool.. > And we are putting our logs of sockstat, iostat 5, vmstat 5, > netstat 5, dmesg, uname -a on the following URL. > > http://zoo.ee.ntu.edu.tw/~keichii/ > > *DRUM ROLL* > What do you think we can do to make this server survive the > peak load of around 5000 users? :) > [snip several non-interesting ideas] > * Anything else we can do? Well first off, telling us which version of FreeBSD this is... Second, provide a crashdump with debug symbols, and show us the backtrace. Third, consider alternatives to MFS since it seems to be a key factor in your stability problems. If you just need a pretty fast /tmp, I would use a softupdates partition as it's probably more effecient than MFS/MD. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 9:28:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 9288937B72E for ; Tue, 20 Mar 2001 09:28:44 -0800 (PST) (envelope-from dscheidt@tumbolia.com) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.11.1/8.11.2) with ESMTP id f2KHSdG51179; Tue, 20 Mar 2001 11:28:43 -0600 (CST) (envelope-from dscheidt@tumbolia.com) Date: Tue, 20 Mar 2001 11:28:38 -0600 (CST) From: David Scheidt X-Sender: dscheidt@shell-2.enteract.com To: "Michael C . Wu" Cc: hackers@freebsd.org Subject: Re: tuning a VERY heavily (30.0) loaded server In-Reply-To: <20010320111144.A51924@peorth.iteration.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Mar 2001, Michael C . Wu wrote: : :This box is rather a FreeBSD advocacate itself, as you will see why. Indeed. : :It runs an self-wrote PERL SMTP daemon. (Sendmail and Postfix croaks) How do sendmail and postfix croak? How much mail are you transporting? If you really can't use one of them, why write a replacement in perl? : :* What is possibly the bottleneck that we have for load 30.0? : (since we are not CPU-bound nor memory bound) You're probably blocked on disk IO. David -- dscheidt@tumbolia.com Bipedalism is only a fad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 9:38:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 44B2F37B734; Tue, 20 Mar 2001 09:38:24 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id EE4CA59283; Tue, 20 Mar 2001 11:38:18 -0600 (CST) Date: Tue, 20 Mar 2001 11:38:18 -0600 From: "Michael C . Wu" To: Alfred Perlstein Cc: "Michael C . Wu" , dillon@FreeBSD.ORG, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server Message-ID: <20010320113818.B52586@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010320092717.R29888@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Mar 20, 2001 at 09:27:17AM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 09:27:17AM -0800, Alfred Perlstein scribbled: | * Michael C . Wu [010320 09:11] wrote: | > [Lengthy email, bear with me please, it is quite interesting. | > This box averages 30.0 load with no problems.] | | cool.. | FreeBSD zoo.ee.ntu.edu.tw 4.2-STABLE FreeBSD 4.2-STABLE #0: Tue Mar 20 11:10:46 CST 2001 root@:/usr/src/sys/compile/SimFarm i386 | > system stats at | > http://zoo.ee.ntu.edu.tw/~keichii/ | | Where's the crashdump/traceback? I'll try to get one tomorrow night, It always crashes. :) It's quite hard trying to get a crashdump when you are 15000miles away from the console. | > Physical memory is 2.5 GB. We do MFS and it croaks/crashes | > at midnight, our peak load time. We do md0, it croaks before | > peak time. | | Explain the crash. What is md0/MFS being used for? Why do you | need it? md0/MFS is used for caching the articles that BBS users read. They often read the same articles over and over again, and we find that a 128MB MFS/md0 will have 70% hitrate When our MFS/md0 fills up after long usage, the box easily dies. (We crontab clean the mfs, but sometimes the load shoots up for no reason and is not able to clean the mfs in time.) If we dont do this cache, the data for the bulletin boards | > Due to the structure of BBS's, we cannot split the load across | > different servers. We also think that we probably cannot | > get more performance out of hardware upgrades that we can afford. | > (i.e. Please don't tell us to buy a Starfire 4500 :-) We are all volunteer | > werkers at El Cheapo university budgets.) | | Well, getting hardware RAID is always a nice thing and really not | too expensive. I looked into that, it seems that hardware RAID will have less performance due to hw raid cards' onboard CPU bounding it. | > We have followed Alfred's advice to do sysctl -w vfs.vmioenable=1 | > It allows us to survive the peak load a little longer than before. | | cool.. | | > And we are putting our logs of sockstat, iostat 5, vmstat 5, | > netstat 5, dmesg, uname -a on the following URL. | > | > http://zoo.ee.ntu.edu.tw/~keichii/ | > * Anything else we can do? | | Well first off, telling us which version of FreeBSD this is... | FreeBSD zoo.ee.ntu.edu.tw 4.2-STABLE FreeBSD 4.2-STABLE #0: Tue Mar 20 11:10:46 CST 2001 root@:/usr/src/sys/compile/SimFarm i386 | Second, provide a crashdump with debug symbols, and show us | the backtrace. | | Third, consider alternatives to MFS since it seems to be a key | factor in your stability problems. If you just need a pretty | fast /tmp, I would use a softupdates partition as it's probably | more effecient than MFS/MD. The harddrives will die very quickly if we don't have MFS... -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 9:49:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id D0B1D37B740; Tue, 20 Mar 2001 09:49:21 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ted.isi.edu (ted.isi.edu [128.9.160.104]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f2KHnK520704; Tue, 20 Mar 2001 09:49:20 -0800 (PST) Received: (from faber@localhost) by ted.isi.edu (8.11.2/8.11.2) id f2KHmls08662; Tue, 20 Mar 2001 09:48:47 -0800 (PST) (envelope-from faber) Date: Tue, 20 Mar 2001 09:48:37 -0800 From: Ted Faber To: "Michael C . Wu" Cc: Alfred Perlstein , "Michael C . Wu" , dillon@FreeBSD.ORG, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server Message-ID: <20010320094837.B1284@ted.isi.edu> References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=php-sha1; protocol="application/pgp-signature"; boundary="BwCQnh7xodEAoBMC" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010320113818.B52586@peorth.iteration.net>; from keichii@iteration.net on Tue, Mar 20, 2001 at 11:38:18AM -0600 X-url: http://www.isi.edu/~faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --BwCQnh7xodEAoBMC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Mar 20, 2001 at 11:38:18AM -0600, Michael C . Wu wrote: > On Tue, Mar 20, 2001 at 09:27:17AM -0800, Alfred Perlstein scribbled: > | * Michael C . Wu [010320 09:11] wrote: > | > Physical memory is 2.5 GB. We do MFS and it croaks/crashes > | > at midnight, our peak load time. We do md0, it croaks before > | > peak time. > | > | Explain the crash. What is md0/MFS being used for? Why do you > | need it? > > md0/MFS is used for caching the articles that BBS users read. > They often read the same articles over and over again, > and we find that a 128MB MFS/md0 will have 70% hitrate > > When our MFS/md0 fills up after long usage, the box easily > dies. (We crontab clean the mfs, but sometimes the load > shoots up for no reason and is not able to clean the mfs in time.) > If we dont do this cache, the data for the bulletin boards Forgive me if this is a stupid question, but how much swap is there on this machine? Is the combination of the packed MFS and high process load exhausting your swap? --BwCQnh7xodEAoBMC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6t5f1aUz3f+Zf+XsRAnKTAKD2KfRmKT5xISmnSw92iVPTxdGTtgCffv16 V6TK3KKHF799LzyDTMhxu7o= =PUFq -----END PGP SIGNATURE----- --BwCQnh7xodEAoBMC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 9:51:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 6F0BD37B740; Tue, 20 Mar 2001 09:51:41 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2KHopk94248; Tue, 20 Mar 2001 09:50:51 -0800 (PST) (envelope-from dillon) Date: Tue, 20 Mar 2001 09:50:51 -0800 (PST) From: Matt Dillon Message-Id: <200103201750.f2KHopk94248@earth.backplane.com> To: "Michael C . Wu" Cc: Alfred Perlstein , "Michael C . Wu" , grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One thing that comes to mind is that you can smarthost your outgoing email to another host so the queues don't build up. This should greatly reduce mail load. In fact, I would recommend offloading email entirely if possible... email always hits disks hard. Definitely get rid of MFS. MFS wastes 2x the memory allocated to it. Use a softupdates-enabled filesystem in place of MFS, or use a swap-backed VN-based partition with softupdates enabled. Alfred's vmiodirenable suggestion is a good one. With all the memory you have you can also try turning off write_behind, e.g. setting vfs.write_behind to 0. I don't have enough information on the type of paging your machine is doing or the disk configuration. If you have multiple HD's, swap should definitely be spread across at least two of them. A few minutes worth of 'vmstat 1' output during the heavily loaded period would be useful, plus 'sysctl -a | fgrep vm'. I might be able to make suggestions on optimizing the VM system. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 9:55:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id C050437B73F; Tue, 20 Mar 2001 09:55:21 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2KHstW94364; Tue, 20 Mar 2001 09:54:55 -0800 (PST) (envelope-from dillon) Date: Tue, 20 Mar 2001 09:54:55 -0800 (PST) From: Matt Dillon Message-Id: <200103201754.f2KHstW94364@earth.backplane.com> To: "Michael C . Wu" Cc: Alfred Perlstein , "Michael C . Wu" , grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :md0/MFS is used for caching the articles that BBS users read. :They often read the same articles over and over again, :and we find that a 128MB MFS/md0 will have 70% hitrate : :When our MFS/md0 fills up after long usage, the box easily :dies. (We crontab clean the mfs, but sometimes the load :shoots up for no reason and is not able to clean the mfs in time.) :If we dont do this cache, the data for the bulletin boards Definitely throw away MFS. A normal filesystem is plenty good enough for caching articles that BBS users read. MFS will just waste memory unnecessarily. It does seem to me that you might not have sufficient swap configured either, as per Ted's thought. With 2.5G of physical memory, You should have *AT LEAST* 3G of configured swap. I would recommend a 1G swap partition on each of your three 9G drives (for 3G total). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10: 2:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 2E40237B73F; Tue, 20 Mar 2001 10:02:26 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id 3E35359283; Tue, 20 Mar 2001 12:01:12 -0600 (CST) Date: Tue, 20 Mar 2001 12:01:12 -0600 From: "Michael C . Wu" To: izero@ms26.hinet.net, cross@math.psu.edu Cc: Alfred Perlstein , "Michael C . Wu" , dillon@FreeBSD.ORG, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded scerver Message-ID: <20010320120112.C52586@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010320113818.B52586@peorth.iteration.net>; from keichii@iteration.net on Tue, Mar 20, 2001 at 11:38:18AM -0600 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG MRTG Graph at http://zoonews.ee.ntu.edu.tw/mrtg/zoo.html | | FreeBSD zoo.ee.ntu.edu.tw 4.2-STABLE FreeBSD 4.2-STABLE | #0: Tue Mar 20 11:10:46 CST 2001 root@:/usr/src/sys/compile/SimFarm i386 | | | > system stats at | | > http://zoo.ee.ntu.edu.tw/~keichii/ | md0/MFS is used for caching the articles that BBS users read. | They often read the same articles over and over again, | and we find that a 128MB MFS/md0 will have 70% hitrate | | When our MFS/md0 fills up after long usage, the box easily | dies. (We crontab clean the mfs, but sometimes the load | shoots up for no reason and is not able to clean the mfs in time.) | If we dont do this cache, the data for the bulletin boards | Another problem is that we have around 4000+ processes accessing lots of SHM at the same time.. The *UGLY* source code for the BBS is at http://zoo.ee.ntu.edu.tw/~keichii/zoo_bbsd_src.tgz We can only provide crash dumps for trusted people because of the thousands of passwords in the dump. -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10: 5:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id E6B0E37B73F; Tue, 20 Mar 2001 10:05:35 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id F01F259283; Tue, 20 Mar 2001 12:03:14 -0600 (CST) Date: Tue, 20 Mar 2001 12:03:14 -0600 From: "Michael C . Wu" To: Ted Faber Cc: fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server Message-ID: <20010320120314.D52586@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320094837.B1284@ted.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010320094837.B1284@ted.isi.edu>; from faber@ISI.EDU on Tue, Mar 20, 2001 at 09:48:37AM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 09:48:37AM -0800, Ted Faber scribbled: | On Tue, Mar 20, 2001 at 11:38:18AM -0600, Michael C . Wu wrote: | > On Tue, Mar 20, 2001 at 09:27:17AM -0800, Alfred Perlstein scribbled: | > | * Michael C . Wu [010320 09:11] wrote: | > | > Physical memory is 2.5 GB. We do MFS and it croaks/crashes | > | > at midnight, our peak load time. We do md0, it croaks before | > | > peak time. | > | | > | Explain the crash. What is md0/MFS being used for? Why do you | > | need it? | > | > md0/MFS is used for caching the articles that BBS users read. | > They often read the same articles over and over again, | > and we find that a 128MB MFS/md0 will have 70% hitrate | > | > When our MFS/md0 fills up after long usage, the box easily | > dies. (We crontab clean the mfs, but sometimes the load | > shoots up for no reason and is not able to clean the mfs in time.) | > If we dont do this cache, the data for the bulletin boards | | Forgive me if this is a stupid question, but how much swap is there on | this machine? Is the combination of the packed MFS and high process | load exhausting your swap? SWAP is never touched. :) last pid: 23395; load averages: 2.08, 2.92, 3.60 up 0+01:29:58 02:03:27 1529 processes:24 running, 1505 sleeping CPU states: 40.5% user, 0.0% nice, 46.4% system, 1.1% interrupt, 12.0% idle Mem: 705M Active, 1369M Inact, 332M Wired, 99M Cache, 265M Buf, 7504K Free Swap: 512M Total, 512M Free -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:12: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 0F33237B718; Tue, 20 Mar 2001 10:11:55 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2KI99W22661; Tue, 20 Mar 2001 10:09:09 -0800 (PST) Date: Tue, 20 Mar 2001 10:09:09 -0800 From: Alfred Perlstein To: "Michael C . Wu" Cc: izero@ms26.hinet.net, cross@math.psu.edu, "Michael C . Wu" , dillon@FreeBSD.ORG, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded scerver Message-ID: <20010320100909.T29888@fw.wintelcom.net> References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320120112.C52586@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010320120112.C52586@peorth.iteration.net>; from keichii@iteration.net on Tue, Mar 20, 2001 at 12:01:12PM -0600 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Michael C . Wu [010320 10:01] wrote: > MRTG Graph at > http://zoonews.ee.ntu.edu.tw/mrtg/zoo.html > > | > | FreeBSD zoo.ee.ntu.edu.tw 4.2-STABLE FreeBSD 4.2-STABLE > | #0: Tue Mar 20 11:10:46 CST 2001 root@:/usr/src/sys/compile/SimFarm i386 > | > | | > system stats at > | | > http://zoo.ee.ntu.edu.tw/~keichii/ > | md0/MFS is used for caching the articles that BBS users read. > | They often read the same articles over and over again, > | and we find that a 128MB MFS/md0 will have 70% hitrate > | > | When our MFS/md0 fills up after long usage, the box easily > | dies. (We crontab clean the mfs, but sometimes the load > | shoots up for no reason and is not able to clean the mfs in time.) > | If we dont do this cache, the data for the bulletin boards > | > > Another problem is that we have around 4000+ processes accessing > lots of SHM at the same time.. How much SHM? Like, what's the combined size of all segments in the system? You can make SHM non-pageable which results in a lot of saved memory for attached processes. You want to be after this date and have this file: Revision 1.3.2.3 / (download) - annotate - [select for diffs], Sun Dec 17 02:05:41 2000 UTC (3 months ago) by alfred Branch: RELENG_4 Changes since 1.3.2.2: +37 -32 lines Diff to previous 1.3.2.2 (colored) to branchpoint 1.3 (colored) next main 1.4 (colored) MFC: phys_pager fix for multiple segments Then set kern.ipc.shm_use_phys=1 > The *UGLY* source code for the BBS is at > http://zoo.ee.ntu.edu.tw/~keichii/zoo_bbsd_src.tgz tis ok, maybe later... though :) > > We can only provide crash dumps for trusted people because > of the thousands of passwords in the dump. Heh. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:19:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 0066637B719; Tue, 20 Mar 2001 10:19:30 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2KIHMx94840; Tue, 20 Mar 2001 10:17:22 -0800 (PST) (envelope-from dillon) Date: Tue, 20 Mar 2001 10:17:22 -0800 (PST) From: Matt Dillon Message-Id: <200103201817.f2KIHMx94840@earth.backplane.com> To: Alfred Perlstein Cc: "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, "Michael C . Wu" , grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded scerver References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320120112.C52586@peorth.iteration.net> <20010320100909.T29888@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :How much SHM? Like, what's the combined size of all segments in :the system? You can make SHM non-pageable which results in a lot :of saved memory for attached processes. : :You want to be after this date and have this file: : : :Revision 1.3.2.3 / (download) - annotate - [select for diffs], Sun Dec 17 02:05:41 2000 UTC (3 months ago) by alfred :Branch: RELENG_4 :Changes since 1.3.2.2: +37 -32 lines :Diff to previous 1.3.2.2 (colored) to branchpoint 1.3 (colored) next main 1.4 (colored) : :MFC: phys_pager fix for multiple segments : :Then set kern.ipc.shm_use_phys=1 We never MFC'd that? After the release we should. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:24:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id C9CB237B718; Tue, 20 Mar 2001 10:24:22 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ted.isi.edu (ted.isi.edu [128.9.160.104]) by boreas.isi.edu (8.11.2/8.11.2) with ESMTP id f2KIM1527394; Tue, 20 Mar 2001 10:22:01 -0800 (PST) Received: (from faber@localhost) by ted.isi.edu (8.11.2/8.11.2) id f2KIM1909090; Tue, 20 Mar 2001 10:22:01 -0800 (PST) (envelope-from faber) Date: Tue, 20 Mar 2001 10:21:56 -0800 From: Ted Faber To: "Michael C . Wu" Cc: fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server Message-ID: <20010320102156.C1284@ted.isi.edu> References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320094837.B1284@ted.isi.edu> <20010320120314.D52586@peorth.iteration.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=php-sha1; protocol="application/pgp-signature"; boundary="ZwgA9U+XZDXt4+m+" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010320120314.D52586@peorth.iteration.net>; from keichii@iteration.net on Tue, Mar 20, 2001 at 12:03:14PM -0600 X-url: http://www.isi.edu/~faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ZwgA9U+XZDXt4+m+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Mar 20, 2001 at 12:03:14PM -0600, Michael C . Wu wrote: > On Tue, Mar 20, 2001 at 09:48:37AM -0800, Ted Faber scribbled: > | Forgive me if this is a stupid question, but how much swap is there on > | this machine? Is the combination of the packed MFS and high process > | load exhausting your swap? > > > SWAP is never touched. :) > > last pid: 23395; load averages: 2.08, 2.92, 3.60 up 0+01:29:58 02:03:27 > 1529 processes:24 running, 1505 sleeping > CPU states: 40.5% user, 0.0% nice, 46.4% system, 1.1% interrupt, 12.0% idle > Mem: 705M Active, 1369M Inact, 332M Wired, 99M Cache, 265M Buf, 7504K Free > Swap: 512M Total, 512M Free A couple other people have mentioned that this is your swap load when the machine's quiet. MFS can exhaust your swap quickly, and if you scale these load numbers up by a factor of 10, I think you're going to touch swap. (Even here you're already down to 7M free mem.) I wouldn't be surprised if you're running out of swap. --ZwgA9U+XZDXt4+m+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6t5/EaUz3f+Zf+XsRAlCNAJsGrpqo0bwQ4UWFZKzu+ZgCb6ROmQCbBFNw h1gZvaVRLZ4fhbGWbCZNJG4= =J9px -----END PGP SIGNATURE----- --ZwgA9U+XZDXt4+m+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:24:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 4281F37B71B; Tue, 20 Mar 2001 10:24:28 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id 780F259283; Tue, 20 Mar 2001 12:21:56 -0600 (CST) Date: Tue, 20 Mar 2001 12:21:56 -0600 From: "Michael C . Wu" To: Alfred Perlstein Cc: izero@ms26.hinet.net, cross@math.psu.edu, "Michael C . Wu" , dillon@FreeBSD.ORG, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded scerver Message-ID: <20010320122156.A53182@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320120112.C52586@peorth.iteration.net> <20010320100909.T29888@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010320100909.T29888@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Mar 20, 2001 at 10:09:09AM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 10:09:09AM -0800, Alfred Perlstein scribbled: | * Michael C . Wu [010320 10:01] wrote: | > MRTG Graph at | > http://zoonews.ee.ntu.edu.tw/mrtg/zoo.html | > | > | | > | FreeBSD zoo.ee.ntu.edu.tw 4.2-STABLE FreeBSD 4.2-STABLE | > | #0: Tue Mar 20 11:10:46 CST 2001 root@:/usr/src/sys/compile/SimFarm i386 | > | | > | | > system stats at | > | | > http://zoo.ee.ntu.edu.tw/~keichii/ | > | md0/MFS is used for caching the articles that BBS users read. | > | They often read the same articles over and over again, | > | and we find that a 128MB MFS/md0 will have 70% hitrate | > | | > | When our MFS/md0 fills up after long usage, the box easily | > | dies. (We crontab clean the mfs, but sometimes the load | > | shoots up for no reason and is not able to clean the mfs in time.) | > | If we dont do this cache, the data for the bulletin boards | > | | > | > Another problem is that we have around 4000+ processes accessing | > lots of SHM at the same time.. | | How much SHM? Like, what's the combined size of all segments in | the system? You can make SHM non-pageable which results in a lot | of saved memory for attached processes. | ipcs -b Shared Memory: T ID KEY MODE OWNER GROUP SEGSZ m 65536 1304 --rw------- bbs bbs 131076 m 65537 1217 --rw------- bbs wheel 1633728 m 65538 1215 --rw------- bbs wheel 768016 m 65539 1219 --rw------- bbs bbs 2065956 m 65540 1111 --rw------- bbs bbs 12 m 65541 1302 --rw------- bbs bbs 40016 m 65542 1303 --rw------- bbs bbs 40016 m 65543 1201 --rw------- bbs bbs 33328 m 65544 1301 --rw------- bbs bbs 33328 VM_KMEM_SIZE_MAX When we raise this variable, the system dies easily, but on a similiarly configured system (bbs.kkcity.com.tw) at similiar load, It helps a lot to keep the system stable. We have a hashd daemon that uses 4300*2 unix domain sockets written in pthreads. There are eight of these daemons each serving about 500 bbsd's. | Revision 1.3.2.3 / (download) - annotate - [select for diffs], Sun Dec 17 02:05:41 2000 UTC (3 months ago) by alfred | Branch: RELENG_4 | Changes since 1.3.2.2: +37 -32 lines | Diff to previous 1.3.2.2 (colored) to branchpoint 1.3 (colored) next main 1.4 (colored) | | MFC: phys_pager fix for multiple segments | | Then set kern.ipc.shm_use_phys=1 O.K. | > The *UGLY* source code for the BBS is at | > http://zoo.ee.ntu.edu.tw/~keichii/zoo_bbsd_src.tgz | | tis ok, maybe later... though :) Someone asked me in private for this. :) -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:24:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id B338E37B71D; Tue, 20 Mar 2001 10:24:31 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id 91F8C59289; Tue, 20 Mar 2001 12:22:45 -0600 (CST) Date: Tue, 20 Mar 2001 12:22:45 -0600 From: "Michael C . Wu" To: Matt Dillon Cc: "Michael C . Wu" , Alfred Perlstein , grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server Message-ID: <20010320122245.E52586@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <200103201750.f2KHopk94248@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103201750.f2KHopk94248@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Mar 20, 2001 at 09:50:51AM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 09:50:51AM -0800, Matt Dillon scribbled: | One thing that comes to mind is that you can smarthost your outgoing | email to another host so the queues don't build up. This should | greatly reduce mail load. In fact, I would recommend offloading email | entirely if possible... email always hits disks hard. | | Definitely get rid of MFS. MFS wastes 2x the memory allocated to it. | Use a softupdates-enabled filesystem in place of MFS, or use a | swap-backed VN-based partition with softupdates enabled. | Alfred's vmiodirenable suggestion is a good one. | | With all the memory you have you can also try turning off write_behind, | e.g. setting vfs.write_behind to 0. done. :) Thank you | I don't have enough information on the type of paging your machine | is doing or the disk configuration. If you have multiple HD's, swap | should definitely be spread across at least two of them. | | A few minutes worth of 'vmstat 1' output during the heavily loaded | period would be useful, plus 'sysctl -a | fgrep vm'. I might be able sysctl -a always crashes the system. It happens on other similiarly loaded BBS'es in Taiwan. | to make suggestions on optimizing the VM system. We have 'vmstat 5' available at http://zoo.ee.ntu.edu.tw/~keichii/ Fresh hot vmstat 1 log at http://zoo.ee.ntu.edu.tw/~keichii/vmstat_1.log -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:25: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 513F337B719; Tue, 20 Mar 2001 10:24:49 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2KIMkg23099; Tue, 20 Mar 2001 10:22:46 -0800 (PST) Date: Tue, 20 Mar 2001 10:22:46 -0800 From: Alfred Perlstein To: Matt Dillon Cc: "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, "Michael C . Wu" , grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded scerver Message-ID: <20010320102246.U29888@fw.wintelcom.net> References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320120112.C52586@peorth.iteration.net> <20010320100909.T29888@fw.wintelcom.net> <200103201817.f2KIHMx94840@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103201817.f2KIHMx94840@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Mar 20, 2001 at 10:17:22AM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [010320 10:17] wrote: > : > :How much SHM? Like, what's the combined size of all segments in > :the system? You can make SHM non-pageable which results in a lot > :of saved memory for attached processes. > : > :You want to be after this date and have this file: > : > : > :Revision 1.3.2.3 / (download) - annotate - [select for diffs], Sun Dec 17 02:05:41 2000 UTC (3 months ago) by alfred > :Branch: RELENG_4 > :Changes since 1.3.2.2: +37 -32 lines > :Diff to previous 1.3.2.2 (colored) to branchpoint 1.3 (colored) next main 1.4 (colored) > : > :MFC: phys_pager fix for multiple segments > : > :Then set kern.ipc.shm_use_phys=1 > > We never MFC'd that? After the release we should. I MFC'd it a long time ago (3 months): > :Branch: RELENG_4 I just wasn't sure if he was up to date with 4.2-stable enough to get it. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:27: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 94F8237B718; Tue, 20 Mar 2001 10:27:03 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id 1DF5A5928B; Tue, 20 Mar 2001 12:23:50 -0600 (CST) Date: Tue, 20 Mar 2001 12:23:50 -0600 From: "Michael C . Wu" To: Matt Dillon Cc: "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, Alfred Perlstein , grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded scerver Message-ID: <20010320122350.F52586@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320120112.C52586@peorth.iteration.net> <200103201815.f2KIFR594803@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103201815.f2KIFR594803@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Mar 20, 2001 at 10:15:27AM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 10:15:27AM -0800, Matt Dillon scribbled: | | :Another problem is that we have around 4000+ processes accessing | :lots of SHM at the same time.. | | How big is 'lots'? If the shared memory segment is smallish, e.g. | less then 64MB, you should be ok. If it is larger then you will | have to do some kernel tuning to avoid running out of pmap entries. This is exactly what happens to us sometimes. We run out of pmap entries. :) But what can we tune? -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:27:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id BF0F537B719; Tue, 20 Mar 2001 10:27:09 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2KINog23123; Tue, 20 Mar 2001 10:23:50 -0800 (PST) Date: Tue, 20 Mar 2001 10:23:50 -0800 From: Alfred Perlstein To: Matt Dillon Cc: "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded scerver Message-ID: <20010320102350.V29888@fw.wintelcom.net> References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320120112.C52586@peorth.iteration.net> <200103201815.f2KIFR594803@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103201815.f2KIFR594803@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Mar 20, 2001 at 10:15:27AM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [010320 10:16] wrote: > > :Another problem is that we have around 4000+ processes accessing > :lots of SHM at the same time.. > > How big is 'lots'? If the shared memory segment is smallish, e.g. > less then 64MB, you should be ok. If it is larger then you will > have to do some kernel tuning to avoid running out of pmap entries. kern.ipc.shm_use_phys should remove the need for pv entries. it's the default on solaris. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:33: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 3E3B137B718; Tue, 20 Mar 2001 10:32:57 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2KITPL23345; Tue, 20 Mar 2001 10:29:25 -0800 (PST) Date: Tue, 20 Mar 2001 10:29:24 -0800 From: Alfred Perlstein To: "Michael C . Wu" Cc: Matt Dillon , "Michael C . Wu" , grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server Message-ID: <20010320102924.X29888@fw.wintelcom.net> References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <200103201750.f2KHopk94248@earth.backplane.com> <20010320122245.E52586@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010320122245.E52586@peorth.iteration.net>; from keichii@iteration.net on Tue, Mar 20, 2001 at 12:22:45PM -0600 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Michael C . Wu [010320 10:27] wrote: > On Tue, Mar 20, 2001 at 09:50:51AM -0800, Matt Dillon scribbled: > > sysctl -a always crashes the system. It happens on other similiarly > loaded BBS'es in Taiwan. WHY ARE THERE NO TRACEBACKS BEING POSTED TO THE LISTS? THIS IS THE WHOLE POINT OF FREEBSD/OPEN-SOURCE. ARE YOU GUYS SO USED TO MICROSOFT THAT YOU DON'T EXPECT US TO CARE ABOUT THIS? WE CARE, WE USE FREEBSD FOR OUR OWN BUSNIESSES. ARGH. THANKS, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:35:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C64F737B71A; Tue, 20 Mar 2001 10:35:14 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2KIVUc23476; Tue, 20 Mar 2001 10:31:30 -0800 (PST) Date: Tue, 20 Mar 2001 10:31:30 -0800 From: Alfred Perlstein To: "Michael C . Wu" Cc: Matt Dillon , "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded scerver Message-ID: <20010320103130.Y29888@fw.wintelcom.net> References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320120112.C52586@peorth.iteration.net> <200103201815.f2KIFR594803@earth.backplane.com> <20010320122350.F52586@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010320122350.F52586@peorth.iteration.net>; from keichii@iteration.net on Tue, Mar 20, 2001 at 12:23:50PM -0600 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Michael C . Wu [010320 10:27] wrote: > On Tue, Mar 20, 2001 at 10:15:27AM -0800, Matt Dillon scribbled: > | > | :Another problem is that we have around 4000+ processes accessing > | :lots of SHM at the same time.. > | > | How big is 'lots'? If the shared memory segment is smallish, e.g. > | less then 64MB, you should be ok. If it is larger then you will > | have to do some kernel tuning to avoid running out of pmap entries. > > This is exactly what happens to us sometimes. We run out of pmap entries. :) > But what can we tune? If this is a result of the shared memory, then my sysctl should fix it. Be aware, that it doesn't fix it on the fly! You must drop and recreate the shared memory segments. better to reboot actually and set the variable before any shm is allocated. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:40:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 8FF3B37B718 for ; Tue, 20 Mar 2001 10:40:46 -0800 (PST) (envelope-from dphoenix@bravenet.com) Received: (qmail 16387 invoked by uid 1000); 20 Mar 2001 18:35:14 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Mar 2001 18:35:14 -0000 Date: Tue, 20 Mar 2001 10:35:14 -0800 (PST) From: Dan Phoenix To: freebsd-hackers@freebsd.org Subject: apache truss readings Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG open("./semcache.inc",0,0666) ERR#2 'No such file or directory' open("/website/include/semcache.inc",0,0666) = 5 (0x5) __getcwd(0xbfbf6b90,0x400) = 0 (0x0) open(".",0,00) = 6 (0x6) chdir(0xbfbf6744) = 0 (0x0) lstat("semcache.inc",0xbfbf6694) = 0 (0x0) __getcwd(0xbfbf6744,0x400) = 0 (0x0) fchdir(0x6) = 0 (0x0) close(6) = 0 (0x0) ioctl(5,TIOCGETA,0xbfbf749c) ERR#25 'Inappropriate ioctl for device' fstat(5,0xbfbf6454) = 0 (0x0) read(0x5,0x8306000,0x2000) = 1043 (0x413) read(0x5,0x8306000,0x2000) = 0 (0x0) ioctl(5,TIOCGETA,0xbfbf64f8) ERR#25 'Inappropriate ioctl for device' close(5) = 0 (0x0) fcntl(0x4,0x4,0x4) = 0 (0x0) read(0x4,0x82fa000,0x2000) ERR#35 'Resource temporarily unavailable' ok first error i understand....a call is being made for ./include instead of real path...whether an extra system call made for an include is really going to make a big diff can;t be to much. What concerns me is ERR#35 'Resource temporarily unavailable'...what could that be from? I do have some nfs for forums but 1)semcache.inc is local on ide drive and second it did not show any other file being opened before that resource issue....ideas? btw what is err#25 from? -- Dan +------------------------------------------------------+ | BRAVENET WEB SERVICES | | dan@bravenet.com | | make installworld | | ln -s /var/qmail/bin/sendmail /usr/sbin/sendmail | | ln -s /var/qmail/bin/newaliases /usr/sbin/newaliases | +______________________________________________________+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:41:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 4D6B237B719; Tue, 20 Mar 2001 10:41:03 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2KIcZP95379; Tue, 20 Mar 2001 10:38:35 -0800 (PST) (envelope-from dillon) Date: Tue, 20 Mar 2001 10:38:35 -0800 (PST) From: Matt Dillon Message-Id: <200103201838.f2KIcZP95379@earth.backplane.com> To: "Michael C . Wu" Cc: izero@ms26.hinet.net, cross@math.psu.edu, Alfred Perlstein , grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded scerver References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320120112.C52586@peorth.iteration.net> <200103201815.f2KIFR594803@earth.backplane.com> <20010320122350.F52586@peorth.iteration.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :| How big is 'lots'? If the shared memory segment is smallish, e.g. :| less then 64MB, you should be ok. If it is larger then you will :| have to do some kernel tuning to avoid running out of pmap entries. : :This is exactly what happens to us sometimes. We run out of pmap entries. :) :But what can we tune? :-- :+-----------------------------------------------------------+ :| keichii@iteration.net | keichii@freebsd.org | What Alfred said: sysctl -w kern.ipc.shm_use_phys=1 (run prior to creating the initial shared memory segment, e.g. when the machine is booted). That should solve the pv entry problem. What Alfred said in regards to 'sysctl -a' crashing too... We'll fix it if you give us a traceback! The kernel config you are using would be useful. It sounds like there are a bunch of things you either need to tune or have already tuned in the kernel configuration. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:43: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth.backplane.com [208.161.114.65]) by hub.freebsd.org (Postfix) with ESMTP id 20FA537B718; Tue, 20 Mar 2001 10:43:01 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2KIFR594803; Tue, 20 Mar 2001 10:15:27 -0800 (PST) (envelope-from dillon) Date: Tue, 20 Mar 2001 10:15:27 -0800 (PST) From: Matt Dillon Message-Id: <200103201815.f2KIFR594803@earth.backplane.com> To: "Michael C . Wu" Cc: izero@ms26.hinet.net, cross@math.psu.edu, Alfred Perlstein , "Michael C . Wu" , grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded scerver References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320120112.C52586@peorth.iteration.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Another problem is that we have around 4000+ processes accessing :lots of SHM at the same time.. How big is 'lots'? If the shared memory segment is smallish, e.g. less then 64MB, you should be ok. If it is larger then you will have to do some kernel tuning to avoid running out of pmap entries. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:47:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 1824A37B71A for ; Tue, 20 Mar 2001 10:47:06 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2KIkgq24009; Tue, 20 Mar 2001 10:46:42 -0800 (PST) Date: Tue, 20 Mar 2001 10:46:42 -0800 From: Alfred Perlstein To: Dan Phoenix Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: apache truss readings Message-ID: <20010320104642.C29888@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from dphoenix@bravenet.com on Tue, Mar 20, 2001 at 10:35:14AM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Dan Phoenix [010320 10:41] wrote: > > btw what is err#25 from? man 2 intro -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:48:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ohm.physics.purdue.edu (ohm.physics.purdue.edu [128.210.146.32]) by hub.freebsd.org (Postfix) with ESMTP id 639F437B718 for ; Tue, 20 Mar 2001 10:48:43 -0800 (PST) (envelope-from will@physics.purdue.edu) Received: (from will@localhost) by ohm.physics.purdue.edu (8.11.2/8.9.3) id f2KIqQn01094; Tue, 20 Mar 2001 13:52:26 -0500 (EST) (envelope-from will@physics.purdue.edu) X-Authentication-Warning: ohm.physics.purdue.edu: will set sender to will@physics.purdue.edu using -f Date: Tue, 20 Mar 2001 13:52:26 -0500 From: Will Andrews To: Luigi Rizzo Cc: hackers@FreeBSD.ORG Subject: Re: any decently supported scanner around ? Message-ID: <20010320135226.E469@ohm.physics.purdue.edu> Reply-To: Will Andrews References: <200103200537.GAA93693@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="FEz7ebHBGB6b2e8X" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103200537.GAA93693@info.iet.unipi.it>; from luigi@info.iet.unipi.it on Tue, Mar 20, 2001 at 06:37:57AM +0100 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --FEz7ebHBGB6b2e8X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Mar 20, 2001 at 06:37:57AM +0100, Luigi Rizzo wrote: > is there any scanner (USB i presume by now) which is decently > supported by FreeBSD, perhaps something that can be driven > using a command line interface rather than SANE or some > other huge piece of software ? >=20 > In the past i have been using with success the Scanjet5p > (SCSI interface, but crappy hardware), and, with quite a > bit of hacking, the Artec AS6E (parallel port, very slow and low > quality), but now i'd really like to get something that > does not require me to spend time in writing a driver... My UMAX SuperVISTA S-12 (6 years old now, amazing that the thing still works, let alone produces quality images) works fine with SANE (which *does* have a CLI interface!). It's supported through generic pass driver. God, does SCSI rock. This scanner too, can't believe I bought it originally for my Mac in 1995 and it still works... even on FreeBSD.. *mumble* *mutter* --=20 wca *croak* --FEz7ebHBGB6b2e8X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6t6bqF47idPgWcsURAsTkAJ98P8mIPTh/U+JUkmIdk2/X0k7M6wCePdoJ Ls7C0x2Xrpkb9v+iar/GYuw= =OvsP -----END PGP SIGNATURE----- --FEz7ebHBGB6b2e8X-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:48:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 9C89B37B71C; Tue, 20 Mar 2001 10:48:46 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2KImj995560; Tue, 20 Mar 2001 10:48:45 -0800 (PST) (envelope-from dillon) Date: Tue, 20 Mar 2001 10:48:45 -0800 (PST) From: Matt Dillon Message-Id: <200103201848.f2KImj995560@earth.backplane.com> To: "Michael C . Wu" Cc: Alfred Perlstein , grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <200103201750.f2KHopk94248@earth.backplane.com> <20010320122245.E52586@peorth.iteration.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :We have 'vmstat 5' available at http://zoo.ee.ntu.edu.tw/~keichii/ :Fresh hot vmstat 1 log at :http://zoo.ee.ntu.edu.tw/~keichii/vmstat_1.log : :-- :+-----------------------------------------------------------+ :| keichii@iteration.net | keichii@freebsd.org | Your vmstat output indicates: * That you have plenty of cpu * That you are not paging heavily (good!) Ah. Your kernel config is in that directory too. Cool. Looks about what I expected. The default VM_KMEM_SIZE_MAX is 200MB, I'm not sure why you are reducing it to 192MB (but it wouldn't make much of a different I guess). I usually don't increase 'maxusers' above 256 myself, but 512 should be fine. Everything else looks fine too. The iostat output sheds more light on the disk activity. It doesn't look all that bad. If your users are accessing a lot of different files it might be beneficial to mount the filesystems in question with the 'noatime' option. This coupled with softupdates should remove any need for MFS. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:49:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 8F07A37B71A; Tue, 20 Mar 2001 10:49:12 -0800 (PST) (envelope-from dscheidt@tumbolia.com) Received: from shell-3.enteract.com (dscheidt@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.11.1/8.11.2) with ESMTP id f2KIEjG70592; Tue, 20 Mar 2001 12:14:45 -0600 (CST) (envelope-from dscheidt@tumbolia.com) Date: Tue, 20 Mar 2001 12:14:45 -0600 (CST) From: David Scheidt X-Sender: dscheidt@shell-3.enteract.com To: "Michael C . Wu" Cc: Ted Faber , fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server In-Reply-To: <20010320120314.D52586@peorth.iteration.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Mar 2001, Michael C . Wu wrote: : :SWAP is never touched. :) Your vmstat output shows page out activity. I can't tell if it's to swap or to file backed memory, but it's happening. You know this isn't happening when your box blows up? : :last pid: 23395; load averages: 2.08, 2.92, 3.60 up 0+01:29:58 02:03:27 :1529 processes:24 running, 1505 sleeping :CPU states: 40.5% user, 0.0% nice, 46.4% system, 1.1% interrupt, 12.0% idle :Mem: 705M Active, 1369M Inact, 332M Wired, 99M Cache, 265M Buf, 7504K Free :Swap: 512M Total, 512M Free You really, really should have at least as much as swap as RAM, probably closer to 2X. A big spike in load can run you out of swap very quickly -- less tan a minute. -- dscheidt@tumbolia.com Bipedalism is only a fad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:50:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id B476C37B71A; Tue, 20 Mar 2001 10:50:15 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id D0F0E59283; Tue, 20 Mar 2001 12:49:38 -0600 (CST) Date: Tue, 20 Mar 2001 12:49:38 -0600 From: "Michael C . Wu" To: Matt Dillon Cc: "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, Alfred Perlstein , grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded scerver Message-ID: <20010320124938.H52586@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320120112.C52586@peorth.iteration.net> <200103201815.f2KIFR594803@earth.backplane.com> <20010320122350.F52586@peorth.iteration.net> <200103201838.f2KIcZP95379@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103201838.f2KIcZP95379@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Mar 20, 2001 at 10:38:35AM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 10:38:35AM -0800, Matt Dillon scribbled: | | :| How big is 'lots'? If the shared memory segment is smallish, e.g. | :| less then 64MB, you should be ok. If it is larger then you will | :| have to do some kernel tuning to avoid running out of pmap entries. | : | :This is exactly what happens to us sometimes. We run out of pmap entries. :) | :But what can we tune? | sysctl -w kern.ipc.shm_use_phys=1 | | (run prior to creating the initial shared memory segment, e.g. when | the machine is booted). | | That should solve the pv entry problem. What Alfred said in regards | to 'sysctl -a' crashing too... We'll fix it if you give us a | traceback! Yes. I promised a trace for public and dump if you want. But there is no one at the NOC now. So it will have to be tomorrow night. We will take the box down at peak load to better help you guys. :) -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:52:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.net.com (relay2.net.com [134.56.3.108]) by hub.freebsd.org (Postfix) with ESMTP id 9D94E37B71A for ; Tue, 20 Mar 2001 10:52:09 -0800 (PST) (envelope-from shankar_agarwal@net.com) Received: from isis.net.com (fremont-ns1.net.com [134.56.112.20]) by relay2.net.com (8.11.3/8.9.3) with ESMTP id f2KIok622716 for ; Tue, 20 Mar 2001 10:50:48 -0800 (PST) Received: from west-mail.net.com by isis.net.com (8.9.3/SMI-SVR4) id KAA09105; Tue, 20 Mar 2001 10:50:46 -0800 (PST) Received: from net.com ([134.56.103.239]) by west-mail.net.com (Netscape Messaging Server 3.6) with ESMTP id AAA55A9; Tue, 20 Mar 2001 10:52:04 -0800 Message-ID: <3AB7A76B.2BCF5D6E@net.com> Date: Tue, 20 Mar 2001 10:54:35 -0800 From: Shankar Agarwal Organization: N.E.T. http://www.net.com X-Mailer: Mozilla 4.61C-NETv45 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en, en-GB, fr, de MIME-Version: 1.0 To: tech-kern@netbsd.org Cc: bsd hackers Subject: Question regarding the array of size 0. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I am getting the following array while trying to compile uipc_syscalls.c file. /vobs/atm/netbsd/sys/sys/syscallargs.h", line 30: zero or negative subscript This is because the code in syscallargs.h is defining an array of size 0. The code that is creating problem is #define syscallarg(x) \ union { \ register_t pad; \ struct { x datum; } le; \ struct { \ int8_t pad[ (sizeof (register_t) < sizeof (x)) \ ? 0 \ : sizeof (register_t) - sizeof (x)]; \ x datum; \ } be; \ } struct sys_exit_args { syscallarg(int) rval; }; struct sys_read_args { syscallarg(int) fd; syscallarg(void *) buf; syscallarg(size_t) nbyte; }; Can someone pls tell me if it is possible to define an array of size 0. If yes then do we need some compiler option for this to work. I am not using the Makefile of FreeBsd and trying to write my own make file which will work for this code. Thanks Regards Shankar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 10:53:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 8409437B71A; Tue, 20 Mar 2001 10:53:41 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2KIquW95665; Tue, 20 Mar 2001 10:52:56 -0800 (PST) (envelope-from dillon) Date: Tue, 20 Mar 2001 10:52:56 -0800 (PST) From: Matt Dillon Message-Id: <200103201852.f2KIquW95665@earth.backplane.com> To: Alfred Perlstein Cc: "Michael C . Wu" , "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded scerver References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320120112.C52586@peorth.iteration.net> <200103201815.f2KIFR594803@earth.backplane.com> <20010320122350.F52586@peorth.iteration.net> <20010320103130.Y29888@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :If this is a result of the shared memory, then my sysctl should fix it. : :Be aware, that it doesn't fix it on the fly! You must drop and recreate :the shared memory segments. : :better to reboot actually and set the variable before any shm is :allocated. : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Lets see. Approximately 4MB shared across 4000 processes. That eats 1024 pte's per process, or around 4 million pmap elements that would be saved. That's a lot of KVM that would be saved. I'll bet turning that option on will magically solve most of Michael's problems too (though I'd still get rid of the MFS filesystem). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 11: 3:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id 5FF8037B718 for ; Tue, 20 Mar 2001 11:03:24 -0800 (PST) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f2KJ3LO16883; Tue, 20 Mar 2001 13:03:21 -0600 (CST) Message-Id: <200103201903.f2KJ3LO16883@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: tech-kern@netbsd.org, bsd hackers Subject: Re: Question regarding the array of size 0. In-reply-to: Your message of "Tue, 20 Mar 2001 10:54:35 PST." <3AB7A76B.2BCF5D6E@net.com> Date: Tue, 20 Mar 2001 13:03:21 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3AB7A76B.2BCF5D6E@net.com>, Shankar Agarwal writes: >Can someone pls tell me if it is possible to define an array of size 0. Not in C. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 11: 4:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 1D7D737B718; Tue, 20 Mar 2001 11:04:25 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2KJ4GP95937; Tue, 20 Mar 2001 11:04:16 -0800 (PST) (envelope-from dillon) Date: Tue, 20 Mar 2001 11:04:16 -0800 (PST) From: Matt Dillon Message-Id: <200103201904.f2KJ4GP95937@earth.backplane.com> To: Ted Faber Cc: "Michael C . Wu" , fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <20010320094837.B1284@ted.isi.edu> <20010320120314.D52586@peorth.iteration.net> <20010320102156.C1284@ted.isi.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> SWAP is never touched. :) :> :> last pid: 23395; load averages: 2.08, 2.92, 3.60 up 0+01:29:58 02:03:27 :> 1529 processes:24 running, 1505 sleeping :> CPU states: 40.5% user, 0.0% nice, 46.4% system, 1.1% interrupt, 12.0% idle :> Mem: 705M Active, 1369M Inact, 332M Wired, 99M Cache, 265M Buf, 7504K Free :> Swap: 512M Total, 512M Free : :A couple other people have mentioned that this is your swap load when :the machine's quiet. MFS can exhaust your swap quickly, and if you :scale these load numbers up by a factor of 10, I think you're going to :touch swap. (Even here you're already down to 7M free mem.) That is almost certainly what is occuring. Since swap is otherwise not being used much, I'm going to retract my '3G of swap' recommendation (though if you ever repartition your disks I would still do it). You don't need 3G of swap, the 512M is fine as long as you scrap MFS. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 11: 4:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blubb.pdc.kth.se (blubb.pdc.kth.se [130.237.221.147]) by hub.freebsd.org (Postfix) with ESMTP id 5A5C437B71B for ; Tue, 20 Mar 2001 11:04:57 -0800 (PST) (envelope-from joda@pdc.kth.se) Received: from joda by blubb.pdc.kth.se with local (Exim 3.13 #1) id 14fRQt-00018n-00; Tue, 20 Mar 2001 20:04:39 +0100 To: Shankar Agarwal Cc: tech-kern@netbsd.org, bsd hackers Subject: Re: Question regarding the array of size 0. References: <3AB7A76B.2BCF5D6E@net.com> From: joda@pdc.kth.se (Johan Danielsson) Date: 20 Mar 2001 20:04:38 +0100 In-Reply-To: Shankar Agarwal's message of "Tue, 20 Mar 2001 10:54:35 -0800" Message-ID: Lines: 8 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shankar Agarwal writes: > Can someone pls tell me if it is possible to define an array of size > 0. No, but you can with gcc. /Johan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 11:17:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Twig.Rodents.Montreal.QC.CA (Twig.Rodents.Montreal.QC.CA [216.46.5.3]) by hub.freebsd.org (Postfix) with ESMTP id 0B71937B71C for ; Tue, 20 Mar 2001 11:17:13 -0800 (PST) (envelope-from mouse@Twig.Rodents.Montreal.QC.CA) Received: (from mouse@localhost) by Twig.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id OAA08339; Tue, 20 Mar 2001 14:16:57 -0500 (EST) Date: Tue, 20 Mar 2001 14:16:57 -0500 (EST) From: der Mouse Message-Id: <200103201916.OAA08339@Twig.Rodents.Montreal.QC.CA> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit To: Shankar Agarwal Cc: tech-kern@netbsd.org, freebsd-hackers@FreeBSD.ORG Subject: Re: Question regarding the array of size 0. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am getting the following array while trying to compile > uipc_syscalls.c file. > /vobs/atm/netbsd/sys/sys/syscallargs.h", line 30: zero or negative subscript > This is because the code in syscallargs.h is defining an array of size 0. > Can someone pls tell me if it is possible to define an array of size > 0. In C, no; in gcc, yes. NetBSD uses gcc. If you expect to build NetBSD code with any other compiler, you may have work to do; this is a simple example. (I've seen nods made in the direction of compatability with other compilers, but they are usually restricted to userland utilities; stuff like that are used only by the kernel get less attention in that direction.) > I am not using the Makefile of FreeBsd I'm not sure why this is relevant; attempting to build NetBSD source code (I note .../netbsd/... in the pathname above, and you asked this on (among others) a NetBSD mailing list) with a FreeBSD Makefile is bound to be an "on your own" sort of thing. > and trying to write my own make file which will work for this code. You will have to either rework it to avoid the zero-size array or switch to using a compiler that supports a C-like language including zero-size arrays (such as gcc). der Mouse mouse@rodents.montreal.qc.ca 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 11:22: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elfie.org (elfie.org [207.198.61.53]) by hub.freebsd.org (Postfix) with ESMTP id 3F33F37B719 for ; Tue, 20 Mar 2001 11:22:02 -0800 (PST) (envelope-from franklin@elfie.org) Received: (from franklin@localhost) by elfie.org (8.11.0/8.10.2) id f2KJLRD07167; Tue, 20 Mar 2001 14:21:27 -0500 (EST) Date: Tue, 20 Mar 2001 14:21:27 -0500 From: John Franklin To: Peter Seebach Cc: tech-kern@netbsd.org, bsd hackers Subject: Re: Question regarding the array of size 0. Message-ID: <20010320142127.D6167@elfie.org> References: <3AB7A76B.2BCF5D6E@net.com> <200103201903.f2KJ3LO16883@guild.plethora.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.9i In-Reply-To: <200103201903.f2KJ3LO16883@guild.plethora.net>; from seebs@plethora.net on Tue, Mar 20, 2001 at 01:03:21PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 01:03:21PM -0600, Peter Seebach wrote: > In message <3AB7A76B.2BCF5D6E@net.com>, Shankar Agarwal writes: > >Can someone pls tell me if it is possible to define an array of size 0. > > Not in C. Actually you can (see below). It depends on the compiler and how strict you have it checking things. It only works in this case because the memory manager is allocating an entire page for the structure, not just the size of the structure. It's not uncommon to use this for message-based communications where you have a header and payload and want to use sizeof(struct message) to get the header size, but also want to use foo.payload to access the message itself. In that case, it's more likely to be used as a cast on a buffer, (e.g., ((struct message*) buffer)->payload) Realize, tho, there's a potential portability issue, if you use this. What follows was done on a NetBSD 1.5 system. [24]% cat zero.c && make zero && ./zero #include struct zero_array { int header; int payload[0]; }; int main() { struct zero_array foo; foo.header=1; foo.payload[0]=10; foo.payload[1]=12; printf("Foo:\n\theader: %d\n", foo.header); printf("\tpayload 0: %d\n", foo.payload[0]); printf("\tpayload 1: %d\n", foo.payload[1]); return 0; } cc -O2 -o zero zero.c Foo: header: 1 payload 0: 10 payload 1: 12 jf -- John Franklin franklin@elfie.org ICBM: N37 12'54", W80 27'14" Z+2100' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 11:25:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id 2A80E37B71C for ; Tue, 20 Mar 2001 11:25:29 -0800 (PST) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f2KJPFO17440; Tue, 20 Mar 2001 13:25:15 -0600 (CST) Message-Id: <200103201925.f2KJPFO17440@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: tech-kern@netbsd.org, bsd hackers Subject: Re: Question regarding the array of size 0. In-reply-to: Your message of "Tue, 20 Mar 2001 14:21:27 EST." <20010320142127.D6167@elfie.org> Date: Tue, 20 Mar 2001 13:25:15 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010320142127.D6167@elfie.org>, John Franklin writes: >On Tue, Mar 20, 2001 at 01:03:21PM -0600, Peter Seebach wrote: >> In message <3AB7A76B.2BCF5D6E@net.com>, Shankar Agarwal writes: >> >Can someone pls tell me if it is possible to define an array of size 0. >> Not in C. >Actually you can (see below). It depends on the compiler and how strict >you have it checking things. The C language doesn't allow zero-sized objects. Some systems may, but C itself doesn't. >What follows was done on a NetBSD 1.5 system. More importantly, it was done with gcc, which (by default) compiles a language called "GNU C", which is very similar to C, but has some extensions. In C99, you can do this "portably" (C99 isn't exactly universally adopted yet) by saying struct message { int header; char payload[]; }; and then doing struct message *p; p = malloc(sizeof(struct message) + 10); p->header = 10; strcpy(p->payload, "123456789"); >int main() >{ > struct zero_array foo; > > foo.header=1; > foo.payload[0]=10; > foo.payload[1]=12; This isn't even a result of the page management, you're just overwriting other space. If you did struct zero_array foo; int a[2]; you would probably find that a[0] was 10, and a[1] was 12. Probably. The behavior is totally undefined, and it's not exactly reliable. :) -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 11:27:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from home.mcmanis.com (adsl-209-76-108-61.dsl.snfc21.pacbell.net [209.76.108.61]) by hub.freebsd.org (Postfix) with SMTP id D11EF37B71B for ; Tue, 20 Mar 2001 11:27:20 -0800 (PST) (envelope-from cmcmanis@mcmanis.com) Received: (qmail+freegate 25784 invoked by alias); 20 Mar 2001 19:27:19 -0000 Received: from ws71-n0.hq.home.mcmanis.com (HELO hplaptop) (192.168.110.71) by hq.home.mcmanis.com with SMTP; 20 Mar 2001 19:27:19 -0000 Date: Tue, 20 Mar 2001 11:25:43 -0800 To: John Franklin , Peter Seebach Cc: tech-kern@netbsd.org, bsd hackers From: Chuck McManis Subject: Re: Question regarding the array of size 0. Organization: KillerBotz Inc X-Mailer: Opera 5.02 build 856a X-Priority: 3 (Normal) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Message-Id: <20010320192720.D11EF37B71B@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Which is an example of a buffer overrun exploit perhaps? As it has been mentioned there is "C" and there is "ANSI-C" and there is "GCC" and they are not the same language. --Chuck 3/20/01 9:21:27 AM, John Franklin wrote: >struct zero_array { > int header; > int payload[0]; >}; ... > foo.header=1; > foo.payload[0]=10; > foo.payload[1]=12; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 11:28:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blubb.pdc.kth.se (blubb.pdc.kth.se [130.237.221.147]) by hub.freebsd.org (Postfix) with ESMTP id D684437B719 for ; Tue, 20 Mar 2001 11:28:14 -0800 (PST) (envelope-from joda@pdc.kth.se) Received: from joda by blubb.pdc.kth.se with local (Exim 3.13 #1) id 14fRnZ-00019j-00; Tue, 20 Mar 2001 20:28:05 +0100 To: John Franklin Cc: Peter Seebach , tech-kern@netbsd.org, bsd hackers Subject: Re: Question regarding the array of size 0. References: <3AB7A76B.2BCF5D6E@net.com> <200103201903.f2KJ3LO16883@guild.plethora.net> <20010320142127.D6167@elfie.org> From: joda@pdc.kth.se (Johan Danielsson) Date: 20 Mar 2001 20:28:05 +0100 In-Reply-To: John Franklin's message of "Tue, 20 Mar 2001 14:21:27 -0500" Message-ID: Lines: 26 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Franklin writes: > > Not in C. > > Actually you can (see below). No you can't. This is from C99: 6.7.5.2 Array declarators Constraints In addition to optional type qualifiers and the keyword static, the [ and ] may delimit an expression or *. If they delimit an expression (which specifies the size of an array), the expression shall have an integer type. If the expression is a constant expression, it shall have a value greater than zero. [...] > What follows was done on a NetBSD 1.5 system. Which uses gcc. I think they use a similar example in the spec, but with an array size of one. /Johan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 11:32: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from starwolf.com (starwolf.com [208.184.74.2]) by hub.freebsd.org (Postfix) with ESMTP id 989FA37B71B for ; Tue, 20 Mar 2001 11:32:02 -0800 (PST) (envelope-from greywolf@starwolf.com) Received: from starjumper.starwolf.com (IDENT:greywolf@starjumper [208.184.74.3]) by starwolf.com (8.11.0/8.11.0) with ESMTP id f2KJVZD02718; Tue, 20 Mar 2001 11:31:35 -0800 (PST) Date: Tue, 20 Mar 2001 11:31:40 -0800 (PST) From: Greywolf To: Shankar Agarwal Cc: , bsd hackers Subject: Re: Question regarding the array of size 0. In-Reply-To: <3AB7A76B.2BCF5D6E@net.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Mar 2001, Shankar Agarwal wrote: # Date: Tue, 20 Mar 2001 10:54:35 -0800 # From: Shankar Agarwal # To: tech-kern@netbsd.org # Cc: bsd hackers # Subject: Question regarding the array of size 0. # # Hi All, # I am getting the following array while trying to compile uipc_syscalls.c # file. # /vobs/atm/netbsd/sys/sys/syscallargs.h", line 30: zero or negative # subscript # This is because the code in syscallargs.h is defining an array of size # 0. # The code that is creating problem is # #define syscallarg(x) \ # union { \ # register_t pad; \ # struct { x datum; } le; \ # struct { \ # int8_t pad[ (sizeof (register_t) < sizeof (x)) \ # ? 0 \ # : sizeof (register_t) - sizeof (x)]; \ # x datum; \ # } be; \ # } # # struct sys_exit_args { # syscallarg(int) rval; # }; I thought ?: were evaluated at run-time, not compile-time? --*greywolf; -- *BSD: The power to Connect To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 11:35: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hawk.prod.itd.earthlink.net (hawk.prod.itd.earthlink.net [207.217.120.22]) by hub.freebsd.org (Postfix) with ESMTP id E47D137B71C for ; Tue, 20 Mar 2001 11:35:01 -0800 (PST) (envelope-from fmela0@sm.socccd.cc.ca.us) Received: from sm.socccd.cc.ca.us (pool0116.cvx4-bradley.dialup.earthlink.net [209.178.146.116]) by hawk.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id LAA01798; Tue, 20 Mar 2001 11:34:46 -0800 (PST) Message-ID: <3AB7B141.6CB14ADF@sm.socccd.cc.ca.us> Date: Tue, 20 Mar 2001 11:36:33 -0800 From: Farooq Mela Reply-To: fmela0@sm.socccd.cc.ca.us X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Greywolf Cc: Shankar Agarwal , tech-kern@netbsd.org, bsd hackers Subject: Re: Question regarding the array of size 0. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greywolf wrote: > # struct { \ > # int8_t pad[ (sizeof (register_t) < sizeof (x)) \ > # ? 0 \ > # : sizeof (register_t) - sizeof (x)]; \ > I thought ?: were evaluated at run-time, not compile-time? sizeof() is evaluated at compile time. -- farooq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 11:35:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from noc.untraceable.net (noc.untraceable.net [166.84.189.65]) by hub.freebsd.org (Postfix) with ESMTP id 40A5E37B71A for ; Tue, 20 Mar 2001 11:35:19 -0800 (PST) (envelope-from atatat@atatdot.net) Received: (from andrew@localhost) by noc.untraceable.net (8.12.0.Beta5/8.12.0.Beta5/bonk!) id f2KJZ9xg029944; Tue, 20 Mar 2001 14:35:09 -0500 (EST) Date: Tue, 20 Mar 2001 14:35:08 -0500 From: Andrew Brown To: Greywolf Cc: Shankar Agarwal , tech-kern@netbsd.org, bsd hackers Subject: Re: Question regarding the array of size 0. Message-ID: <20010320143508.A29869@noc.untraceable.net> Reply-To: Andrew Brown References: <3AB7A76B.2BCF5D6E@net.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from greywolf@starwolf.com on Tue, Mar 20, 2001 at 11:31:40AM -0800 X-Hi-To-All-My-Friends-In-Domestic-Surveillance: hi there, sports fans :) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 11:31:40AM -0800, Greywolf wrote: >On Tue, 20 Mar 2001, Shankar Agarwal wrote: > ># Date: Tue, 20 Mar 2001 10:54:35 -0800 ># From: Shankar Agarwal ># To: tech-kern@netbsd.org ># Cc: bsd hackers ># Subject: Question regarding the array of size 0. ># ># Hi All, ># #define syscallarg(x) \ ># union { \ ># register_t pad; \ ># struct { x datum; } le; \ ># struct { \ ># int8_t pad[ (sizeof (register_t) < sizeof (x)) \ ># ? 0 \ ># : sizeof (register_t) - sizeof (x)]; \ ># x datum; \ ># } be; \ ># } ># ># struct sys_exit_args { ># syscallarg(int) rval; ># }; > >I thought ?: were evaluated at run-time, not compile-time? any halfway decent optimizing compiler ought to be reducing the number of useless constants in its output, this being an example of such. -- |-----< "CODE WARRIOR" >-----| codewarrior@daemon.org * "ah! i see you have the internet twofsonet@graffiti.com (Andrew Brown) that goes *ping*!" andrew@crossbar.com * "information is power -- share the wealth." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 12:41:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from manta.mayn.de (big.endian.de [194.145.150.69]) by hub.freebsd.org (Postfix) with ESMTP id 0330637B71A for ; Tue, 20 Mar 2001 12:41:16 -0800 (PST) (envelope-from alex@fump.cichlids.com) Received: from fump.cichlids.com (big.endian.de [194.145.150.69]) by manta.mayn.de (Postfix) with ESMTP id 910429B005; Tue, 20 Mar 2001 21:41:28 +0100 (CET) Received: by fump.cichlids.com (Postfix, from userid 1001) id AFD437BDB; Mon, 19 Mar 2001 22:27:07 +0100 (CET) Date: Mon, 19 Mar 2001 22:27:07 +0100 From: Alexander Langer To: avn Cc: Alexander Langer , freebsd-hackers@FreeBSD.ORG Subject: Re: device driver dev. book Message-ID: <20010319222707.B551@fump.cichlids.com> References: <20010317153934.A2243@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from avn@any.ru on Mon, Mar 19, 2001 at 11:42:25AM +0300 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-PGP-at: finger alex@big.endian.de X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake avn (avn@any.ru): > >A "Developers Handbook", which will also cover device driver and > >kernel module programming is in work under the leadership of Jeroen > Is there URL for work in progress? :) cvsup the doc tree. You won't find much, though. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 13: 5:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 1C82337B71B for ; Tue, 20 Mar 2001 13:05:47 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2KL2wg27895; Tue, 20 Mar 2001 13:02:58 -0800 (PST) Date: Tue, 20 Mar 2001 13:02:58 -0800 From: Alfred Perlstein To: Paul Herman Cc: Matt Dillon , "Michael C . Wu" , hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server Message-ID: <20010320130257.F29888@fw.wintelcom.net> References: <200103201848.f2KImj995560@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from pherman@frenchfries.net on Tue, Mar 20, 2001 at 10:00:40PM +0100 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Paul Herman [010320 13:02] wrote: > On Tue, 20 Mar 2001, Matt Dillon wrote: > > > :We have 'vmstat 5' available at http://zoo.ee.ntu.edu.tw/~keichii/ > > :Fresh hot vmstat 1 log at > > :http://zoo.ee.ntu.edu.tw/~keichii/vmstat_1.log > > > > I usually don't increase 'maxusers' above 256 myself, but > > 512 should be fine. Everything else looks fine too. > > I ran a heavily loaded (3.4-RELEASE) www/mysql server once which > randomly froze about every three days. It had maxusers 512, and > backing it off to about 490 got rid of the freezing. IIRC, it used to > not be safe to run maxusers 512, but things may have changed since > then. It should have been fixed, if it's broken again we'd like to know. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 13:16:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by hub.freebsd.org (Postfix) with ESMTP id C21DC37B71D for ; Tue, 20 Mar 2001 13:16:39 -0800 (PST) (envelope-from titus@pleach.de) Received: from fwd07.sul.t-online.com by mailout04.sul.t-online.com with smtp id 14fTSc-000325-04; Tue, 20 Mar 2001 22:14:34 +0100 Received: from mail.net (340050866639-0001@[62.226.215.29]) by fmrl07.sul.t-online.com with esmtp id 14fTSB-2L5UuGC; Tue, 20 Mar 2001 22:14:07 +0100 Received: from schweinkram.pleach-hamburg.de (localhost [127.0.0.1]) by mail.net (8.11.1/8.9.2) with ESMTP id f2KLBax63428; Tue, 20 Mar 2001 22:11:36 +0100 (CET) (envelope-from titus@pleach-hamburg.de) Received: from pleach-hamburg.de (dialin01.pleachconn.de [192.168.2.10]) by schweinkram.pleach-hamburg.de (8.11.1/8.11.1) with ESMTP id f2KL9Kv63358; Tue, 20 Mar 2001 22:09:20 +0100 (CET) (envelope-from titus@pleach-hamburg.de) Message-ID: <3AB7C787.96200D6C@pleach-hamburg.de> Date: Tue, 20 Mar 2001 22:11:35 +0100 From: Titus von Boxberg X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: de-DE,en MIME-Version: 1.0 To: "Alexander N. Kabaev" Cc: hackers@FreeBSD.ORG Subject: Re: GCC Upgrade? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: 340050866639-0001@t-dialin.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Alexander N. Kabaev" wrote: > > On 19-Mar-2001 Titus von Boxberg wrote: > > David O'Brien wrote: > >> > >> On Mon, Mar 19, 2001 at 02:54:52PM +0100, Titus von Boxberg wrote: > >> > Since at least aug. 2000 (according to the mailing list > >> > archives) the exception handling in base system g++ is broken > >> > (at least for multithreaded programs) > > The problem you are talking about has nothing to do with threads. Rather, the > problem was with the way in which GCC handles inline function expansions. Why does the code generated by the packaged gcc2952 work? And why can't that version be used for the base system? Is there a link available to documentation that explains DWARF and fsjlf > Yet another problem I have patches for. GCC does not handle PIC register > correctly when handling exceptions thrown across shared library boundaries. > Additionally, the shared libraries in AIX make the challenge of sharing > exception context state among all shared libraries in the executable very > interesting. I was unable to get these fixes into official CVS source - FSF > guys apparently decided that the problem cannot be fixed. They even seriously > tried to convince me that my patch could not work except by coincidence > without even taking a sigle look at the patch itself - even though that > 'coincidence' reliably works for me in multithreaded CORBA server written using > omniORB :) I basically gave up on them. Drop me a line if you need help getting > GCC 2.95.3 work properly on AIX 4.x. Thanks a lot, normally I'm just using FreeBSD/i386 or NT/VC++ regards titus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 13:34: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id D568E37B71C for ; Tue, 20 Mar 2001 13:34:05 -0800 (PST) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.11.3/8.11.3) id f2KLV7l65387; Tue, 20 Mar 2001 16:31:07 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.7p2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <3AB7C787.96200D6C@pleach-hamburg.de> Date: Tue, 20 Mar 2001 16:31:06 -0500 (EST) Organization: Verizon Laboratories Inc. From: "Alexander N. Kabaev" To: Titus von Boxberg Subject: Re: GCC Upgrade? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Mar-2001 Titus von Boxberg wrote: > "Alexander N. Kabaev" wrote: >> >> On 19-Mar-2001 Titus von Boxberg wrote: >> > David O'Brien wrote: >> >> >> >> On Mon, Mar 19, 2001 at 02:54:52PM +0100, Titus von Boxberg wrote: >> >> > Since at least aug. 2000 (according to the mailing list >> >> > archives) the exception handling in base system g++ is broken >> >> > (at least for multithreaded programs) >> >> The problem you are talking about has nothing to do with threads. Rather, >> the >> problem was with the way in which GCC handles inline function expansions. > Why does the code generated by the packaged gcc2952 work? > And why can't that version be used for the base system? Because gcc 2.95.2 from ports is configured to use DWARF2 unwinder which is not affected by this particular bug. There is DWARF2 specific INSN bookkeeping in GCC which allows the basic code blocks to stay alive. These blocks get erroneously deleted by the GCC optimizer in sjlj case. > And why can't that version be used for the base system? Again, because it uses DWARF2 exception handling. You cannot easily switch between sjlj and DWARF2 exception handling methods and you cannot mix and match object files and libraries compiled with different exception flags. The switch will require that every C++ binary and every C++ library on all FreeBSD boxes is recompiled. I certainly do not see that happening in FreeBSD 4-STABLE any time soon. FreeBSD-CURRENT might switch to DWARF2 some day, David O'Brien is the right person to ask about that. > Is there a link available to documentation that explains DWARF and fsjlf You could try looking at gcc.gnu.org site for information on how GCC works internally. ---------------------------------- E-Mail: Alexander N. Kabaev Date: 20-Mar-2001 Time: 16:15:24 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 13:35:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mr200.netcologne.de (mr200.netcologne.de [194.8.194.109]) by hub.freebsd.org (Postfix) with ESMTP id 504B837B71A for ; Tue, 20 Mar 2001 13:35:28 -0800 (PST) (envelope-from pherman@frenchfries.net) Received: from husten.security.at12.de (dial-213-168-64-176.netcologne.de [213.168.64.176]) by mr200.netcologne.de (Mirapoint) with ESMTP id ACT75210; Tue, 20 Mar 2001 22:00:53 +0100 (CET) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by husten.security.at12.de (8.11.3/8.11.2) with ESMTP id f2KL0eD42311; Tue, 20 Mar 2001 22:00:41 +0100 (CET) (envelope-from pherman@frenchfries.net) Date: Tue, 20 Mar 2001 22:00:40 +0100 (CET) From: Paul Herman To: Matt Dillon Cc: "Michael C . Wu" , Alfred Perlstein , Subject: Re: tuning a VERY heavily (30.0) loaded server In-Reply-To: <200103201848.f2KImj995560@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Mar 2001, Matt Dillon wrote: > :We have 'vmstat 5' available at http://zoo.ee.ntu.edu.tw/~keichii/ > :Fresh hot vmstat 1 log at > :http://zoo.ee.ntu.edu.tw/~keichii/vmstat_1.log > > I usually don't increase 'maxusers' above 256 myself, but > 512 should be fine. Everything else looks fine too. I ran a heavily loaded (3.4-RELEASE) www/mysql server once which randomly froze about every three days. It had maxusers 512, and backing it off to about 490 got rid of the freezing. IIRC, it used to not be safe to run maxusers 512, but things may have changed since then. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 13:56:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 9E81F37B723 for ; Tue, 20 Mar 2001 13:56:26 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id WAA89252; Tue, 20 Mar 2001 22:56:23 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Dan Phoenix Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: apache truss readings References: From: Dag-Erling Smorgrav Date: 20 Mar 2001 22:56:22 +0100 In-Reply-To: Dan Phoenix's message of "Tue, 20 Mar 2001 10:35:14 -0800 (PST)" Message-ID: Lines: 8 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dan Phoenix writes: > [...] Try ktrace instead, it provides much more detailed information. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 14: 8:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cmailg7.svr.pol.co.uk (cmailg7.svr.pol.co.uk [195.92.195.177]) by hub.freebsd.org (Postfix) with ESMTP id 04F9037B71A for ; Tue, 20 Mar 2001 14:08:31 -0800 (PST) (envelope-from rearnsha@buzzard.freeserve.co.uk) Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk) by cmailg7.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 14fUIn-0008Cy-00 for freebsd-hackers@freebsd.org; Tue, 20 Mar 2001 22:08:29 +0000 Received: from modem-203.blackbird.dialup.pol.co.uk ([62.137.124.203] helo=buzzard.freeserve.co.uk) by mail18.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 14fUIm-0005bg-00 for freebsd-hackers@FreeBSD.ORG; Tue, 20 Mar 2001 22:08:28 +0000 Received: from buzzard (localhost [127.0.0.1]) by buzzard.freeserve.co.uk (8.11.3/8.11.1) with ESMTP id f2KM8LZ00878; Tue, 20 Mar 2001 22:08:21 GMT Message-Id: <200103202208.f2KM8LZ00878@buzzard.freeserve.co.uk> X-Mailer: exmh version 2.1.1 10/15/1999 To: der Mouse Cc: Shankar Agarwal , tech-kern@netbsd.org, freebsd-hackers@FreeBSD.ORG Subject: Re: Question regarding the array of size 0. In-Reply-To: Your message of "Tue, 20 Mar 2001 14:16:57 EST." <200103201916.OAA08339@Twig.Rodents.Montreal.QC.CA> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Mar 2001 22:08:21 +0000 From: Richard Earnshaw X-BadReturnPath: rearnsha@buzzard.buzzard.freeserve.co.uk rewritten as rearnsha@buzzard.freeserve.co.uk using "From" header Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am getting the following array while trying to compile > > uipc_syscalls.c file. > > > /vobs/atm/netbsd/sys/sys/syscallargs.h", line 30: zero or negative subscript > > This is because the code in syscallargs.h is defining an array of size 0. > > > Can someone pls tell me if it is possible to define an array of size > > 0. > > In C, no; in gcc, yes. > You can also do it in c98, provided it is the last element of a structure. R. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 14: 9:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id 8930237B72E for ; Tue, 20 Mar 2001 14:09:40 -0800 (PST) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f2KM9VO16925; Tue, 20 Mar 2001 16:09:32 -0600 (CST) Message-Id: <200103202209.f2KM9VO16925@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: tech-kern@netbsd.org, freebsd-hackers@freebsd.org Subject: Re: Question regarding the array of size 0. In-reply-to: Your message of "Tue, 20 Mar 2001 22:08:21 GMT." <200103202208.f2KM8LZ00878@buzzard.freeserve.co.uk> Date: Tue, 20 Mar 2001 16:09:31 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200103202208.f2KM8LZ00878@buzzard.freeserve.co.uk>, Richard Earnsha w writes: >You can also do it in c98, provided it is the last element of a structure. C99, but it's not spelled as [0], it's spelled as []. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 14:11:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id DFAF737B78B for ; Tue, 20 Mar 2001 14:11:37 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id XAA89295; Tue, 20 Mar 2001 23:11:35 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: freebsd-hackers@FreeBSD.ORG Cc: Gurpratap Virdi Subject: Re: Debuging kernel crashes References: <20010320055052.20711.qmail@venus.postmark.net> <20010319213936.F29888@fw.wintelcom.net> <001101c0b102$977d8310$050101c0@dhgfhcpps5nhe1> <20010320094737.A22505@daemon.ninth-circle.org> From: Dag-Erling Smorgrav Date: 20 Mar 2001 23:11:34 +0100 In-Reply-To: Jeroen Ruigrok/Asmodai's message of "Tue, 20 Mar 2001 09:47:37 +0100" Message-ID: Lines: 12 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai writes: > Please see http://www.freebsd.org/handbook/kerneldebug.html > > If you find any problems with that let us know in -doc and we'll fix the > docs. Actually, I have uncommitted patches to that file. I'll see what I can do about cleaning them up and committing them. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 14:12:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 93C0837B759 for ; Tue, 20 Mar 2001 14:12:37 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2KMCRV41061; Tue, 20 Mar 2001 14:12:27 -0800 (PST) (envelope-from obrien) Date: Tue, 20 Mar 2001 14:12:23 -0800 From: "David O'Brien" To: "Alexander N. Kabaev" Cc: Titus von Boxberg , hackers@FreeBSD.ORG Subject: Re: GCC Upgrade? Message-ID: <20010320141223.A40933@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <3AB7C787.96200D6C@pleach-hamburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ak03@gte.com on Tue, Mar 20, 2001 at 04:31:06PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 04:31:06PM -0500, Alexander N. Kabaev wrote: > I certainly do not see that happening in FreeBSD 4-STABLE any time > soon. It never will. > FreeBSD-CURRENT might switch to DWARF2 some day, David O'Brien is > the right person to ask about that. It will happen right after I MFC GCC 2.95.3. DWARF2 is required by the IA-64 psABI, and is supported better on the Alpha. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 14:14:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id AC9FA37B759 for ; Tue, 20 Mar 2001 14:14:26 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id XAA89318; Tue, 20 Mar 2001 23:14:20 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Peter Pentchev Cc: Thiago Pinto Damas , freebsd-hackers@FreeBSD.ORG Subject: Re: kernel panic References: <20010320191434.C21416@ringworld.oblivion.bg> From: Dag-Erling Smorgrav Date: 20 Mar 2001 23:14:20 +0100 In-Reply-To: Peter Pentchev's message of "Tue, 20 Mar 2001 19:14:35 +0200" Message-ID: Lines: 10 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Pentchev writes: > You could take a look at www.FreeBSD.org/handbook/kerneldebug.html > and provide a bit more details about that crash; at the very least, > a 'where' or 'bt' would be useful. That, and a dmesg, or at least uname -a. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 14:15:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail12.svr.pol.co.uk (mail12.svr.pol.co.uk [195.92.193.215]) by hub.freebsd.org (Postfix) with ESMTP id 0E1D537B75A for ; Tue, 20 Mar 2001 14:15:30 -0800 (PST) (envelope-from rearnsha@buzzard.freeserve.co.uk) Received: from [195.92.67.23] (helo=mail18.svr.pol.co.uk) by mail12.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 14fUPZ-0005Tf-00 for freebsd-hackers@freebsd.org; Tue, 20 Mar 2001 22:15:29 +0000 Received: from modem-203.blackbird.dialup.pol.co.uk ([62.137.124.203] helo=buzzard.freeserve.co.uk) by mail18.svr.pol.co.uk with esmtp (Exim 3.13 #0) id 14fUPZ-00060F-00 for freebsd-hackers@freebsd.org; Tue, 20 Mar 2001 22:15:29 +0000 Received: from buzzard (localhost [127.0.0.1]) by buzzard.freeserve.co.uk (8.11.3/8.11.1) with ESMTP id f2KMFUZ00952; Tue, 20 Mar 2001 22:15:30 GMT Message-Id: <200103202215.f2KMFUZ00952@buzzard.freeserve.co.uk> X-Mailer: exmh version 2.1.1 10/15/1999 To: seebs@plethora.net (Peter Seebach) Cc: tech-kern@netbsd.org, freebsd-hackers@freebsd.org Subject: Re: Question regarding the array of size 0. In-Reply-To: Your message of "Tue, 20 Mar 2001 16:09:31 CST." <200103202209.f2KM9VO16925@guild.plethora.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Mar 2001 22:15:30 +0000 From: Richard Earnshaw X-BadReturnPath: rearnsha@buzzard.buzzard.freeserve.co.uk rewritten as rearnsha@buzzard.freeserve.co.uk using "From" header Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200103202208.f2KM8LZ00878@buzzard.freeserve.co.uk>, Richard Earnsha > w writes: > >You can also do it in c98, provided it is the last element of a structure. > > C99, but it's not spelled as [0], it's spelled as []. So I got fed up of waiting. Whatever, that's the one. R. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 14:19:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from amsmta02-svc.chello.nl (mail-out.chello.nl [213.46.240.7]) by hub.freebsd.org (Postfix) with ESMTP id BA2DD37B78D for ; Tue, 20 Mar 2001 14:19:29 -0800 (PST) (envelope-from wvengen@stack.nl) Received: from stack.nl ([213.46.110.240]) by amsmta02-svc.chello.nl (InterMail vK.4.03.02.00 201-232-124 license 123510a18e2ad992799e3cab97e0f17c) with ESMTP id <20010320220554.KLN21800.amsmta02-svc@stack.nl> for ; Tue, 20 Mar 2001 23:05:54 +0100 Message-ID: <3AB7D52A.3EBDD198@stack.nl> Date: Tue, 20 Mar 2001 23:09:46 +0100 From: Willem van Engen X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: driver: probe not called when smbus child References: <3AB77C31.8213C158@stack.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's currently working as an isa-child, but I'm still wondering if it's the 'clean' way, since I only use smbus commands. - Willem Willem van Engen wrote: > > I'm trying to write a module which should be a child of the smbus. > When I make the driver a child of the isa bus, identify, probe, > and attach functions are properly called. I use the following > code to do that: > DRIVER_MODULE(my, isa, my_driver, my_devclass, 0, 0); > But when I put it on the smbus using > DRIVER_MODULE(my, smbus, my_driver, my_devclass, 0, 0); > only identify is called. The identify function is as follows: > > static void > my_identify(driver_t *driver, device_t parent) > { > devclass_t dc; > device_t child; > > printf("my: my_identify called\n"); > dc = devclass_find("my"); > if (devclass_get_device(dc, 0)==NULL) { > child = BUS_ADD_CHILD(parent, 0, "my", -1); > } > } > > The driver only uses smbus calls, so I think the best parent > would be smbus. > And when I do a smbus_request_bus, the call waits forever as > it seems. That seems sensible to me, because it asks the > parent for the bus and the isa bus can't grant requests for > the smbus. So I think the driver has to be a child of the smbus. > > Looking in the kernel sources, I see that the only smbus child > I can find, smb, (if there are others, I'm certainly interested) > is attached in the smbus code itself. So the next question rises: > Is it possible to have an smbus child in a dynamically loadable > module (I can't find smbus.ko in /modules, so loading the child > first and then smbus isn't an option I guess) ? > > - Willem van Engen > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 14:22:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id BAAAF37B731; Tue, 20 Mar 2001 14:22:11 -0800 (PST) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.11.3/8.11.3) id f2KMMBm65665; Tue, 20 Mar 2001 17:22:11 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.7p2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010320141223.A40933@dragon.nuxi.com> Date: Tue, 20 Mar 2001 17:22:11 -0500 (EST) Organization: Verizon Laboratories Inc. From: "Alexander N. Kabaev" To: "David O'Brien" Subject: Re: GCC Upgrade? Cc: hackers@FreeBSD.ORG, Titus von Boxberg Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Mar-2001 David O'Brien wrote: > On Tue, Mar 20, 2001 at 04:31:06PM -0500, Alexander N. Kabaev wrote: >> I certainly do not see that happening in FreeBSD 4-STABLE any time >> soon. > > It never will. I was trying to tell the same in less definitive words :) >> FreeBSD-CURRENT might switch to DWARF2 some day, David O'Brien is >> the right person to ask about that. > > It will happen right after I MFC GCC 2.95.3. DWARF2 is required by the > IA-64 psABI, and is supported better on the Alpha. It will be so nice to finally leave these sjlj exceptions problems behind. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 16:17:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.prod.itd.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id C8A0E37B71F for ; Tue, 20 Mar 2001 16:17:28 -0800 (PST) (envelope-from gvirdi@gvirdi.com) Received: from godfather (1Cust66.tnt1.chi1.da.uu.net [63.20.221.66]) by falcon.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id QAA23094; Tue, 20 Mar 2001 16:17:25 -0800 (PST) Message-ID: <02fb01c0b19d$12355200$cc4b6f87@godfather> From: "Gurpratap Virdi" To: , "Dag-Erling Smorgrav" References: <20010320055052.20711.qmail@venus.postmark.net> <20010319213936.F29888@fw.wintelcom.net> <001101c0b102$977d8310$050101c0@dhgfhcpps5nhe1> <20010320094737.A22505@daemon.ninth-circle.org> Subject: Re: Debuging kernel crashes Date: Tue, 20 Mar 2001 18:22:50 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks!! Could you please let me know when it's ready. Virdi ----- Original Message ----- From: "Dag-Erling Smorgrav" To: Cc: "Gurpratap Virdi" Sent: Tuesday, March 20, 2001 4:11 PM Subject: Re: Debuging kernel crashes Jeroen Ruigrok/Asmodai writes: > Please see http://www.freebsd.org/handbook/kerneldebug.html > > If you find any problems with that let us know in -doc and we'll fix the > docs. Actually, I have uncommitted patches to that file. I'll see what I can do about cleaning them up and committing them. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 17:48:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cube.gelatinous.com (cube.gelatinous.com [207.82.194.150]) by hub.freebsd.org (Postfix) with SMTP id 237A137B73D for ; Tue, 20 Mar 2001 17:48:44 -0800 (PST) (envelope-from aaron@mutex.org) Received: (qmail 53174 invoked by uid 1000); 21 Mar 2001 01:46:30 -0000 Date: Tue, 20 Mar 2001 17:46:30 -0800 From: Aaron Smith To: freebsd-hackers@freebsd.org Cc: jon@csua.berkeley.edu, breadbox@muppetlabs.com Subject: gzip's custom i386 asm should be disabled Message-ID: <20010320174630.B82004@gelatinous.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="0rSojgWGcpz+ezC3" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --0rSojgWGcpz+ezC3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline gzip's i386 assembly code, activated by default in the FreeBSD source tree, produces poor performance on an i686 core (PPro/P2/P3). This is due to the 'partial register stall' problem, explained in a URL recently brought up on the list, http://www.emulators.com/pentium4.htm. In the course of learning more about partial register stalls I came across the following i686 and i586 assembly optimizations for gzip: http://www.muppetlabs.com/~breadbox/software/assembly.html. This optimized i686 asm avoids partial reg stall and is between 20-40% faster, with higher compression levels achieving greater benefit from the patch. The i586 patch is usually only 5% faster, but in some cases achieves a 25% speedup. For completeness, I also ran some tests on a non-asm gcc 2.95.2 compile, with and without -march=pentiumpro. Here are the results (three runs, averaged, caches warmed with some throwaway runs) on a Pentium II 400, linux-2.4.2.tar, --best. [type] [user secs] [time (as % of slowest)] i386 asm: 175 100% no asm, -O: 142 81.1% no asm, -O2: 139 79.4% no asm, -O -march=pentiumpro: 136 77.7% no asm, -O2 -march=pentiumpro: 140 80.0% i686 asm: 124 70.8% I'm interested in other people's results/tests. Particularly, I should do some runs with -mcpu=pentiumpro as well. An important part of the equation is to make sure it doesn't hurt i586 machines. I did several tests on a Pentium 200MMX; the i386 asm and the gcc-emitted asm are not measurably different on that CPU. Brian Raiter (breadbox@muppetlabs.com, author of the i586/i686 asm patches) has contacted the gzip maintainers, but it's been years since a release and there may not be another gzip release. I have seen a 1.2.4a release which had his files in a contrib/ directory, but they were not active in any way. Since I would imagine a large percentage of FreeBSD users run on i686 cores, it'd be great to get this pretty significant speed increase into our tree. The i686 patch is neat (30% faster!) but its improvement over gcc's emitted assembly is small. Disabling the old i386 assembly seems a good first step. Attached is a patch that disables the custom asm. I'm interested in hearing everyone's comments. Aaron --0rSojgWGcpz+ezC3 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=gzip-noasm-patch Index: Makefile =================================================================== RCS file: /usr/cvs/src/gnu/usr.bin/gzip/Makefile,v retrieving revision 1.21 diff -u -r1.21 Makefile --- Makefile 1999/08/27 23:35:48 1.21 +++ Makefile 2001/03/20 23:59:48 @@ -8,11 +8,6 @@ CFLAGS+=-DSTDC_HEADERS=1 -DHAVE_UNISTD_H=1 -DDIRENT=1 GREP_LIBZ?= YES -.if ${MACHINE_ARCH} == "i386" -SRCS+= match.S -CFLAGS+=-DASMV -.endif - MLINKS= gzip.1 gunzip.1 gzip.1 zcat.1 gzip.1 gzcat.1 MLINKS+= zdiff.1 zcmp.1 --0rSojgWGcpz+ezC3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 18:14:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id 865FA37B71A for ; Tue, 20 Mar 2001 18:14:29 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f2L2AUg89630; Tue, 20 Mar 2001 21:10:30 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <017d01c0b1ab$df4be1b0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Aaron Smith" , Cc: , References: <20010320174630.B82004@gelatinous.com> Subject: Re: gzip's custom i386 asm should be disabled Date: Tue, 20 Mar 2001 21:08:49 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Since I would imagine a large percentage of FreeBSD users run on i686 > cores, it'd be great to get this pretty significant speed increase into our > tree. I sure hope I'm not the only one with a "lab" of 4 FreeBSD machines that are all 486s or 586s. It would be great to implement these patches for gzip in the base tree, but they need to be conditianal based on CPUTYPE in /etc/make.conf. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 20:33:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 531D537B730; Tue, 20 Mar 2001 20:33:41 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (1cny9a@localhost [127.0.0.1]) by green.dyndns.org (8.11.2/8.11.1) with ESMTP id f2L4WNd21223; Tue, 20 Mar 2001 23:32:24 -0500 (EST) (envelope-from green@FreeBSD.org) Message-Id: <200103210432.f2L4WNd21223@green.dyndns.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Tomoyuki Murakami Cc: freebsd-hackers@FreeBSD.org Subject: Re: OpenSSH 2.5.1 In-Reply-To: Message from Tomoyuki Murakami of "Wed, 21 Feb 2001 22:13:14 +0900." <20010221.221314.71106066.tomoyuki@pobox.com> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Mar 2001 23:32:23 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tomoyuki Murakami wrote: > > >>> In OpenSSH 2.5.1 > >>> I wrote: > > tomoyuki> > tomoyuki> http://www.c-wind.com/~tomo/230-250.diff.gz > correct url is > http://www.c-wind.com/~tomo/230-251.diff.gz > I'm very sorry for this. > > tomoyuki> - /usr/src/crypto/openssh diffs > tomoyuki> - MD5 (230-251.diff.gz) = 9ff326a90d1f0b6d2eb0f863defdc129 > > >>> In Re: OpenSSH 2.5.1 > >>> Peter Pentchev wrote: > > roam> I might be wrong, but I think that OpenSSH upgrades, just as upgrades > roam> for most software in src/contrib, are not handled with patches, but > roam> with imports on the vendor branch - then CVS examines the changes > roam> that the FreeBSD Project has made to the individual files, and tries > roam> to merge them into the newly imported version. > > OK. I could be so short-temperd or something. but, first of all, > I personally needed the working functions of OpenSSH's port forward > '-R' option. > > Thanks for your comment. Thanks for your effort. I'd like to know, can you diff from OpenSSH 2.5.1 to what you have now? That might really be able to help. Otherwise, if you want to maintain the port in some fashion... ;) -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 20:45:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 9517B37B71E for ; Tue, 20 Mar 2001 20:45:36 -0800 (PST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id NAA57784; Wed, 21 Mar 2001 13:48:42 +0900 (JST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Message-Id: <200103210448.NAA57784@shidahara1.planet.sci.kobe-u.ac.jp> To: Willem van Engen Cc: hackers@freebsd.org Subject: Re: driver: probe not called when smbus child In-reply-to: Your message of "Tue, 20 Mar 2001 16:50:09 +0100." <3AB77C31.8213C158@stack.nl> Date: Wed, 21 Mar 2001 13:48:42 +0900 From: Takanori Watanabe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3AB77C31.8213C158@stack.nl>, Willem van Engen $B$5$s$$$o$/(B: >I'm trying to write a module which should be a child of the smbus. >When I make the driver a child of the isa bus, identify, probe, >and attach functions are properly called. I use the following >code to do that: > DRIVER_MODULE(my, isa, my_driver, my_devclass, 0, 0); >But when I put it on the smbus using > DRIVER_MODULE(my, smbus, my_driver, my_devclass, 0, 0); >only identify is called. The identify function is as follows: > > static void > my_identify(driver_t *driver, device_t parent) > { > devclass_t dc; > device_t child; > > printf("my: my_identify called\n"); > dc = devclass_find("my"); > if (devclass_get_device(dc, 0)==NULL) { > child = BUS_ADD_CHILD(parent, 0, "my", -1); > } > } 'smbus' code do not have 'bus_add_child' method.So the BUS_ADD_CHILD call do not take effect. Call device_add_child(parent,"my",-1); or define bus_add_child method. And you will need to know grandparent device name to bind the device collectly.(Or should we need a way to get device attribute such as Mother board, Video Capture BitBang,Video Capture Cooked,VGA Card and etc.) Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 21:32:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id CD41837B71F for ; Tue, 20 Mar 2001 21:32:08 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2L31vO00905; Tue, 20 Mar 2001 19:01:59 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103210301.f2L31vO00905@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: thomas@cuivre.fr.eu.org Cc: freebsd-hackers@FreeBSD.org Subject: Re: SCSI-over-* hacks In-reply-to: Your message of "Mon, 19 Mar 2001 15:11:34 +0100." <20010319151134.A89803@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Mar 2001 19:01:57 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi hackers, > > Has anyone implemented/thought of implementing: > - a CAM transport for ATAPI devices; Yes. It's not a lot of work. > - a CAM transport for USB scanners; No; this wouldn't make much sense, since most USB scanners aren't SCSI devices. > - the Linux SCSI generic device (/dev/sg*)? We already have a far superior mechanism (/dev/pass*) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 21:32:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C0AAC37B71E for ; Tue, 20 Mar 2001 21:32:09 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2L30rO00891; Tue, 20 Mar 2001 19:00:58 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103210300.f2L30rO00891@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexey Dokuchaev Cc: freebsd-hackers@FreeBSD.org Subject: Re: Some PCI-related programming things In-reply-to: Your message of "Mon, 19 Mar 2001 16:23:35 +0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Mar 2001 19:00:53 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Under linux, PCI stuff is generally done thru set of pci* functions, while > > > under FreeBSD there are ioctls provided by pci driver. I've been doing > > > some code migration from linux to FreeBSD, and got thru most of it, except > > > for things like this one: > > > > You are probably doing something very wrong here, but rather than try to > > convince you to do it, right, I'll just answer your question. 8) > > Hey, that's not fair :-) I'd like to know how to do things the rigth way. You'll need to tell us what it is that you're actually doing, then, since it's hard to guess from a tiny snippet like that. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 21:32:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 04AE237B721 for ; Tue, 20 Mar 2001 21:32:10 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2L2pTO00741; Tue, 20 Mar 2001 18:51:31 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103210251.f2L2pTO00741@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Willem van Engen Cc: freebsd-hackers@FreeBSD.org Subject: Re: driver: probe not called when smbus child In-reply-to: Your message of "Tue, 20 Mar 2001 16:50:09 +0100." <3AB77C31.8213C158@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 Mar 2001 18:51:29 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm trying to write a module which should be a child of the smbus. The smbus probe/attach is broken; you're going to have to fix it before this code will work properly. 8( -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 23:16:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chopper.Poohsticks.ORG (chopper.poohsticks.org [63.227.60.73]) by hub.freebsd.org (Postfix) with ESMTP id 5702937B721; Tue, 20 Mar 2001 23:16:47 -0800 (PST) (envelope-from drew@chopper.Poohsticks.ORG) Received: from chopper.Poohsticks.ORG (drew@localhost.poohsticks.org [127.0.0.1]) by chopper.Poohsticks.ORG (8.10.1/8.10.1) with ESMTP id f2L7GjO02859; Wed, 21 Mar 2001 00:16:45 -0700 Message-Id: <200103210716.f2L7GjO02859@chopper.Poohsticks.ORG> To: Mike Smith Cc: thomas@cuivre.fr.eu.org, freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI-over-* hacks In-reply-to: Your message of "Tue, 20 Mar 2001 19:01:57 PST." <200103210301.f2L31vO00905@mass.dis.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2855.985159005.1@chopper.Poohsticks.ORG> Date: Wed, 21 Mar 2001 00:16:45 -0700 From: Drew Eckhardt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200103210301.f2L31vO00905@mass.dis.org>, msmith@FreeBSD.ORG writes: >> - the Linux SCSI generic device (/dev/sg*)? > >We already have a far superior mechanism (/dev/pass*) FWIW, The Linux /dev/sg was implemented as a simple way to send SCSI commands to media changer robots in an MO drive library for a medical imaging application, which found its way into the standard kernel becuase Linux is distributed under the GPL. -- Home Page For those who do, no explanation is necessary. For those who don't, no explanation is possible. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Mar 20 23:54:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 7C8D637B71B for ; Tue, 20 Mar 2001 23:54:43 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id CAA27566; Wed, 21 Mar 2001 02:54:40 -0500 (EST) Date: Wed, 21 Mar 2001 02:54:39 -0500 (EST) From: "Matthew N. Dodd" To: Willem van Engen Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: driver: probe not called when smbus child In-Reply-To: <3AB77C31.8213C158@stack.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Mar 2001, Willem van Engen wrote: > I'm trying to write a module which should be a child of the smbus. > When I make the driver a child of the isa bus, identify, probe, > and attach functions are properly called. I use the following > code to do that: > DRIVER_MODULE(my, isa, my_driver, my_devclass, 0, 0); > But when I put it on the smbus using > DRIVER_MODULE(my, smbus, my_driver, my_devclass, 0, 0); Shouldn't this be: DRIVER_MODULE(smbus, my, smbus_driver, smbus_devclass, 0, 0); -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 0:40:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from extreme.neko.tama.or.jp (extreme.neko.tama.or.jp [203.139.82.198]) by hub.freebsd.org (Postfix) with SMTP id D5DC837B718 for ; Wed, 21 Mar 2001 00:40:44 -0800 (PST) (envelope-from tomoyuki@pobox.com) Received: (qmail 29631 invoked from network); 21 Mar 2001 17:40:40 +0900 Received: from unknown (HELO localhost) (127.0.0.1) by localhost with SMTP; 21 Mar 2001 17:40:40 +0900 Date: Wed, 21 Mar 2001 17:40:40 +0900 (JST) Message-Id: <20010321.174040.41659770.tomoyuki@pobox.com> To: green@FreeBSD.org Cc: freebsd-hackers@FreeBSD.org Subject: Re: OpenSSH 2.5.1 From: Tomoyuki Murakami In-Reply-To: <200103210432.f2L4WNd21223@green.dyndns.org> References: <200103210432.f2L4WNd21223@green.dyndns.org> X-Mailer: Mew version 1.95b112 on XEmacs 21.1.12 (Channel Islands) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> In Re: OpenSSH 2.5.1 >>> "Brian F. Feldman" wrote: green> Thanks for your effort. I'd like to know, can you diff from OpenSSH 2.5.1 green> to what you have now? That might really be able to help. Otherwise, if you ok. I've made diffs(gzip-ed approx. 40k) to http://www.c-wind.com/~tomo/openssh-251-f251.diff.gz MD5 (openssh-251-f251.diff.gz) = 3f390bd40671f1e79e7734f20cf1cede I'll be glad if it helps. but, again, in this porting, I have not tested whole functions, including - SKEY or OPIE functions. - Kerberos4/5 functions. -- tomo. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 0:52:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id E15D237B719 for ; Wed, 21 Mar 2001 00:52:12 -0800 (PST) (envelope-from danfe@inet.ssc.nsu.ru) Received: (qmail 22357 invoked from network); 21 Mar 2001 08:52:07 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 21 Mar 2001 08:52:07 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id OAA14064; Wed, 21 Mar 2001 14:51:36 +0600 Date: Wed, 21 Mar 2001 14:51:34 +0600 (NOVT) From: Alexey Dokuchaev To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: Some PCI-related programming things In-Reply-To: <200103210300.f2L30rO00891@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Mar 2001, Mike Smith wrote: > > > > Under linux, PCI stuff is generally done thru set of pci* functions, while > > > > under FreeBSD there are ioctls provided by pci driver. I've been doing > > > > some code migration from linux to FreeBSD, and got thru most of it, except > > > > for things like this one: > > > > > > You are probably doing something very wrong here, but rather than try to > > > convince you to do it, right, I'll just answer your question. 8) > > > > Hey, that's not fair :-) I'd like to know how to do things the rigth way. > > You'll need to tell us what it is that you're actually doing, then, since > it's hard to guess from a tiny snippet like that. 8) Well, but if you didn't know, how could you tell that I'm doing something very wrong then? :-) I was porting (that is, it's not mine) some linux code that walks thru PCI bus, searches for a particular device, and when it finds any, figures out their parameters and fills some structures. This code is used, actually, in char device driver. -- Regs, Alexey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 1:10:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web4803.mail.yahoo.com (web4803.mail.yahoo.com [216.115.105.245]) by hub.freebsd.org (Postfix) with SMTP id A997937B71F for ; Wed, 21 Mar 2001 01:10:40 -0800 (PST) (envelope-from elahi1978@yahoo.com) Message-ID: <20010321091040.1818.qmail@web4803.mail.yahoo.com> Received: from [213.29.16.6] by web4803.mail.yahoo.com; Wed, 21 Mar 2001 01:10:40 PST Date: Wed, 21 Mar 2001 01:10:40 -0800 (PST) From: Masoud Elahi Reply-To: Admin@iol.co.ir Subject: Re: freebsd-hackers-digest V5 #71 To: hackers@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-hackers --- freebsd-hackers-digest wrote: > > freebsd-hackers-digest Wednesday, March 21 2001 > Volume 05 : Number 071 > > > > In this issue: > driver: probe not called when smbus child > Re: Routing latency > RE: Routing latency > RE: Routing latency > Re: Easy way to compute memory stats? (procfs?) > kernel panic > tuning a VERY heavily (30.0) loaded server > Re: kernel panic > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded scerver > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded scerver > Re: tuning a VERY heavily (30.0) loaded scerver > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded scerver > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded scerver > Re: tuning a VERY heavily (30.0) loaded scerver > Re: tuning a VERY heavily (30.0) loaded scerver > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded scerver > apache truss readings > Re: tuning a VERY heavily (30.0) loaded scerver > Re: tuning a VERY heavily (30.0) loaded scerver > Re: apache truss readings > Re: any decently supported scanner around ? > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded server > Re: tuning a VERY heavily (30.0) loaded scerver > Question regarding the array of size 0. > Re: tuning a VERY heavily (30.0) loaded scerver > Re: Question regarding the array of size 0. > Re: tuning a VERY heavily (30.0) loaded server > Re: Question regarding the array of size 0. > Re: Question regarding the array of size 0. > Re: Question regarding the array of size 0. > Re: Question regarding the array of size 0. > Re: Question regarding the array of size 0. > Re: Question regarding the array of size 0. > Re: Question regarding the array of size 0. > Re: Question regarding the array of size 0. > Re: Question regarding the array of size 0. > Re: device driver dev. book > Re: tuning a VERY heavily (30.0) loaded server > Re: GCC Upgrade? > Re: GCC Upgrade? > Re: tuning a VERY heavily (30.0) loaded server > Re: apache truss readings > Re: Question regarding the array of size 0. > Re: Question regarding the array of size 0. > Re: Debuging kernel crashes > Re: GCC Upgrade? > Re: kernel panic > Re: Question regarding the array of size 0. > Re: driver: probe not called when smbus child > Re: GCC Upgrade? > Re: Debuging kernel crashes > gzip's custom i386 asm should be disabled > Re: gzip's custom i386 asm should be disabled > Re: OpenSSH 2.5.1 > Re: driver: probe not called when smbus child > Re: SCSI-over-* hacks > Re: Some PCI-related programming things > Re: driver: probe not called when smbus child > Re: SCSI-over-* hacks > Re: driver: probe not called when smbus child > Re: OpenSSH 2.5.1 > Re: Some PCI-related programming things > > ---------------------------------------------------------------------- > > Date: Tue, 20 Mar 2001 16:50:09 +0100 > From: Willem van Engen > Subject: driver: probe not called when smbus child > > I'm trying to write a module which should be a child > of the smbus. > When I make the driver a child of the isa bus, > identify, probe, > and attach functions are properly called. I use the > following > code to do that: > DRIVER_MODULE(my, isa, my_driver, my_devclass, 0, > 0); > But when I put it on the smbus using > DRIVER_MODULE(my, smbus, my_driver, my_devclass, > 0, 0); > only identify is called. The identify function is as > follows: > > static void > my_identify(driver_t *driver, device_t parent) > { > devclass_t dc; > device_t child; > > printf("my: my_identify called\n"); > dc = devclass_find("my"); > if (devclass_get_device(dc, 0)==NULL) { > child = BUS_ADD_CHILD(parent, 0, "my", > -1); > } > } > > The driver only uses smbus calls, so I think the > best parent > would be smbus. > And when I do a smbus_request_bus, the call waits > forever as > it seems. That seems sensible to me, because it asks > the > parent for the bus and the isa bus can't grant > requests for > the smbus. So I think the driver has to be a child > of the smbus. > > Looking in the kernel sources, I see that the only > smbus child > I can find, smb, (if there are others, I'm certainly > interested) > is attached in the smbus code itself. So the next > question rises: > Is it possible to have an smbus child in a > dynamically loadable > module (I can't find smbus.ko in /modules, so > loading the child > first and then smbus isn't an option I guess) ? > > - - Willem van Engen > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of > the message > > ------------------------------ > > Date: Tue, 20 Mar 2001 11:46:15 -0500 > From: Dennis > Subject: Re: Routing latency > > At 02:43 AM 03/20/2001, you wrote: > > > > I'm using the de driver. Alas, the NICs seems > quite old. They are > > 21140's. > > > > I've only got one 21143. I think there is a > 3COM 3c905b in the lab too. > > > > Would it be better to use the 21143 + 3com > than two 21140s? > > > > > > definitely : in my packet blaster, I get an > order of magnitude less > > > packet drops with a 3c905 than with a dc NIC > (which is on a multi-port > > > NIC : the PCI-PCI bridge may be a hindrance > there) > > > >not my experience -- with the 21143 i can blast > 140kpacket/s > >and receive them with no problems. > >For sure the "de" driver might have its own > problems, > >but i think a lot of packet drops also depend on > the card > >not being properly set for full duplex (which can > >cause collisions and lots of drops). > > > You should initially test mono-directional in a > controlled environment to > avoid "collisions" to compare the true efficiency of > the driver. > > dennis > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of > the message > > ------------------------------ > > Date: Tue, 20 Mar 2001 11:50:53 -0500 > From: Dennis > Subject: RE: Routing latency > > At 02:04 AM 03/20/2001, M=E5rten Wikstr=F6m wrote: > > >[snip] > === message truncated === __________________________________________________ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 1:18:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 66B1137B721 for ; Wed, 21 Mar 2001 01:18:18 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2L9FG502274; Wed, 21 Mar 2001 01:15:16 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103210915.f2L9FG502274@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexey Dokuchaev Cc: freebsd-hackers@freebsd.org Subject: Re: Some PCI-related programming things In-reply-to: Your message of "Wed, 21 Mar 2001 14:51:34 +0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Mar 2001 01:15:16 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Hey, that's not fair :-) I'd like to know how to do things the rigth way. > > > > You'll need to tell us what it is that you're actually doing, then, since > > it's hard to guess from a tiny snippet like that. 8) > > Well, but if you didn't know, how could you tell that I'm doing something > very wrong then? :-) Because dinking with PCI configuration space is usually the wrong thing to do from userland. > I was porting (that is, it's not mine) some linux code that walks thru PCI > bus, searches for a particular device, and when it finds any, figures out > their parameters and fills some structures. > > This code is used, actually, in char device driver. Mm, so what's it doing in userspace? 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 1:26:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id E9D7A37B723 for ; Wed, 21 Mar 2001 01:26:04 -0800 (PST) (envelope-from danfe@inet.ssc.nsu.ru) Received: (qmail 22599 invoked from network); 21 Mar 2001 09:25:54 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 21 Mar 2001 09:25:54 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id PAA16266; Wed, 21 Mar 2001 15:25:35 +0600 Date: Wed, 21 Mar 2001 15:25:34 +0600 (NOVT) From: Alexey Dokuchaev To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: Some PCI-related programming things In-Reply-To: <200103210915.f2L9FG502274@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Mar 2001, Mike Smith wrote: > > > > Hey, that's not fair :-) I'd like to know how to do things the rigth way. > > > > > > You'll need to tell us what it is that you're actually doing, then, since > > > it's hard to guess from a tiny snippet like that. 8) > > > > Well, but if you didn't know, how could you tell that I'm doing something > > very wrong then? :-) > > Because dinking with PCI configuration space is usually the wrong thing > to do from userland. So what about pciconf(8)? > > > I was porting (that is, it's not mine) some linux code that walks thru PCI > > bus, searches for a particular device, and when it finds any, figures out > > their parameters and fills some structures. > > > > This code is used, actually, in char device driver. > > Mm, so what's it doing in userspace? 8) Did I say I'm doing it from userspace?! If I did (too lazy to dig into sent-mail), I beg your pardon :) -- Rgs, Alexey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 1:53: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from melusine.cuivre.fr.eu.org (ppp15-net1-idf3-bas1.isdnet.net [195.154.52.15]) by hub.freebsd.org (Postfix) with ESMTP id 4D27337B742; Wed, 21 Mar 2001 01:53:00 -0800 (PST) (envelope-from thomas@cuivre.fr.eu.org) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id 8CA9324D02; Wed, 21 Mar 2001 10:52:50 +0100 (CET) Date: Wed, 21 Mar 2001 10:52:50 +0100 From: Thomas Quinot To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: SCSI-over-* hacks Message-ID: <20010321105250.A35328@melusine.cuivre.fr.eu.org> Reply-To: thomas@cuivre.fr.eu.org References: <20010319151134.A89803@melusine.cuivre.fr.eu.org> <200103210301.f2L31vO00905@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200103210301.f2L31vO00905@mass.dis.org>; from msmith@freebsd.org on Tue, Mar 20, 2001 at 07:01:57PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Le 2001-03-21, Mike Smith écrivait : > > Has anyone implemented/thought of implementing: > > - a CAM transport for ATAPI devices; > Yes. It's not a lot of work. Ah, interesting! Do you know if any source code is publicly available? > > - a CAM transport for USB scanners; > No; this wouldn't make much sense, since most USB scanners aren't SCSI > devices. Mine (Minolta Dimâge Scan Dual II, an Avision unit in disguise) is :) > > - the Linux SCSI generic device (/dev/sg*)? > We already have a far superior mechanism (/dev/pass*) Think 'Linux binary-only software'... Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 2: 4:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id EB0AA37B744 for ; Wed, 21 Mar 2001 02:04:27 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2LA1g502649; Wed, 21 Mar 2001 02:01:43 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103211001.f2LA1g502649@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: thomas@cuivre.fr.eu.org Cc: freebsd-hackers@freebsd.org Subject: Re: SCSI-over-* hacks In-reply-to: Your message of "Wed, 21 Mar 2001 10:52:50 +0100." <20010321105250.A35328@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Wed, 21 Mar 2001 02:01:42 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Le 2001-03-21, Mike Smith =E9crivait : > = > > > Has anyone implemented/thought of implementing: > > > - a CAM transport for ATAPI devices; > > Yes. It's not a lot of work. > = > Ah, interesting! Do you know if any source code is publicly available? No, for various reasons it hasn't been done; primarily, the FreeBSD ATA = maintainer doesn't consider it worthwhile. > > > - a CAM transport for USB scanners; > > No; this wouldn't make much sense, since most USB scanners aren't SCS= I = > > devices. > > Mine (Minolta Dim=E2ge Scan Dual II, an Avision unit in disguise) is :)= Think about it for a moment. SCSI is way of encapsulating scanner commands so that you can transport = them to the scanner. So is USB. The command set your scanner uses is = probably the same as the SCSI command set, but this is not what a CAM = transport would give you - it would only give you the layers beneath, = which would not be useful, since you already have this in the form of USB= =2E > > > - the Linux SCSI generic device (/dev/sg*)? > > We already have a far superior mechanism (/dev/pass*) > = > Think 'Linux binary-only software'... Think "barfing up a prime rib, plus all the vegetables and gravy". 8) -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 2: 4:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 2D4A037B747; Wed, 21 Mar 2001 02:04:51 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA23672; Wed, 21 Mar 2001 11:03:11 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103211003.LAA23672@freebsd.dk> Subject: Re: SCSI-over-* hacks In-Reply-To: <20010321105250.A35328@melusine.cuivre.fr.eu.org> from Thomas Quinot at "Mar 21, 2001 10:52:50 am" To: thomas@cuivre.fr.eu.org Date: Wed, 21 Mar 2001 11:03:11 +0100 (CET) Cc: msmith@FreeBSD.ORG (Mike Smith), freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Thomas Quinot wrote: > Le 2001-03-21, Mike Smith écrivait : > > > > Has anyone implemented/thought of implementing: > > > - a CAM transport for ATAPI devices; > > Yes. It's not a lot of work. > > Ah, interesting! Do you know if any source code is publicly available? What do you want it for actually ? I've played with it loooong ago and tossed it due to performance and loss of features compared to the ATAPI subsystem... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 2:32: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from melusine.cuivre.fr.eu.org (ppp15-net1-idf3-bas1.isdnet.net [195.154.52.15]) by hub.freebsd.org (Postfix) with ESMTP id 3719637B71A for ; Wed, 21 Mar 2001 02:32:06 -0800 (PST) (envelope-from thomas@cuivre.fr.eu.org) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id 30E1424D02; Wed, 21 Mar 2001 11:28:35 +0100 (CET) Date: Wed, 21 Mar 2001 11:28:35 +0100 From: Thomas Quinot To: Soren Schmidt Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI-over-* hacks Message-ID: <20010321112835.A37126@melusine.cuivre.fr.eu.org> Reply-To: thomas@cuivre.fr.eu.org References: <20010321105250.A35328@melusine.cuivre.fr.eu.org> <200103211003.LAA23672@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200103211003.LAA23672@freebsd.dk>; from sos@freebsd.dk on Wed, Mar 21, 2001 at 11:03:11AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Le 2001-03-21, Soren Schmidt écrivait : > > > > - a CAM transport for ATAPI devices; > What do you want it for actually ? It is a possible solution for me to be able to use cdparanoia and cdrdao with my ATAPI CD drive. An alternative solution would be to implement an atapi-cd ioctl to send a raw command to an ATAPI device, and make libscg use that. Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 2:37:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from melusine.cuivre.fr.eu.org (ppp15-net1-idf3-bas1.isdnet.net [195.154.52.15]) by hub.freebsd.org (Postfix) with ESMTP id 4214337B71B; Wed, 21 Mar 2001 02:37:37 -0800 (PST) (envelope-from thomas@cuivre.fr.eu.org) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id 9B35F24D02; Wed, 21 Mar 2001 11:32:39 +0100 (CET) Date: Wed, 21 Mar 2001 11:32:39 +0100 From: Thomas Quinot To: Mike Smith Cc: thomas@cuivre.fr.eu.org, freebsd-hackers@freebsd.org Subject: Re: SCSI-over-* hacks Message-ID: <20010321113239.B37126@melusine.cuivre.fr.eu.org> Reply-To: thomas@cuivre.fr.eu.org References: <20010321105250.A35328@melusine.cuivre.fr.eu.org> <200103211001.f2LA1g502649@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <200103211001.f2LA1g502649@mass.dis.org>; from msmith@freebsd.org on Wed, Mar 21, 2001 at 02:01:42AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Le 2001-03-21, Mike Smith écrivait : > SCSI is way of encapsulating scanner commands so that you can transport > them to the scanner. So is USB. The command set your scanner uses is > probably the same as the SCSI command set, but this is not what a CAM > transport would give you - it would only give you the layers beneath, > which would not be useful, since you already have this in the form of USB. Um. The CAM tranport in question would not be a reimplementation of the USB layer, of course. What I was mentioning was the possibility of having a CAM transport that wraps a uscan device (just as there is one already that wraps umass devices to make them appear as SCSI disks). This would allow all USB scanners that use an SCSI command set to be accessible through pass*, and thus be supported by any scanning software that can use a SCSI scanner. Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 2:52: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id C954D37B71F for ; Wed, 21 Mar 2001 02:51:59 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA35280; Wed, 21 Mar 2001 11:48:01 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103211048.LAA35280@freebsd.dk> Subject: Re: SCSI-over-* hacks In-Reply-To: <20010321112835.A37126@melusine.cuivre.fr.eu.org> from Thomas Quinot at "Mar 21, 2001 11:28:35 am" To: thomas@cuivre.fr.eu.org Date: Wed, 21 Mar 2001 11:48:01 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Thomas Quinot wrote: > Le 2001-03-21, Soren Schmidt écrivait : > > > > > > - a CAM transport for ATAPI devices; > > > What do you want it for actually ? > > It is a possible solution for me to be able to use cdparanoia and cdrdao > with my ATAPI CD drive. An alternative solution would be to implement > an atapi-cd ioctl to send a raw command to an ATAPI device, and make > libscg use that. Exactly, I coule dream up an API for that shoving ATAPI commands into the ATA driver, that would make at least some sense... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 3: 6:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.iinet.net.au (symphony-02.iinet.net.au [203.59.24.17]) by hub.freebsd.org (Postfix) with SMTP id C672A37B724 for ; Wed, 21 Mar 2001 03:06:04 -0800 (PST) (envelope-from julian@elischer.org) Received: (qmail 7739 invoked by uid 666); 21 Mar 2001 11:05:58 -0000 Received: from unknown (HELO elischer.org) (203.59.78.139) by mail.iinet.net.au with SMTP; 21 Mar 2001 11:05:58 -0000 Message-ID: <3AB87A5A.69562D89@elischer.org> Date: Wed, 21 Mar 2001 01:54:34 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Peter Seebach Cc: tech-kern@netbsd.org, bsd hackers Subject: Re: Question regarding the array of size 0. References: <200103201903.f2KJ3LO16883@guild.plethora.net> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Seebach wrote: > > In message <3AB7A76B.2BCF5D6E@net.com>, Shankar Agarwal writes: > >Can someone pls tell me if it is possible to define an array of size 0. > > Not in C. GCC and most other compilers support it. I do it all the time (see all the various netgraph structures) however it must be the LAST item in the structure. It gives the address of the first byte AFTER the structure. This is very useful if the structure is a header of some sort. > > -s > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000-2001 ---> X_.---._/ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 3:13:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id 8C3C537B72E; Wed, 21 Mar 2001 03:13:45 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.11.3/8.9.3) with ESMTP id f2LBDQi06370; Wed, 21 Mar 2001 21:43:26 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010321113239.B37126@melusine.cuivre.fr.eu.org> Date: Wed, 21 Mar 2001 21:42:09 +1030 (CST) From: "Daniel O'Connor" To: Thomas Quinot Subject: Re: SCSI-over-* hacks Cc: freebsd-hackers@freebsd.org, Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Mar-01 Thomas Quinot wrote: > Um. The CAM tranport in question would not be a reimplementation of > the USB layer, of course. What I was mentioning was the possibility > of having a CAM transport that wraps a uscan device (just as there is > one already that wraps umass devices to make them appear as SCSI disks). Well, SANE grok's SCSI and USB transports for the same underlying commands.. For example it uses the same code to talk to a parallel and USB HP ScanJet 5400C.. > This would allow all USB scanners that use an SCSI command set to be > accessible through pass*, and thus be supported by any scanning software > that can use a SCSI scanner. If scanners supported SCSI they'd be umass devices, generally they're not, you attach uscanner to them and then feed them to SANE. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 3:14:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 67FE137B72E; Wed, 21 Mar 2001 03:14:14 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from mobile.wemm.org (mobile.wemm.org [10.0.0.5]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f2LBEEp89135; Wed, 21 Mar 2001 03:14:14 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f2LBE0h57371; Wed, 21 Mar 2001 03:14:04 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200103211114.f2LBE0h57371@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Matt Dillon Cc: Alfred Perlstein , "Michael C . Wu" , "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver In-Reply-To: <200103201852.f2KIquW95665@earth.backplane.com> Date: Wed, 21 Mar 2001 03:13:59 -0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon wrote: > :If this is a result of the shared memory, then my sysctl should fix it. > : > :Be aware, that it doesn't fix it on the fly! You must drop and recreate > :the shared memory segments. > : > :better to reboot actually and set the variable before any shm is > :allocated. > : > :-- > :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > > Lets see. Approximately 4MB shared across 4000 processes. That eats > 1024 pte's per process, or around 4 million pmap elements that would be > saved. That's a lot of KVM that would be saved. Also, 4MB = 1024 pages, at 28 bytes per mapping == 28k per process. 28k * 4000 processes = 114688k of kvm, ie: 114MB of kvm. I bet you'll find that you are right on the limit, and you are seeing lots of page unwiring by the page daemon to try and stop it running out of pv entries. Do you see messages on the console saying that pmap_collect got activated? Do a sysctl vm.zone (or vmstat -z) and see the entry for 'PV ENTRY'. vmstat -z is different to vm.zone on 4.x, but somebody broke it on -current so that you cannot use it on crashdumps anymore. :-( GRRRRR! You can increase PMAP_SHPGPERPROC (kernel compile option). Or use the sysctl to use physical memory backed shm mappings, which do not consume pv_entries for each page per process. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 3:47:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from amsmta04-svc.chello.nl (mail-out.chello.nl [213.46.240.7]) by hub.freebsd.org (Postfix) with ESMTP id 07C1437B732 for ; Wed, 21 Mar 2001 03:47:35 -0800 (PST) (envelope-from wvengen@stack.nl) Received: from stack.nl ([213.46.110.240]) by amsmta04-svc.chello.nl (InterMail vK.4.03.02.00 201-232-124 license 9a0f3c09abb1b740b3b0b1917e20d81c) with ESMTP id <20010321114457.FAD11230.amsmta04-svc@stack.nl>; Wed, 21 Mar 2001 12:44:57 +0100 Message-ID: <3AB8936D.887833B3@stack.nl> Date: Wed, 21 Mar 2001 12:41:33 +0100 From: Willem van Engen X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew N. Dodd" , freebsd-hackers@freebsd.org Subject: Re: driver: probe not called when smbus child References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > > On Tue, 20 Mar 2001, Willem van Engen wrote: > > > I'm trying to write a module which should be a child of the smbus. > > When I make the driver a child of the isa bus, identify, probe, > > and attach functions are properly called. I use the following > > code to do that: > > DRIVER_MODULE(my, isa, my_driver, my_devclass, 0, 0); > > But when I put it on the smbus using > > DRIVER_MODULE(my, smbus, my_driver, my_devclass, 0, 0); > > Shouldn't this be: > > DRIVER_MODULE(smbus, my, smbus_driver, smbus_devclass, 0, 0); the DRIVER_MODULE(9) manual says DRIVER_MODULE(name, busname, driver_t driver, devclass_t devclass, int (*evh) (struct module *, int, void *), void *arg) and the smb device uses the following: DRIVER_MODULE(smb, smbus, smb_driver, smb_devclass, 0, 0); so I guess not. But thanks anyway :) - Willem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 3:51:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id C4D6537B737 for ; Wed, 21 Mar 2001 03:51:43 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 21 Mar 2001 11:48:37 +0000 (GMT) Date: Wed, 21 Mar 2001 11:48:32 +0000 From: David Malone To: Matthew Emmerton Cc: Aaron Smith , freebsd-hackers@FreeBSD.ORG, jon@csua.berkeley.edu, breadbox@muppetlabs.com Subject: Re: gzip's custom i386 asm should be disabled Message-ID: <20010321114832.A31809@walton.maths.tcd.ie> References: <20010320174630.B82004@gelatinous.com> <017d01c0b1ab$df4be1b0$1200a8c0@gsicomp.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <017d01c0b1ab$df4be1b0$1200a8c0@gsicomp.on.ca>; from matt@gsicomp.on.ca.emmerton.org on Tue, Mar 20, 2001 at 09:08:49PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 09:08:49PM -0500, Matthew Emmerton wrote: > > Since I would imagine a large percentage of FreeBSD users run on i686 > > cores, it'd be great to get this pretty significant speed increase into > our > > tree. > > I sure hope I'm not the only one with a "lab" of 4 FreeBSD machines that are > all 486s or 586s. You may find that the 686 assembly is as fast on a 386/486/586 as the old assembly is. Maybe you could test it and let the list know? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 3:52:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 4025537B732 for ; Wed, 21 Mar 2001 03:52:52 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id GAA30439; Wed, 21 Mar 2001 06:51:43 -0500 (EST) Date: Wed, 21 Mar 2001 06:51:42 -0500 (EST) From: "Matthew N. Dodd" To: Willem van Engen Cc: freebsd-hackers@freebsd.org Subject: Re: driver: probe not called when smbus child In-Reply-To: <3AB8936D.887833B3@stack.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Mar 2001, Willem van Engen wrote: > DRIVER_MODULE(smb, smbus, smb_driver, smb_devclass, 0, 0); > so I guess not. But thanks anyway :) Yes, but the 'smbus' bus driver doesn't have an attachment to your driver. You're trying to create a device that provides an 'smbus' right? Or did I totally misread your original post? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 4:39:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.newst.irs.ru (newst.irs.ru [212.164.94.1]) by hub.freebsd.org (Postfix) with ESMTP id DFD5537B721; Wed, 21 Mar 2001 04:39:54 -0800 (PST) (envelope-from fjoe@newst.net) Received: from lark.nsk.bsgdesign.com (lark.nsk.bsgdesign.com [192.168.3.21]) by mail.newst.irs.ru (8.11.1/8.11.0) with ESMTP id f2LCdlh89824; Wed, 21 Mar 2001 18:39:48 +0600 (NOVT) (envelope-from fjoe@newst.net) Date: Wed, 21 Mar 2001 18:39:47 +0600 (NOVT) From: Max Khon X-Sender: fjoe@localhost To: "Alexander N. Kabaev" Cc: "David O'Brien" , hackers@FreeBSD.ORG, Titus von Boxberg Subject: Re: GCC Upgrade? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 20 Mar 2001, Alexander N. Kabaev wrote: > > It will happen right after I MFC GCC 2.95.3. DWARF2 is required by the > > IA-64 psABI, and is supported better on the Alpha. > > It will be so nice to finally leave these sjlj exceptions problems behind. Btw, do you have patches that fix sjlj exceptions for 2.95.3? At this time we use 4.2-STABLE + gcc 2.95.2 + your fixes for sjlj in 2.95.2 for C++ development. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 4:43:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.newst.irs.ru (newst.irs.ru [212.164.94.1]) by hub.freebsd.org (Postfix) with ESMTP id 9BC0B37B731; Wed, 21 Mar 2001 04:43:13 -0800 (PST) (envelope-from fjoe@newst.net) Received: from lark.nsk.bsgdesign.com (lark.nsk.bsgdesign.com [192.168.3.21]) by mail.newst.irs.ru (8.11.1/8.11.0) with ESMTP id f2LCgGh89970; Wed, 21 Mar 2001 18:42:17 +0600 (NOVT) (envelope-from fjoe@newst.net) Date: Wed, 21 Mar 2001 18:42:16 +0600 (NOVT) From: Max Khon X-Sender: fjoe@localhost To: Mike Smith Cc: thomas@cuivre.fr.eu.org, freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI-over-* hacks In-Reply-To: <200103210301.f2L31vO00905@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 20 Mar 2001, Mike Smith wrote: > > Has anyone implemented/thought of implementing: > > - a CAM transport for ATAPI devices; > > Yes. It's not a lot of work. that would be GREAT for cd recording on IDE CD-RW (one will be able to use cdrdao and cdrecord instead of burncd) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 5: 6:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6.port.ru (mx6.port.ru [194.67.23.42]) by hub.freebsd.org (Postfix) with ESMTP id 4F6A137B73F for ; Wed, 21 Mar 2001 05:06:29 -0800 (PST) (envelope-from kabaev@mail.ru) Received: from adsl-151-203-116-69.bostma.adsl.bellatlantic.net ([151.203.116.69] helo=kan.dnsalias.net) by smtp6.port.ru with esmtp (Exim 3.14 #43) id 14fiHm-0007La-00; Wed, 21 Mar 2001 16:04:23 +0300 Received: (from kan@localhost) by kan.dnsalias.net (8.11.3/8.11.3) id f2LD49k22296; Wed, 21 Mar 2001 08:04:09 -0500 (EST) (envelope-from kan) Message-ID: X-Mailer: XFMail 1.4.7p2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 21 Mar 2001 08:04:08 -0500 (EST) From: "Alexander N. Kabaev" To: Max Khon Subject: Re: GCC Upgrade? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My fixes or fixes ported by me from gcc-devel branch? I have both. Let me know if you need them. GCC 2.95.3 is not MFCed yet, so there is no hurry. > Btw, do you have patches that fix sjlj exceptions for 2.95.3? > At this time we use 4.2-STABLE + gcc 2.95.2 + your fixes for sjlj in > 2.95.2 for C++ development. > > /fjoe ---------------------------------- E-Mail: Alexander N. Kabaev Date: 21-Mar-2001 Time: 07:58:37 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 5:26:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from amsmta04-svc.chello.nl (mail-out.chello.nl [213.46.240.7]) by hub.freebsd.org (Postfix) with ESMTP id C332F37B71E for ; Wed, 21 Mar 2001 05:26:44 -0800 (PST) (envelope-from wvengen@stack.nl) Received: from stack.nl ([213.46.110.240]) by amsmta04-svc.chello.nl (InterMail vK.4.03.02.00 201-232-124 license 9a0f3c09abb1b740b3b0b1917e20d81c) with ESMTP id <20010321131940.BEDG11230.amsmta04-svc@stack.nl>; Wed, 21 Mar 2001 14:19:40 +0100 Message-ID: <3AB8A9A0.3A35227E@stack.nl> Date: Wed, 21 Mar 2001 14:16:16 +0100 From: Willem van Engen X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Takanori Watanabe , freebsd-hackers@freebsd.org Subject: Re: driver: probe not called when smbus child References: <200103210448.NAA57784@shidahara1.planet.sci.kobe-u.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Takanori Watanabe wrote: > > In message <3AB77C31.8213C158@stack.nl>, Willem van Engen $B$5$s$$$o$/(B: > >I'm trying to write a module which should be a child of the smbus. > >When I make the driver a child of the isa bus, identify, probe, > >and attach functions are properly called. I use the following > >code to do that: > > DRIVER_MODULE(my, isa, my_driver, my_devclass, 0, 0); > >But when I put it on the smbus using > > DRIVER_MODULE(my, smbus, my_driver, my_devclass, 0, 0); > >only identify is called. The identify function is as follows: > > > > static void > > my_identify(driver_t *driver, device_t parent) > > { > > devclass_t dc; > > device_t child; > > > > printf("my: my_identify called\n"); > > dc = devclass_find("my"); > > if (devclass_get_device(dc, 0)==NULL) { > > child = BUS_ADD_CHILD(parent, 0, "my", -1); > > } > > } > > 'smbus' code do not have 'bus_add_child' method.So the BUS_ADD_CHILD > call do not take effect. > Call device_add_child(parent,"my",-1); or define bus_add_child method. I'm now using the above device_add_child and it works. It gets attached to smbus0 and the smbus_attach,detach,readw and writew commands work (probabely others too, but I only use these). Thanks! > > And you will need to know grandparent device name to bind the device > collectly.(Or should we need a way to get device attribute such as > Mother board, Video Capture BitBang,Video Capture Cooked,VGA Card and etc.) I don't quite understand this; I guess I don't know enough about newbus or so. > > Takanori Watanabe > > Public Key > Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A - Willem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 5:33:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from eidolon.muppetlabs.com (eidolon.muppetlabs.com [216.231.41.85]) by hub.freebsd.org (Postfix) with ESMTP id 45BCB37B719 for ; Wed, 21 Mar 2001 05:33:31 -0800 (PST) (envelope-from breadbox@eidolon.muppetlabs.com) Received: (from breadbox@localhost) by eidolon.muppetlabs.com (8.9.3/8.9.3) id FAA07031; Wed, 21 Mar 2001 05:28:52 -0800 Date: Wed, 21 Mar 2001 05:28:52 -0800 Message-Id: <200103211328.FAA07031@eidolon.muppetlabs.com> From: Brian Raiter To: David Malone Cc: Matthew Emmerton , Aaron Smith , freebsd-hackers@FreeBSD.ORG, jon@csua.berkeley.edu Subject: Re: gzip's custom i386 asm should be disabled In-Reply-To: <20010321114832.A31809@walton.maths.tcd.ie> References: <20010320174630.B82004@gelatinous.com> <017d01c0b1ab$df4be1b0$1200a8c0@gsicomp.on.ca> <20010321114832.A31809@walton.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Since I would imagine a large percentage of FreeBSD users run on >>> i686 cores, it'd be great to get this pretty significant speed >>> increase into our tree. >> >> I sure hope I'm not the only one with a "lab" of 4 FreeBSD machines >> that are all 486s or 586s. > > You may find that the 686 assembly is as fast on a 386/486/586 as > the old assembly is. Maybe you could test it and let the list know? Possibly, but my guess would be no. My 586 patch will probably outdo my 686 patch when run on a 486. The latter uses "movzx" in place of a simple "and" in order to avoid the partial register stall, which will be slower on the 486. In fact, the C compiler, if optimizing specifically for the 486, might be better than either of my patches. The gzip encoder is much more memory-bound than CPU-bound, so it's really hard to squeeze any speed out of the algorithm. Code that's targeted for the wrong Intel chip will probably lose out. (Back in 1998 when I created those patches, I wanted to make a third one specifically for the 486, but by then I didn't have access to a working 486 machine. I had some ideas written down on paper, but I didn't feel comfortable proceeding without any way to test them out.) b To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 6:14:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id C946437B72E for ; Wed, 21 Mar 2001 06:14:25 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f2LECYb91455; Wed, 21 Mar 2001 09:12:34 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <006101c0b210$c400edf0$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "David Malone" , "Matthew Emmerton" Cc: "Aaron Smith" , , , References: <20010320174630.B82004@gelatinous.com> <017d01c0b1ab$df4be1b0$1200a8c0@gsicomp.on.ca> <20010321114832.A31809@walton.maths.tcd.ie> Subject: Re: gzip's custom i386 asm should be disabled Date: Wed, 21 Mar 2001 09:11:03 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I sure hope I'm not the only one with a "lab" of 4 FreeBSD machines that are > > all 486s or 586s. > > You may find that the 686 assembly is as fast on a 386/486/586 as > the old assembly is. Maybe you could test it and let the list know? I was under the impression that the 586/686 code uses instructions that are not present on 386/486 machines, so I doubt that it would help. -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 6:21:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from eidolon.muppetlabs.com (eidolon.muppetlabs.com [216.231.41.85]) by hub.freebsd.org (Postfix) with ESMTP id 324DE37B726 for ; Wed, 21 Mar 2001 06:21:31 -0800 (PST) (envelope-from breadbox@eidolon.muppetlabs.com) Received: (from breadbox@localhost) by eidolon.muppetlabs.com (8.9.3/8.9.3) id GAA07389; Wed, 21 Mar 2001 06:21:14 -0800 Date: Wed, 21 Mar 2001 06:21:14 -0800 Message-Id: <200103211421.GAA07389@eidolon.muppetlabs.com> From: Brian Raiter To: "Matthew Emmerton" Cc: "David Malone" , "Aaron Smith" , , Subject: Re: gzip's custom i386 asm should be disabled In-Reply-To: <006101c0b210$c400edf0$1200a8c0@gsicomp.on.ca> References: <20010320174630.B82004@gelatinous.com> <017d01c0b1ab$df4be1b0$1200a8c0@gsicomp.on.ca> <20010321114832.A31809@walton.maths.tcd.ie> <006101c0b210$c400edf0$1200a8c0@gsicomp.on.ca> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> I sure hope I'm not the only one with a "lab" of 4 FreeBSD >>> machines that are all 486s or 586s. >> >> You may find that the 686 assembly is as fast on a 386/486/586 as >> the old assembly is. Maybe you could test it and let the list know? > > I was under the impression that the 586/686 code uses instructions > that are not present on 386/486 machines, so I doubt that it would > help. Bite your tongue! The youngest instruction in my patches is movzx, which was introduced with the 386. b To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 6:29: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id B258A37B738 for ; Wed, 21 Mar 2001 06:29:02 -0800 (PST) (envelope-from matt@gsicomp.on.ca) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.11.1/8.11.3) with SMTP id f2LERE591511; Wed, 21 Mar 2001 09:27:14 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <009d01c0b212$d0626a40$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Brian Raiter" Cc: References: <20010320174630.B82004@gelatinous.com><017d01c0b1ab$df4be1b0$1200a8c0@gsicomp.on.ca><20010321114832.A31809@walton.maths.tcd.ie><006101c0b210$c400edf0$1200a8c0@gsicomp.on.ca> <200103211421.GAA07389@eidolon.muppetlabs.com> Subject: Re: gzip's custom i386 asm should be disabled Date: Wed, 21 Mar 2001 09:25:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>> I sure hope I'm not the only one with a "lab" of 4 FreeBSD > >>> machines that are all 486s or 586s. > >> > >> You may find that the 686 assembly is as fast on a 386/486/586 as > >> the old assembly is. Maybe you could test it and let the list know? > > > > I was under the impression that the 586/686 code uses instructions > > that are not present on 386/486 machines, so I doubt that it would > > help. > > Bite your tongue! The youngest instruction in my patches is movzx, > which was introduced with the 386. Serves me right for not looking at the patches (no thanks to my flaky cable connection.) My bad assumption that code optimized for 586/686 would be 586/686-specific. I'll go away now :) -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 7: 8:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id B793537B71A for ; Wed, 21 Mar 2001 07:08:34 -0800 (PST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id AAA61574; Thu, 22 Mar 2001 00:08:38 +0900 (JST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Message-Id: <200103211508.AAA61574@shidahara1.planet.sci.kobe-u.ac.jp> To: Willem van Engen Cc: hackers@FreeBSD.org Subject: Re: driver: probe not called when smbus child In-reply-to: Your message of "Wed, 21 Mar 2001 14:16:16 +0100." <3AB8A9A0.3A35227E@stack.nl> Date: Thu, 22 Mar 2001 00:08:38 +0900 From: Takanori Watanabe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3AB8A9A0.3A35227E@stack.nl>, Willem van Engen $B$5$s$$$o$/(B: >> And you will need to know grandparent device name to bind the device >> collectly.(Or should we need a way to get device attribute such as >> Mother board, Video Capture BitBang,Video Capture Cooked,VGA Card and etc.) >I don't quite understand this; I guess I don't know enough about newbus >or so. Do you want your driver attached to Video Capture device? 'device_identify' method is called from all parent bus. Takanori Watanabe Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 7:24: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from amsmta02-svc.chello.nl (mail-out.chello.nl [213.46.240.7]) by hub.freebsd.org (Postfix) with ESMTP id 57BEE37B71E for ; Wed, 21 Mar 2001 07:24:01 -0800 (PST) (envelope-from wvengen@stack.nl) Received: from stack.nl ([213.46.110.240]) by amsmta02-svc.chello.nl (InterMail vK.4.03.02.00 201-232-124 license 9a0f3c09abb1b740b3b0b1917e20d81c) with ESMTP id <20010321145609.CBNZ6000.amsmta02-svc@stack.nl> for ; Wed, 21 Mar 2001 15:56:09 +0100 Message-ID: <3AB8C1F3.5F26D59F@stack.nl> Date: Wed, 21 Mar 2001 16:00:03 +0100 From: Willem van Engen X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: driver: probe not called when smbus child References: <3AB8AB5D.D479E1FC@stack.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > > On Wed, 21 Mar 2001, Willem van Engen wrote: > > DRIVER_MODULE(smb, smbus, smb_driver, smb_devclass, 0, 0); > > so I guess not. But thanks anyway :) > > Yes, but the 'smbus' bus driver doesn't have an attachment to your driver. > > You're trying to create a device that provides an 'smbus' right? > > Or did I totally misread your original post? I think so, or I miswrote it :). I'm writing a driver for a device located on the smbus and want to do it in kernel-space (not a userland program that uses /dev/smb?). > > -- > | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | > | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | > | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 9:16: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from amx.mathieu.org (modemcable161.243-201-24.mtl.mc.videotron.ca [24.201.243.161]) by hub.freebsd.org (Postfix) with ESMTP id 343F237B72A for ; Wed, 21 Mar 2001 09:15:54 -0800 (PST) (envelope-from mathieu@amx.dyn.dhs.org) Received: from amx.dyn.dhs.org (localhost [127.0.0.1]) by amx.mathieu.org (Postfix) with ESMTP id 8954A40BC for ; Wed, 21 Mar 2001 12:25:22 -0500 (EST) Message-ID: <3AB8E402.51160B75@amx.dyn.dhs.org> Date: Wed, 21 Mar 2001 12:25:22 -0500 From: Mathieu Reply-To: mathieu@amx.dyn.dhs.org X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-BETA i386) X-Accept-Language: fr-CA, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: 4.3-BETA world crashing 4.2-RELEASE kernel ? Content-Type: multipart/mixed; boundary="------------DF068CFB638B4E3F4339B60F" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------DF068CFB638B4E3F4339B60F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello ! First, sorry I don't speak English very well :p Usually speak French ! I have a problem with a FreeBSD server that is far far away, so I don't have access to the console. As far as I know, it worked fine with 4.2-RELEASE for... hmm, 2 days, then I upgraded it to the latest STABLE (4.3-BETA), and the server worked fine for 24 hours or so, but then, the server locked up. It was still answering to pings, but all daemons weren't responding anymore. I could still telnet to it, but I was just not getting the login prompt, same thing for Apache, FTP, SSH... I can connect, but no answers. I asked to reboot it many time. And each time, I can telnet to it, and get the login prompt (!), but that's strange... seems it can't fork a shell... I don't even get the motd, just the "Last login from..." thing. But sometime SendMail is working, and I could send mail to the account previously created on the machine. But all the servers always die in something like, 5 minutes.. Then it still answers to pings, but just no answers from Telnet/Apache/FTP, etc... :( However, the technicians there were able to do a make world in single user mode, worked fine. But in multi user mode, the server seems to consume all his ressources, and then processes start to crash randomly, and there is also files corrumption, and always some kind of error messages like "Cannot kill process", things like that, they don't know what's causing this. Of course, technicians there want to bill me 100$ to reinstall 4.2-RELEASE.. hehehe :p But luckily, I've backuped a 4.2-RELEASE kernel in the root. So, now, the computer does exactly the same thing with the 4.2 kernel, exactly. But those technicians still says that the problem came from the 4.3-BETA environnement (hmm, the "world" !), not the kernel, nor the hardware, so they have to "repair" what I've broken ($). :( So, is it safe to say that the world is indenpendent of the hardware so this problem should reproduce on all 4.3 system around the planet (Hehehe, personnaly, it works fine on my computer ! :p), or could this really be a bug NOT in the FreeBSD kernel that causes the machine to die in 5 minutes or so in multi user mode (even will it is idle !) ? Thanks ! And sorry for this long long long e-mail :p I've attached a DMESG from 4.2-RELEASE, sorry... I don't have a more recent one. -- Mathieu --------------DF068CFB638B4E3F4339B60F Content-Type: text/plain; charset=us-ascii; name="dmesg.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.txt" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT 2000 jkh@bento.FreeBSD.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (735.00-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383fbff real memory = 66060288 (64512K bytes) config> di sn0 config> di lnc0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> q avail memory = 60080128 (58672K bytes) Preloaded elf kernel "kernel" at 0xc0436000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc043609c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 1.0 irq 0 pcib1: at device 30.0 on pci0 pci1: on pcib1 fxp0: port 0xdf00-0xdf3f mem 0xff700000-0xff7fffff,0xff8df000-0xff8dffff irq 10 at device 5.0 on pci1 fxp0: Ethernet address 00:e0:81:01:7e:be isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: (vendor=0x8086, dev=0x2413) at 31.3 irq 11 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ad0: 19541MB [39704/16/63] at ata0-master UDMA66 Mounting root from ufs:/dev/ad0s1a fxp0: promiscuous mode enabled fxp0: promiscuous mode disabled --------------DF068CFB638B4E3F4339B60F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 9:25:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout1-100bt.midsouth.rr.com (mailout1-100bt.midsouth.rr.com [24.92.68.6]) by hub.freebsd.org (Postfix) with ESMTP id 0AA3237B72A for ; Wed, 21 Mar 2001 09:25:03 -0800 (PST) (envelope-from dchance@valuedata.net) Received: from mail.midsouth.rr.com (mail.midsouth.rr.com [24.92.68.1]) by mailout1-100bt.midsouth.rr.com (8.11.2/8.11.2) with ESMTP id f2LHOuL15675; Wed, 21 Mar 2001 11:24:56 -0600 (CST) Received: from mike ([24.95.125.205]) by mail.midsouth.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-59787U250000L250000S0V35) with SMTP id com; Wed, 21 Mar 2001 11:24:57 -0600 Message-ID: <002e01c0b22b$da43fb00$0200000a@mike> From: "Daryl Chance" To: , References: <3AB8E402.51160B75@amx.dyn.dhs.org> Subject: Re: 4.3-BETA world crashing 4.2-RELEASE kernel ? Date: Wed, 21 Mar 2001 11:24:54 -0600 Organization: ValueData, LLC MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you compiling with any optimizations? I had a problem similar to this in that ssh, ftp, apache were running, and I could connect on my internal network....but connections from the outside (like me trying to connect to it from work) would either make it seem the machine was "locked down". you could ping and see that it was alive, but you couldn't get in through SSH or anything else. I traced it down to a compile I did with kernal optimizations (-02), so I turned that off, rebuilt the kernal, rebooted and all was fine. - Daryl Chance | And which parallel universe did ValueData, LLC | YOU crawl out of? Memphis, TN | - http://www.thinkgeek.com ----- Original Message ----- From: "Mathieu" To: Sent: Wednesday, March 21, 2001 11:25 AM Subject: 4.3-BETA world crashing 4.2-RELEASE kernel ? > Hello ! > > First, sorry I don't speak English very well :p Usually speak French ! > > I have a problem with a FreeBSD server that is far far away, so I don't > have access to the console. As far as I know, it worked fine with > 4.2-RELEASE for... hmm, 2 days, then I upgraded it to the latest STABLE > (4.3-BETA), and the server worked fine for 24 hours or so, but then, the > server locked up. It was still answering to pings, but all daemons > weren't responding anymore. I could still telnet to it, but I was just > not getting the login prompt, same thing for Apache, FTP, SSH... I can > connect, but no answers. > > I asked to reboot it many time. And each time, I can telnet to it, and > get the login prompt (!), but that's strange... seems it can't fork a > shell... I don't even get the motd, just the "Last login from..." thing. > But sometime SendMail is working, and I could send mail to the account > previously created on the machine. But all the servers always die in > something like, 5 minutes.. Then it still answers to pings, but just no > answers from Telnet/Apache/FTP, etc... :( > > However, the technicians there were able to do a make world in single > user mode, worked fine. But in multi user mode, the server seems to > consume all his ressources, and then processes start to crash randomly, > and there is also files corrumption, and always some kind of error > messages like "Cannot kill process", things like that, they don't know > what's causing this. > > Of course, technicians there want to bill me 100$ to reinstall > 4.2-RELEASE.. hehehe :p But luckily, I've backuped a 4.2-RELEASE kernel > in the root. So, now, the computer does exactly the same thing with the > 4.2 kernel, exactly. But those technicians still says that the problem > came from the 4.3-BETA environnement (hmm, the "world" !), not the > kernel, nor the hardware, so they have to "repair" what I've broken ($). > :( > > So, is it safe to say that the world is indenpendent of the hardware so > this problem should reproduce on all 4.3 system around the planet > (Hehehe, personnaly, it works fine on my computer ! :p), or could this > really be a bug NOT in the FreeBSD kernel that causes the machine to die > in 5 minutes or so in multi user mode (even will it is idle !) ? > > Thanks ! And sorry for this long long long e-mail :p > > I've attached a DMESG from 4.2-RELEASE, sorry... I don't have a more > recent one. > > -- > Mathieu ---------------------------------------------------------------------------- ---- > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT 2000 > jkh@bento.FreeBSD.org:/usr/src/sys/compile/GENERIC > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (735.00-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x686 Stepping = 6 > Features=0x383fbff > real memory = 66060288 (64512K bytes) > config> di sn0 > config> di lnc0 > config> di ie0 > config> di fe0 > config> di ed0 > config> di cs0 > config> q > avail memory = 60080128 (58672K bytes) > Preloaded elf kernel "kernel" at 0xc0436000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc043609c. > Pentium Pro MTRR support enabled > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pci0: at 1.0 irq 0 > pcib1: at device 30.0 on pci0 > pci1: on pcib1 > fxp0: port 0xdf00-0xdf3f mem 0xff700000-0xff7fffff,0xff8df000-0xff8dffff irq 10 at device 5.0 on pci1 > fxp0: Ethernet address 00:e0:81:01:7e:be > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: (vendor=0x8086, dev=0x2413) at 31.3 irq 11 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x100> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A, console > sio1: configured irq 3 not in bitmap of probed irqs 0 > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ad0: 19541MB [39704/16/63] at ata0-master UDMA66 > Mounting root from ufs:/dev/ad0s1a > fxp0: promiscuous mode enabled > fxp0: promiscuous mode disabled > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 9:30:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id A0ED237B73D for ; Wed, 21 Mar 2001 09:30:21 -0800 (PST) (envelope-from danfe@inet.ssc.nsu.ru) Received: (qmail 23291 invoked from network); 21 Mar 2001 17:30:01 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 21 Mar 2001 17:30:01 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id XAA25194 for ; Wed, 21 Mar 2001 23:29:42 +0600 Date: Wed, 21 Mar 2001 23:29:41 +0600 (NOVT) From: Alexey Dokuchaev To: freebsd-hackers@freebsd.org Subject: Linux -> FreeBSD VM functions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I seems to have a lot of VM-relevant code to port, and I'd like to get answers for several questions arised along the way: --- * How do I port something like this: . . . static inline unsigned long get_kvirt_address(unsigned long address) { pgd_t *pg_dir; pmd_t *pg_mid_dir; pte_t *pg_table; unsigned long ret_addr = 0; pg_dir = pgd_offset(current->mm, address); if (pgd_none(*pg_dir)) goto done; pg_mid_dir = pmd_offset(pg_dir, address); if (pmd_none(*pg_mid_dir)) goto done; pg_table = pte_offset(pg_mid_dir, address); if (!pte_present(*pg_table)) goto done; ret_addr = pte_page(*pg_table); done: return ret_addr; } . . . Is simple PHYS_TO_VM_PAGE will do? --- * What about this one: . . . if (PageReserved(mem_map + GET_MAP_NR(page))) { ... } . . . And this one: . . . mem_map_reserve(GET_MAP_NR(page)); . . . --- * There seem to be these flags defined in linux/mm.h: /* Page flag bit values */ #define PG_locked 0 #define PG_error 1 #define PG_referenced 2 #define PG_dirty 3 #define PG_uptodate 4 #define PG_free_after 5 #define PG_decr_after 6 #define PG_swap_unlock_after 7 #define PG_DMA 8 #define PG_Slab 9 #define PG_swap_cache 10 #define PG_skip 11 #define PG_reserved 31 How do those relate to FreeBSD vision of things? --- I will really appreciate any help with regard to this, since this is my first serious in-depth look at VM internals of both linux and FreeBSD, and there seem to be no technical (that is, not plain overviews) of both VM subsystems. -- Regs, Alexey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 9:48: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id AE64037B73E for ; Wed, 21 Mar 2001 09:47:47 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2LHkdO93629; Wed, 21 Mar 2001 09:46:39 -0800 (PST) (envelope-from obrien) Date: Wed, 21 Mar 2001 09:46:38 -0800 From: "David O'Brien" To: Max Khon Cc: "Alexander N. Kabaev" , hackers@FreeBSD.ORG, Titus von Boxberg Subject: Re: GCC Upgrade? Message-ID: <20010321094638.E92274@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from fjoe@newst.net on Wed, Mar 21, 2001 at 06:39:47PM +0600 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 21, 2001 at 06:39:47PM +0600, Max Khon wrote: > Btw, do you have patches that fix sjlj exceptions for 2.95.3? Can you try these? Index: except.c =================================================================== RCS file: /cvs/gcc/egcs/gcc/except.c,v retrieving revision 1.82.4.3 retrieving revision 1.82.4.2 diff -u -r1.82.4.3 -r1.82.4.2 --- except.c 2001/02/19 14:01:59 1.82.4.3 +++ except.c 2000/12/29 16:18:54 1.82.4.2 @@ -723,21 +723,41 @@ receive_exception_label (handler_label) rtx handler_label; { + rtx around_label = NULL_RTX; + + if (! flag_new_exceptions || exceptions_via_longjmp) + { + around_label = gen_label_rtx (); + emit_jump (around_label); + emit_barrier (); + } + emit_label (handler_label); -#ifdef HAVE_exception_receiver if (! exceptions_via_longjmp) - if (HAVE_exception_receiver) - emit_insn (gen_exception_receiver ()); + { +#ifdef HAVE_exception_receiver + if (HAVE_exception_receiver) + emit_insn (gen_exception_receiver ()); + else #endif - #ifdef HAVE_nonlocal_goto_receiver - if (! exceptions_via_longjmp) - if (HAVE_nonlocal_goto_receiver) - emit_insn (gen_nonlocal_goto_receiver ()); + if (HAVE_nonlocal_goto_receiver) + emit_insn (gen_nonlocal_goto_receiver ()); + else #endif -} + { /* Nothing */ } + } + else + { +#ifndef DONT_USE_BUILTIN_SETJMP + expand_builtin_setjmp_receiver (handler_label); +#endif + } + if (around_label) + emit_label (around_label); +} struct func_eh_entry { @@ -1320,7 +1340,7 @@ start_dynamic_handler () { rtx dhc, dcc; - rtx x, arg, buf; + rtx arg, buf; int size; #ifndef DONT_USE_BUILTIN_SETJMP @@ -1362,18 +1382,17 @@ buf = plus_constant (XEXP (arg, 0), GET_MODE_SIZE (Pmode)*2); #ifdef DONT_USE_BUILTIN_SETJMP - x = emit_library_call_value (setjmp_libfunc, NULL_RTX, 1, SImode, 1, - buf, Pmode); - /* If we come back here for a catch, transfer control to the handler. */ - jumpif_rtx (x, ehstack.top->entry->exception_handler_label); -#else { - /* A label to continue execution for the no exception case. */ - rtx noex = gen_label_rtx(); - x = expand_builtin_setjmp (buf, NULL_RTX, noex, - ehstack.top->entry->exception_handler_label); - emit_label (noex); + rtx x; + x = emit_library_call_value (setjmp_libfunc, NULL_RTX, LCT_CONST, + TYPE_MODE (integer_type_node), 1, + buf, Pmode); + /* If we come back here for a catch, transfer control to the handler. */ + jumpif_rtx (x, ehstack.top->entry->exception_handler_label); } +#else + expand_builtin_setjmp_setup (buf, + ehstack.top->entry->exception_handler_label); #endif /* We are committed to this, so update the handler chain. */ Index: expr.c =================================================================== RCS file: /cvs/gcc/egcs/gcc/expr.c,v retrieving revision 1.144.4.9 retrieving revision 1.144.4.8 diff -u -r1.144.4.9 -r1.144.4.8 --- expr.c 2001/02/19 14:02:00 1.144.4.9 +++ expr.c 2001/01/25 14:03:06 1.144.4.8 @@ -192,6 +192,7 @@ static int apply_args_size PROTO((void)); static int apply_result_size PROTO((void)); static rtx result_vector PROTO((int, rtx)); +static rtx expand_builtin_setjmp PROTO((tree, rtx)); static rtx expand_builtin_apply_args PROTO((void)); static rtx expand_builtin_apply PROTO((rtx, rtx, rtx)); static void expand_builtin_return PROTO((rtx)); @@ -8544,44 +8545,29 @@ return tem; } -/* __builtin_setjmp is passed a pointer to an array of five words (not - all will be used on all machines). It operates similarly to the C - library function of the same name, but is more efficient. Much of - the code below (and for longjmp) is copied from the handling of - non-local gotos. - - NOTE: This is intended for use by GNAT and the exception handling - scheme in the compiler and will only work in the method used by - them. */ +/* Construct the leading half of a __builtin_setjmp call. Control will + return to RECEIVER_LABEL. This is used directly by sjlj exception + handling code. */ -rtx -expand_builtin_setjmp (buf_addr, target, first_label, next_label) +void +expand_builtin_setjmp_setup (buf_addr, receiver_label) rtx buf_addr; - rtx target; - rtx first_label, next_label; + rtx receiver_label; { - rtx lab1 = gen_label_rtx (); enum machine_mode sa_mode = STACK_SAVEAREA_MODE (SAVE_NONLOCAL); - enum machine_mode value_mode; rtx stack_save; - value_mode = TYPE_MODE (integer_type_node); - #ifdef POINTERS_EXTEND_UNSIGNED buf_addr = convert_memory_address (Pmode, buf_addr); #endif buf_addr = force_reg (Pmode, buf_addr); - if (target == 0 || GET_CODE (target) != REG - || REGNO (target) < FIRST_PSEUDO_REGISTER) - target = gen_reg_rtx (value_mode); - emit_queue (); - /* We store the frame pointer and the address of lab1 in the buffer - and use the rest of it for the stack save area, which is - machine-dependent. */ + /* We store the frame pointer and the address of receiver_label in + the buffer and use the rest of it for the stack save area, which + is machine-dependent. */ #ifndef BUILTIN_SETJMP_FRAME_VALUE #define BUILTIN_SETJMP_FRAME_VALUE virtual_stack_vars_rtx @@ -8593,7 +8579,7 @@ (gen_rtx_MEM (Pmode, plus_constant (buf_addr, GET_MODE_SIZE (Pmode)))), - force_reg (Pmode, gen_rtx_LABEL_REF (Pmode, lab1))); + force_reg (Pmode, gen_rtx_LABEL_REF (Pmode, receiver_label))); stack_save = gen_rtx_MEM (sa_mode, plus_constant (buf_addr, @@ -8606,20 +8592,22 @@ emit_insn (gen_builtin_setjmp_setup (buf_addr)); #endif - /* Set TARGET to zero and branch to the first-time-through label. */ - emit_move_insn (target, const0_rtx); - emit_jump_insn (gen_jump (first_label)); - emit_barrier (); - emit_label (lab1); + /* Tell optimize_save_area_alloca that extra work is going to + need to go on during alloca. */ + current_function_calls_setjmp = 1; - /* Tell flow about the strange goings on. Putting `lab1' on - `nonlocal_goto_handler_labels' to indicates that function - calls may traverse the arc back to this label. */ - + /* Set this so all the registers get saved in our frame; we need to be + able to copy the saved values for any registers from frames we unwind. */ current_function_has_nonlocal_label = 1; - nonlocal_goto_handler_labels = - gen_rtx_EXPR_LIST (VOIDmode, lab1, nonlocal_goto_handler_labels); +} +/* Construct the trailing part of a __builtin_setjmp call. + This is used directly by sjlj exception handling code. */ + +void +expand_builtin_setjmp_receiver (receiver_label) + rtx receiver_label ATTRIBUTE_UNUSED; +{ /* Clobber the FP when we get here, so we have to make sure it's marked as used by this function. */ emit_insn (gen_rtx_USE (VOIDmode, hard_frame_pointer_rtx)); @@ -8666,7 +8654,7 @@ #ifdef HAVE_builtin_setjmp_receiver if (HAVE_builtin_setjmp_receiver) - emit_insn (gen_builtin_setjmp_receiver (lab1)); + emit_insn (gen_builtin_setjmp_receiver (receiver_label)); else #endif #ifdef HAVE_nonlocal_goto_receiver @@ -8678,11 +8666,67 @@ ; /* Nothing */ } - /* Set TARGET, and branch to the next-time-through label. */ - emit_move_insn (target, const1_rtx); - emit_jump_insn (gen_jump (next_label)); + /* @@@ This is a kludge. Not all machine descriptions define a blockage + insn, but we must not allow the code we just generated to be reordered + by scheduling. Specifically, the update of the frame pointer must + happen immediately, not later. So emit an ASM_INPUT to act as blockage + insn. */ + emit_insn (gen_rtx_ASM_INPUT (VOIDmode, "")); +} + + +/* __builtin_setjmp is passed a pointer to an array of five words (not + all will be used on all machines). It operates similarly to the C + library function of the same name, but is more efficient. Much of + the code below (and for longjmp) is copied from the handling of + non-local gotos. + + NOTE: This is intended for use by GNAT and the exception handling + scheme in the compiler and will only work in the method used by + them. */ + +static rtx +expand_builtin_setjmp (arglist, target) + tree arglist; + rtx target; +{ + rtx buf_addr, next_lab, cont_lab; + + if (arglist == 0 + || TREE_CODE (TREE_TYPE (TREE_VALUE (arglist))) != POINTER_TYPE) + return NULL_RTX; + + if (target == 0 || GET_CODE (target) != REG + || REGNO (target) < FIRST_PSEUDO_REGISTER) + target = gen_reg_rtx (TYPE_MODE (integer_type_node)); + + buf_addr = expand_expr (TREE_VALUE (arglist), NULL_RTX, VOIDmode, 0); + + next_lab = gen_label_rtx (); + cont_lab = gen_label_rtx (); + + expand_builtin_setjmp_setup (buf_addr, next_lab); + + /* Set TARGET to zero and branch to the continue label. */ + emit_move_insn (target, const0_rtx); + emit_jump_insn (gen_jump (cont_lab)); emit_barrier (); + emit_label (next_lab); + expand_builtin_setjmp_receiver (next_lab); + + /* Set TARGET to one. */ + emit_move_insn (target, const1_rtx); + emit_label (cont_lab); + + /* Tell flow about the strange goings on. Putting `next_lab' on + `nonlocal_goto_handler_labels' to indicates that function + calls may traverse the arc back to this label. */ + + current_function_has_nonlocal_label = 1; + nonlocal_goto_handler_labels + = gen_rtx_EXPR_LIST (VOIDmode, next_lab, nonlocal_goto_handler_labels); + return target; } @@ -9703,18 +9747,10 @@ #endif case BUILT_IN_SETJMP: - if (arglist == 0 - || TREE_CODE (TREE_TYPE (TREE_VALUE (arglist))) != POINTER_TYPE) - break; - else - { - rtx buf_addr = expand_expr (TREE_VALUE (arglist), subtarget, - VOIDmode, 0); - rtx lab = gen_label_rtx (); - rtx ret = expand_builtin_setjmp (buf_addr, target, lab, lab); - emit_label (lab); - return ret; - } + target = expand_builtin_setjmp (arglist, target); + if (target) + return target; + break; /* __builtin_longjmp is passed a pointer to an array of five words. It's similar to the C library longjmp function but works with Index: expr.h =================================================================== RCS file: /cvs/gcc/egcs/gcc/expr.h,v retrieving revision 1.34.4.4 retrieving revision 1.34.4.3 diff -u -r1.34.4.4 -r1.34.4.3 --- expr.h 2001/02/19 14:02:02 1.34.4.4 +++ expr.h 2000/12/29 16:18:54 1.34.4.3 @@ -831,7 +831,8 @@ Useful after calling expand_expr with 1 as sum_ok. */ extern rtx force_operand PROTO((rtx, rtx)); -extern rtx expand_builtin_setjmp PROTO((rtx, rtx, rtx, rtx)); +extern void expand_builtin_setjmp_setup PARAMS ((rtx, rtx)); +extern void expand_builtin_setjmp_receiver PARAMS ((rtx)); #ifdef TREE_CODE /* Generate code for computing expression EXP. Index: varasm.c =================================================================== RCS file: /cvs/gcc/egcs/gcc/varasm.c,v retrieving revision 1.59.4.7 retrieving revision 1.59.4.6 diff -u -r1.59.4.7 -r1.59.4.6 --- varasm.c 2001/02/19 14:02:02 1.59.4.7 +++ varasm.c 2001/01/25 14:03:24 1.59.4.6 @@ -3494,6 +3494,18 @@ pop_obstacks (); } + if (GET_CODE (x) == LABEL_REF) + { + extern rtx forced_labels; + + push_obstacks_nochange (); + rtl_in_saveable_obstack (); + + forced_labels = gen_rtx_EXPR_LIST (VOIDmode, + XEXP (x, 0), + forced_labels); + pop_obstacks (); + } /* Allocate a pool constant descriptor, fill it in, and chain it in. */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 9:51: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postfix.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id 342B337B742 for ; Wed, 21 Mar 2001 09:50:57 -0800 (PST) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by postfix.conectiva.com.br (Postfix) with SMTP id C1E9A16DFD for ; Wed, 21 Mar 2001 14:50:51 -0300 (EST) Received: (qmail 30402 invoked by uid 0); 21 Mar 2001 17:50:13 -0000 Received: from dial10.ras.conectiva (HELO imladris.rielhome.conectiva) (root@10.0.8.10) by burns.conectiva with SMTP; 21 Mar 2001 17:50:13 -0000 Received: from localhost (IDENT:riel@localhost [127.0.0.1]) by imladris.rielhome.conectiva (8.11.2/8.11.2) with ESMTP id f2LGVjh10858; Wed, 21 Mar 2001 13:31:45 -0300 Date: Wed, 21 Mar 2001 13:31:45 -0300 (BRST) From: Rik van Riel X-Sender: riel@imladris.rielhome.conectiva To: Peter Wemm Cc: Matt Dillon , Alfred Perlstein , "Michael C . Wu" , "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver In-Reply-To: <200103211114.f2LBE0h57371@mobile.wemm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Mar 2001, Peter Wemm wrote: > Also, 4MB = 1024 pages, at 28 bytes per mapping == 28k per process. 28 bytes/mapping is a LOT. I've implemented an (admittedly not completely architecture-independent) reverse mapping patch for Linux with an overhead of 8 bytes/pte... I wonder how hard/easy would it be to reduce the memory overhead of some of these old Mach data structures in FreeBSD... regards, Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com.br/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 9:58: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from amx.mathieu.org (modemcable161.243-201-24.mtl.mc.videotron.ca [24.201.243.161]) by hub.freebsd.org (Postfix) with ESMTP id 8A42037B746 for ; Wed, 21 Mar 2001 09:57:50 -0800 (PST) (envelope-from mathieu@amx.dyn.dhs.org) Received: from amx.dyn.dhs.org (localhost [127.0.0.1]) by amx.mathieu.org (Postfix) with ESMTP id E81CA40BC; Wed, 21 Mar 2001 13:05:54 -0500 (EST) Message-ID: <3AB8ED82.2D73F891@amx.dyn.dhs.org> Date: Wed, 21 Mar 2001 13:05:54 -0500 From: Mathieu Reply-To: mathieu@amx.dyn.dhs.org X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-BETA i386) X-Accept-Language: fr-CA, en MIME-Version: 1.0 To: Daryl Chance Cc: freebsd-hackers@freebsd.org Subject: Re: 4.3-BETA world crashing 4.2-RELEASE kernel ? References: <3AB8E402.51160B75@amx.dyn.dhs.org> <002e01c0b22b$da43fb00$0200000a@mike> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Interesting.. I didn't know -O2 could do that. :p But I don't think I compiled with any optimisations, nothing in my make.conf, nothing in my kernel config file. What I did to upgrade was CVSup, Backuping /etc, make buildkernel, make buildworld, make installkernel, reboot, make installworld, reboot, mergemaster, reboot ! And then it worked fine for 24 hours ! Did I foget something ? Daryl Chance wrote: > > Are you compiling with any optimizations? I had a problem similar > to this in that ssh, ftp, apache were running, and I could connect > on my internal network....but connections from the outside (like me > trying to connect to it from work) would either make it seem the > machine was "locked down". you could ping and see that it was > alive, but you couldn't get in through SSH or anything else. I > traced it down to a compile I did with kernal optimizations (-02), > so I turned that off, rebuilt the kernal, rebooted and all was fine. > > - > Daryl Chance | And which parallel universe did > ValueData, LLC | YOU crawl out of? > Memphis, TN | - http://www.thinkgeek.com > ----- Original Message ----- > From: "Mathieu" > To: > Sent: Wednesday, March 21, 2001 11:25 AM > Subject: 4.3-BETA world crashing 4.2-RELEASE kernel ? > > > Hello ! > > > > First, sorry I don't speak English very well :p Usually speak French ! > > > > I have a problem with a FreeBSD server that is far far away, so I don't > > have access to the console. As far as I know, it worked fine with > > 4.2-RELEASE for... hmm, 2 days, then I upgraded it to the latest STABLE > > (4.3-BETA), and the server worked fine for 24 hours or so, but then, the > > server locked up. It was still answering to pings, but all daemons > > weren't responding anymore. I could still telnet to it, but I was just > > not getting the login prompt, same thing for Apache, FTP, SSH... I can > > connect, but no answers. > > > > I asked to reboot it many time. And each time, I can telnet to it, and > > get the login prompt (!), but that's strange... seems it can't fork a > > shell... I don't even get the motd, just the "Last login from..." thing. > > But sometime SendMail is working, and I could send mail to the account > > previously created on the machine. But all the servers always die in > > something like, 5 minutes.. Then it still answers to pings, but just no > > answers from Telnet/Apache/FTP, etc... :( > > > > However, the technicians there were able to do a make world in single > > user mode, worked fine. But in multi user mode, the server seems to > > consume all his ressources, and then processes start to crash randomly, > > and there is also files corrumption, and always some kind of error > > messages like "Cannot kill process", things like that, they don't know > > what's causing this. > > > > Of course, technicians there want to bill me 100$ to reinstall > > 4.2-RELEASE.. hehehe :p But luckily, I've backuped a 4.2-RELEASE kernel > > in the root. So, now, the computer does exactly the same thing with the > > 4.2 kernel, exactly. But those technicians still says that the problem > > came from the 4.3-BETA environnement (hmm, the "world" !), not the > > kernel, nor the hardware, so they have to "repair" what I've broken ($). > > :( > > > > So, is it safe to say that the world is indenpendent of the hardware so > > this problem should reproduce on all 4.3 system around the planet > > (Hehehe, personnaly, it works fine on my computer ! :p), or could this > > really be a bug NOT in the FreeBSD kernel that causes the machine to die > > in 5 minutes or so in multi user mode (even will it is idle !) ? > > > > Thanks ! And sorry for this long long long e-mail :p > > > > I've attached a DMESG from 4.2-RELEASE, sorry... I don't have a more > > recent one. > > > > -- > > Mathieu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 10:38:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 1E87C37B721; Wed, 21 Mar 2001 09:58:38 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2LHucH27120; Wed, 21 Mar 2001 09:56:38 -0800 (PST) Date: Wed, 21 Mar 2001 09:56:38 -0800 From: Alfred Perlstein To: Rik van Riel Cc: Peter Wemm , Matt Dillon , "Michael C . Wu" , "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver Message-ID: <20010321095638.H12319@fw.wintelcom.net> References: <200103211114.f2LBE0h57371@mobile.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from riel@conectiva.com.br on Wed, Mar 21, 2001 at 01:31:45PM -0300 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Rik van Riel [010321 09:51] wrote: > On Wed, 21 Mar 2001, Peter Wemm wrote: > > > Also, 4MB = 1024 pages, at 28 bytes per mapping == 28k per process. > > 28 bytes/mapping is a LOT. I've implemented an (admittedly > not completely architecture-independent) reverse mapping > patch for Linux with an overhead of 8 bytes/pte... > > I wonder how hard/easy would it be to reduce the memory > overhead of some of these old Mach data structures in FreeBSD... "Our" Alan Cox and Tor Egge have been trimming these structs down for quite some time. Perhaps they should look at Linux's system, however last I checked Linux's was an order of magnitude less complex which might prohibit that simplification in FreeBSD. If you have suggestions, let's hear them. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 11:31:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id D838837B775; Wed, 21 Mar 2001 11:31:35 -0800 (PST) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.11.3/8.11.3) id f2LIZUb76043; Wed, 21 Mar 2001 13:35:30 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.7p2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010321094638.E92274@dragon.nuxi.com> Date: Wed, 21 Mar 2001 13:35:30 -0500 (EST) Organization: Verizon Laboratories Inc. From: "Alexander N. Kabaev" To: "David O'Brien" Subject: Re: GCC Upgrade? Cc: Titus von Boxberg , hackers@FreeBSD.ORG, Max Khon Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This patch will work. According to Berndt Schimidt, there are some problems with it on HP/UX and that was the main reason why it was backed out. I never saw any ill effects on i386 with this patch though, while good efects include: a) working sjlj exceptions b) ability to compile QT2 with exceptions enabled and with -O2 flag without consuming ~400M memory for abnormal call egdes in GCC flow optimization pass. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 11:32:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.2.7]) by hub.freebsd.org (Postfix) with ESMTP id 4AAD737B718 for ; Wed, 21 Mar 2001 11:32:32 -0800 (PST) (envelope-from Marcov@stack.nl) Received: from hermes.tue.nl (hermes.tue.nl [131.155.2.46]) by kweetal.tue.nl (8.11.0/8.11.0) with ESMTP id f2LJ13w09295 for ; Wed, 21 Mar 2001 20:01:03 +0100 (MET) Received: from tilly (n164.dial.tue.nl [131.155.209.163]) by hermes.tue.nl (Postfix) with SMTP id 37A822E802 for ; Wed, 21 Mar 2001 20:00:42 +0100 (CET) From: "Marco van de Voort" To: freebsd-hackers@freebsd.org Date: Wed, 21 Mar 2001 19:51:49 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Opinion asked: unicode encoding X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <20010321190042.37A822E802@hermes.tue.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. The fpc core team is currently working on unicode support for Free Pascal, a pascal compiler that runs on FreeBSD/i386, and I would like to ask your opinion about what encoding to choose for the default multibyte string type. (Delphi's WideString), choices are UTF- 8 , -16 or UCS4. Not only because you might have an opinion on what is going to be the dominant encoding over time on FreeBSD (and *nix in general), but also because our core members are mainly in countries which are covered by cp850, and therefore have relatively little experience with multibyte characters and their pitfalls. Actually all three encodings and conversions will be implemented, but only one will get full support (with all string operations available), for the other two encodings, the compiler will insert automatic conversions for the routines not overloaded for the less important encodings. Any opinions? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 11:33:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth.backplane.com [208.161.114.65]) by hub.freebsd.org (Postfix) with ESMTP id AA1DC37B7FA; Wed, 21 Mar 2001 11:33:29 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2LJ7cp17933; Wed, 21 Mar 2001 11:07:38 -0800 (PST) (envelope-from dillon) Date: Wed, 21 Mar 2001 11:07:38 -0800 (PST) From: Matt Dillon Message-Id: <200103211907.f2LJ7cp17933@earth.backplane.com> To: Alfred Perlstein Cc: "Michael C . Wu" , Rik van Riel , Peter Wemm , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver References: <200103211114.f2LBE0h57371@mobile.wemm.org> <20010321120620.A932@peorth.iteration.net> <200103211817.f2LIHR416007@earth.backplane.com> <20010321102836.N12319@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hey, talking about large amounts of swap, did you know that: : 4.2-STABLE FreeBSD 4.2-STABLE #1: Sat Feb 10 01:26:41 PST 2001 :has a max swap limit that's possibly 'low': : : b: 15912412 0 swap # (Cyl. 0 - 990*) : c: 17912412 0 unused 0 0 # (Cyl. 0 - 1114*) : :If I made b == c, then i couldn't swapon it. : :Don't ask why I have that much swap, I just needed a bunch on a dedicated :disk. :) : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] You would have to reconfigure your kernel to reduce NSWAP from 4 to either 2 or 1. Bitmap overhead for swap is 2 bits per page (4K) of swap. There is a maximum of 2G / 16 / NSWAPDEV blocks (512 byte chunks) of swap. If NSWAPDEV is 4, this comes to: 2G/16/4x512 = 17GB. So you would be able to create approximately four 17GB swap partitions. If you reduce NSWAP to 2 you would be able to create approximately two 34GB swap partitions. If you reduce NSWAP to 1 you would be able to create approximately one 68GB swap partition. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 11:34: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth.backplane.com [208.161.114.65]) by hub.freebsd.org (Postfix) with ESMTP id F20BB37B765; Wed, 21 Mar 2001 11:33:29 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2LIHR416007; Wed, 21 Mar 2001 10:17:27 -0800 (PST) (envelope-from dillon) Date: Wed, 21 Mar 2001 10:17:27 -0800 (PST) From: Matt Dillon Message-Id: <200103211817.f2LIHR416007@earth.backplane.com> To: "Michael C . Wu" Cc: Rik van Riel , Peter Wemm , Alfred Perlstein , "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver References: <200103211114.f2LBE0h57371@mobile.wemm.org> <20010321120620.A932@peorth.iteration.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :B) Added 3gb of swap on one drive, 1gb of swap on a raid volume : another 1gb swap on another raid volume :C) enabled vfs.vmiodirenable and kern.ipc.shm_use_phys : :-- :+-----------------------------------------------------------+ :| keichii@iteration.net | keichii@freebsd.org | I'd reduce that 3gb on that one drive to 1gb. The kernel allocates a bitmap for 4 * (largest_swap_partition), i.e. it will allocate a bitmap for 3gb x 4 = 12 gb worth of swap, even though you only have 5. If you reduce the 3gb to 1gb, then the kernel will allocate a bitmap for 1gb x 4 = 4gb worth of swap, using 1/3 the memory for the bitmap. Each page of swap eats 2 bits of memory for the bitmap so we aren't talking about a huge amount of memory, but it's worth doing. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 11:34:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth.backplane.com [208.161.114.65]) by hub.freebsd.org (Postfix) with ESMTP id 547CF37B718; Wed, 21 Mar 2001 11:34:24 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2LIeYA16476; Wed, 21 Mar 2001 10:40:34 -0800 (PST) (envelope-from dillon) Date: Wed, 21 Mar 2001 10:40:34 -0800 (PST) From: Matt Dillon Message-Id: <200103211840.f2LIeYA16476@earth.backplane.com> To: Alfred Perlstein Cc: Rik van Riel , Peter Wemm , "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver References: <200103211114.f2LBE0h57371@mobile.wemm.org> <20010321095638.H12319@fw.wintelcom.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :* Rik van Riel [010321 09:51] wrote: :> On Wed, 21 Mar 2001, Peter Wemm wrote: :> :> > Also, 4MB = 1024 pages, at 28 bytes per mapping == 28k per process. :> :> 28 bytes/mapping is a LOT. I've implemented an (admittedly :> not completely architecture-independent) reverse mapping :> patch for Linux with an overhead of 8 bytes/pte... :> :> I wonder how hard/easy would it be to reduce the memory :> overhead of some of these old Mach data structures in FreeBSD... : :"Our" Alan Cox and Tor Egge have been trimming :these structs down for quite some time. Perhaps they should :look at Linux's system, however last I checked Linux's was :an order of magnitude less complex which might prohibit that :simplification in FreeBSD. : :If you have suggestions, let's hear them. :) : :-- :-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] We've looked at those structures quite a bit. DG and I talked about it a year or two ago but we came to the conclusion that the extra linkages in our pv_entry gave us significant performance benefits during rundowns. Since then Tor has done a lot of cleanup, but I don't think the analysis has changed much. typedef struct pv_entry { pmap_t pv_pmap; /* pmap where mapping lies */ vm_offset_t pv_va; /* virtual address for mapping */ TAILQ_ENTRY(pv_entry) pv_list; TAILQ_ENTRY(pv_entry) pv_plist; vm_page_t pv_ptem; /* VM page for pte */ } *pv_entry_t; pv_pmap The pmap associated with the pv_entry. pv_va The virtual address of the pv_entry in the pmap. Used to quickly track down the pv_entry associated with a (pmap, vm_page_t, va) when iterating a pv_list or pv_plist. pv_list - pv_entry's associated with a vm_page_t. pv_plist - pv_entry's associated with a pmap A pmap_entry can be located either through pv_list or through pv_plist. The kernel chooses which list to iterate through to find a pv_entry based on which of the two lists has the least number of elements. One of the two nodes could be removed from the pv_entry structure (saving 8 bytes) could be removed but at the cost of performance for certain cases. If you have a huge number of processes sharing a page of memory, iterating through pv_plist to locate a mapping is usually more efficient. If you have fewer processes but full mappings (e.g. the page table page is full), then iterating through pv_list is more efficient. pv_ptem The vm_page_t associated with a pv_entry. This field is used to quickly find associate vm_page_t's when we are wiping whole page tables (e.g. on process exit). It could be removed, but at significant cost to process exits and munmap()'s of large areas. Theoretically we can remove half the structure, but at a significant cost in performance. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 11:36:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 4CB4C37B71B; Wed, 21 Mar 2001 11:36:12 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2LISbL28025; Wed, 21 Mar 2001 10:28:37 -0800 (PST) Date: Wed, 21 Mar 2001 10:28:37 -0800 From: Alfred Perlstein To: Matt Dillon Cc: "Michael C . Wu" , Rik van Riel , Peter Wemm , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.org, fs@FreeBSD.org, hackers@FreeBSD.org Subject: Re: tuning a VERY heavily (30.0) loaded s cerver Message-ID: <20010321102836.N12319@fw.wintelcom.net> References: <200103211114.f2LBE0h57371@mobile.wemm.org> <20010321120620.A932@peorth.iteration.net> <200103211817.f2LIHR416007@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103211817.f2LIHR416007@earth.backplane.com>; from dillon@earth.backplane.com on Wed, Mar 21, 2001 at 10:17:27AM -0800 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matt Dillon [010321 10:20] wrote: > > :B) Added 3gb of swap on one drive, 1gb of swap on a raid volume > : another 1gb swap on another raid volume > :C) enabled vfs.vmiodirenable and kern.ipc.shm_use_phys > : > :-- > :+-----------------------------------------------------------+ > :| keichii@iteration.net | keichii@freebsd.org | > > I'd reduce that 3gb on that one drive to 1gb. The kernel > allocates a bitmap for 4 * (largest_swap_partition), i.e. > it will allocate a bitmap for 3gb x 4 = 12 gb worth of swap, > even though you only have 5. If you reduce the 3gb to 1gb, then > the kernel will allocate a bitmap for 1gb x 4 = 4gb worth of swap, > using 1/3 the memory for the bitmap. Each page of swap eats 2 bits of > memory for the bitmap so we aren't talking about a huge > amount of memory, but it's worth doing. Hey, talking about large amounts of swap, did you know that: 4.2-STABLE FreeBSD 4.2-STABLE #1: Sat Feb 10 01:26:41 PST 2001 has a max swap limit that's possibly 'low': b: 15912412 0 swap # (Cyl. 0 - 990*) c: 17912412 0 unused 0 0 # (Cyl. 0 - 1114*) If I made b == c, then i couldn't swapon it. Don't ask why I have that much swap, I just needed a bunch on a dedicated disk. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 11:41:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout1-100bt.midsouth.rr.com (mailout1-100bt.midsouth.rr.com [24.92.68.6]) by hub.freebsd.org (Postfix) with ESMTP id 8A30D37B727 for ; Wed, 21 Mar 2001 11:41:41 -0800 (PST) (envelope-from dchance@valuedata.net) Received: from mail.midsouth.rr.com (mail.midsouth.rr.com [24.92.68.1]) by mailout1-100bt.midsouth.rr.com (8.11.2/8.11.2) with ESMTP id f2LIxYL29562; Wed, 21 Mar 2001 12:59:35 -0600 (CST) Received: from mike ([24.95.125.205]) by mail.midsouth.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-59787U250000L250000S0V35) with SMTP id com; Wed, 21 Mar 2001 12:59:36 -0600 Message-ID: <000d01c0b239$13181800$0200000a@mike> From: "Daryl Chance" To: Cc: References: <3AB8E402.51160B75@amx.dyn.dhs.org> <002e01c0b22b$da43fb00$0200000a@mike> <3AB8ED82.2D73F891@amx.dyn.dhs.org> Subject: Re: 4.3-BETA world crashing 4.2-RELEASE kernel ? Date: Wed, 21 Mar 2001 12:59:36 -0600 Organization: ValueData, LLC MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I may go about it wrong, but when I upgrade releases I do this: make buildworld make installworld reboot config cd ../../conf/ make depend && make && make install && reboot the gist, I think you need to build the world before the kernal....that *might* be your problem, I don't know :). HTH, - Daryl Chance | And which parallel universe did ValueData, LLC | YOU crawl out of? Memphis, TN | - http://www.thinkgeek.com ----- Original Message ----- From: "Mathieu" To: "Daryl Chance" Cc: Sent: Wednesday, March 21, 2001 12:05 PM Subject: Re: 4.3-BETA world crashing 4.2-RELEASE kernel ? > Interesting.. I didn't know -O2 could do that. :p > > But I don't think I compiled with any optimisations, nothing in my > make.conf, nothing in my kernel config file. What I did to upgrade was > CVSup, Backuping /etc, make buildkernel, make buildworld, make > installkernel, reboot, make installworld, reboot, mergemaster, reboot ! > And then it worked fine for 24 hours ! Did I foget something ? > > Daryl Chance wrote: > > > > Are you compiling with any optimizations? I had a problem similar > > to this in that ssh, ftp, apache were running, and I could connect > > on my internal network....but connections from the outside (like me > > trying to connect to it from work) would either make it seem the > > machine was "locked down". you could ping and see that it was > > alive, but you couldn't get in through SSH or anything else. I > > traced it down to a compile I did with kernal optimizations (-02), > > so I turned that off, rebuilt the kernal, rebooted and all was fine. > > > > - > > Daryl Chance | And which parallel universe did > > ValueData, LLC | YOU crawl out of? > > Memphis, TN | - http://www.thinkgeek.com > > ----- Original Message ----- > > From: "Mathieu" > > To: > > Sent: Wednesday, March 21, 2001 11:25 AM > > Subject: 4.3-BETA world crashing 4.2-RELEASE kernel ? > > > > > Hello ! > > > > > > First, sorry I don't speak English very well :p Usually speak French ! > > > > > > I have a problem with a FreeBSD server that is far far away, so I don't > > > have access to the console. As far as I know, it worked fine with > > > 4.2-RELEASE for... hmm, 2 days, then I upgraded it to the latest STABLE > > > (4.3-BETA), and the server worked fine for 24 hours or so, but then, the > > > server locked up. It was still answering to pings, but all daemons > > > weren't responding anymore. I could still telnet to it, but I was just > > > not getting the login prompt, same thing for Apache, FTP, SSH... I can > > > connect, but no answers. > > > > > > I asked to reboot it many time. And each time, I can telnet to it, and > > > get the login prompt (!), but that's strange... seems it can't fork a > > > shell... I don't even get the motd, just the "Last login from..." thing. > > > But sometime SendMail is working, and I could send mail to the account > > > previously created on the machine. But all the servers always die in > > > something like, 5 minutes.. Then it still answers to pings, but just no > > > answers from Telnet/Apache/FTP, etc... :( > > > > > > However, the technicians there were able to do a make world in single > > > user mode, worked fine. But in multi user mode, the server seems to > > > consume all his ressources, and then processes start to crash randomly, > > > and there is also files corrumption, and always some kind of error > > > messages like "Cannot kill process", things like that, they don't know > > > what's causing this. > > > > > > Of course, technicians there want to bill me 100$ to reinstall > > > 4.2-RELEASE.. hehehe :p But luckily, I've backuped a 4.2-RELEASE kernel > > > in the root. So, now, the computer does exactly the same thing with the > > > 4.2 kernel, exactly. But those technicians still says that the problem > > > came from the 4.3-BETA environnement (hmm, the "world" !), not the > > > kernel, nor the hardware, so they have to "repair" what I've broken ($). > > > :( > > > > > > So, is it safe to say that the world is indenpendent of the hardware so > > > this problem should reproduce on all 4.3 system around the planet > > > (Hehehe, personnaly, it works fine on my computer ! :p), or could this > > > really be a bug NOT in the FreeBSD kernel that causes the machine to die > > > in 5 minutes or so in multi user mode (even will it is idle !) ? > > > > > > Thanks ! And sorry for this long long long e-mail :p > > > > > > I've attached a DMESG from 4.2-RELEASE, sorry... I don't have a more > > > recent one. > > > > > > -- > > > Mathieu > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 11:56:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postfix.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id EDBE537B735 for ; Wed, 21 Mar 2001 11:56:46 -0800 (PST) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by postfix.conectiva.com.br (Postfix) with SMTP id 3DDB116E2A for ; Wed, 21 Mar 2001 16:25:29 -0300 (EST) Received: (qmail 1026 invoked by uid 0); 21 Mar 2001 19:24:50 -0000 Received: from dial11.ras.conectiva (HELO imladris.rielhome.conectiva) (root@10.0.8.11) by burns.conectiva with SMTP; 21 Mar 2001 19:24:50 -0000 Received: from localhost (IDENT:riel@localhost [127.0.0.1]) by imladris.rielhome.conectiva (8.11.2/8.11.2) with ESMTP id f2LJEXh17515; Wed, 21 Mar 2001 16:14:33 -0300 Date: Wed, 21 Mar 2001 16:14:32 -0300 (BRST) From: Rik van Riel X-Sender: riel@imladris.rielhome.conectiva To: Matt Dillon Cc: Alfred Perlstein , Peter Wemm , "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver In-Reply-To: <200103211840.f2LIeYA16476@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Mar 2001, Matt Dillon wrote: > We've looked at those structures quite a bit. DG and I talked about > it a year or two ago but we came to the conclusion that the extra > linkages in our pv_entry gave us significant performance benefits > during rundowns. Since then Tor has done a lot of cleanup, but > I don't think the analysis has changed much. > > typedef struct pv_entry { > pmap_t pv_pmap; /* pmap where mapping lies */ > vm_offset_t pv_va; /* virtual address for mapping */ > TAILQ_ENTRY(pv_entry) pv_list; > TAILQ_ENTRY(pv_entry) pv_plist; > vm_page_t pv_ptem; /* VM page for pte */ > } *pv_entry_t; The (maybe too lightweight) structure I have in my patch looks like this: struct pte_chain { struct pte_chain * next; pte_t * ptep; }; Each pte_chain hangs off a page of physical memory and the ptep is a pointer to a page table entry. The page struct of the page table page itself is used to note down which address space and offset we have. This means that FreeBSD's pv_pmap, pv_va and pv_ptem are in the page table page and NOT in each pte_chain structure... The only issue is address space rundowns, but this _could_ be ok due to the fact that systems usually seem to have more short-running processes than long-running ones and the tasks that are short-running will have their pte_chain nearer to the beginning of the list. Finding all pages in an address_space is simply done by walking the populated parts of the page tables, this is cache friendly and relatively fast for everything except really huge sparse mappings (but in that case, the finer grained locking makes sure this penalty gets restricted to the exiting task only and doesn't block the rest of the system). The whole patch is available at: http://www.surriel.com/patches/2.4/2.4.1-pmap-swapsonuml I have some newer code available, but haven't bothered coding up a new patch yet since the reverse mapping is experimental stuff and we're still busy finetuning and debugging 2.4 ;) regards, Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com.br/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 11:58:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relayout1.micronpc.com (meihost.micronpc.com [209.19.139.2]) by hub.freebsd.org (Postfix) with ESMTP id F012537B729 for ; Wed, 21 Mar 2001 11:58:38 -0800 (PST) (envelope-from mpsimerson@hostpro.com) Received: from mei00wssout01.micron.com (mei00wssout01.micronpc.com [172.30.41.216]) by relayout1.micronpc.com (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with SMTP id MAA02754 for ; Wed, 21 Mar 2001 12:58:11 -0700 Received: from 172.30.41.146 by mei00wssout01.micron.com with ESMTP ( Tumbleweed MMS SMTP Relay(WSS) v4.5); Wed, 21 Mar 2001 12:58:12 -0700 X-Server-Uuid: 6b1d535a-5b27-11d3-bf09-00902786a6a3 Received: by imcout1.micronpc.com with Internet Mail Service ( 5.5.2650.21) id ; Wed, 21 Mar 2001 12:58:38 -0700 Message-ID: <8D18712B2604D411A6BB009027F6449801B4B53D@0SEA01EXSRV1> From: "Matt Simerson" To: freebsd-hackers@freebsd.org Subject: RE: 4.3-BETA world crashing 4.2-RELEASE kernel ? Date: Wed, 21 Mar 2001 12:58:04 -0700 X-Mailer: Internet Mail Service (5.5.2650.21) MIME-Version: 1.0 X-WSS-ID: 16A7D85E266764-01-01 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's how I do a make world: # screen # cvsup /etc/cvsup-stable ; grab the latest sources # cd /usr/src # make buildkernel KERNEL= # ctrl-A c ; creates a new virtual terminal # cd /usr/src; make buildworld # ctrl-A d ; detaches your current screen session At this point you wait a while. I typically start one of these at the end of the day and then go home. When I get home I can ssh into the machine: # ssh host.with.newworld.com # su - # screen -r ; reattaches me to my screen session Now I can see the output of the build commands and if everything looks good, I finish it up as follows: # make installworld # make installkernel # mergemaster # reboot Works like a charm nearly every time (on some older systems it's necessary to build the kernel the old way). Matt > -----Original Message----- > From: Daryl Chance [mailto:dchance@valuedata.net] > Sent: Wednesday, March 21, 2001 11:00 AM > To: mathieu@amx.dyn.dhs.org > Cc: freebsd-hackers@freebsd.org > Subject: Re: 4.3-BETA world crashing 4.2-RELEASE kernel ? > > > I may go about it wrong, but when I upgrade releases I do this: > > make buildworld > make installworld > reboot > > config > cd ../../conf/ > make depend && make && make install && reboot > > the gist, I think you need to build the world before the > kernal....that > *might* be your problem, I don't know :). > > HTH, > - > Daryl Chance | And which parallel universe did > ValueData, LLC | YOU crawl out of? > Memphis, TN | - http://www.thinkgeek.com > ----- Original Message ----- > From: "Mathieu" > To: "Daryl Chance" > Cc: > Sent: Wednesday, March 21, 2001 12:05 PM > Subject: Re: 4.3-BETA world crashing 4.2-RELEASE kernel ? > > > > Interesting.. I didn't know -O2 could do that. :p > > > > But I don't think I compiled with any optimisations, nothing in my > > make.conf, nothing in my kernel config file. What I did to > upgrade was > > CVSup, Backuping /etc, make buildkernel, make buildworld, make > > installkernel, reboot, make installworld, reboot, > mergemaster, reboot ! > > And then it worked fine for 24 hours ! Did I foget something ? > > > > Daryl Chance wrote: > > > > > > Are you compiling with any optimizations? I had a problem similar > > > to this in that ssh, ftp, apache were running, and I could connect > > > on my internal network....but connections from the > outside (like me > > > trying to connect to it from work) would either make it seem the > > > machine was "locked down". you could ping and see that it was > > > alive, but you couldn't get in through SSH or anything else. I > > > traced it down to a compile I did with kernal optimizations (-02), > > > so I turned that off, rebuilt the kernal, rebooted and > all was fine. > > > > > > - > > > Daryl Chance | And which parallel universe did > > > ValueData, LLC | YOU crawl out of? > > > Memphis, TN | - http://www.thinkgeek.com > > > ----- Original Message ----- > > > From: "Mathieu" > > > To: > > > Sent: Wednesday, March 21, 2001 11:25 AM > > > Subject: 4.3-BETA world crashing 4.2-RELEASE kernel ? > > > > > > > Hello ! > > > > > > > > First, sorry I don't speak English very well :p Usually > speak French ! > > > > > > > > I have a problem with a FreeBSD server that is far far > away, so I > don't > > > > have access to the console. As far as I know, it worked > fine with > > > > 4.2-RELEASE for... hmm, 2 days, then I upgraded it to the latest > STABLE > > > > (4.3-BETA), and the server worked fine for 24 hours or > so, but then, > the > > > > server locked up. It was still answering to pings, but > all daemons > > > > weren't responding anymore. I could still telnet to it, > but I was just > > > > not getting the login prompt, same thing for Apache, > FTP, SSH... I can > > > > connect, but no answers. > > > > > > > > I asked to reboot it many time. And each time, I can > telnet to it, and > > > > get the login prompt (!), but that's strange... seems > it can't fork a > > > > shell... I don't even get the motd, just the "Last > login from..." > thing. > > > > But sometime SendMail is working, and I could send mail > to the account > > > > previously created on the machine. But all the servers > always die in > > > > something like, 5 minutes.. Then it still answers to > pings, but just > no > > > > answers from Telnet/Apache/FTP, etc... :( > > > > > > > > However, the technicians there were able to do a make > world in single > > > > user mode, worked fine. But in multi user mode, the > server seems to > > > > consume all his ressources, and then processes start to crash > randomly, > > > > and there is also files corrumption, and always some > kind of error > > > > messages like "Cannot kill process", things like that, > they don't know > > > > what's causing this. > > > > > > > > Of course, technicians there want to bill me 100$ to reinstall > > > > 4.2-RELEASE.. hehehe :p But luckily, I've backuped a 4.2-RELEASE > kernel > > > > in the root. So, now, the computer does exactly the > same thing with > the > > > > 4.2 kernel, exactly. But those technicians still says > that the problem > > > > came from the 4.3-BETA environnement (hmm, the "world" > !), not the > > > > kernel, nor the hardware, so they have to "repair" what > I've broken > ($). > > > > :( > > > > > > > > So, is it safe to say that the world is indenpendent of > the hardware > so > > > > this problem should reproduce on all 4.3 system around > the planet > > > > (Hehehe, personnaly, it works fine on my computer ! > :p), or could this > > > > really be a bug NOT in the FreeBSD kernel that causes > the machine to > die > > > > in 5 minutes or so in multi user mode (even will it is idle !) ? > > > > > > > > Thanks ! And sorry for this long long long e-mail :p > > > > > > > > I've attached a DMESG from 4.2-RELEASE, sorry... I > don't have a more > > > > recent one. > > > > > > > > -- > > > > Mathieu > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 12: 7:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id A1B4437B735; Wed, 21 Mar 2001 12:07:03 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id B2FB05928C; Wed, 21 Mar 2001 12:06:20 -0600 (CST) Date: Wed, 21 Mar 2001 12:06:20 -0600 From: "Michael C . Wu" To: Rik van Riel Cc: Peter Wemm , Matt Dillon , Alfred Perlstein , "Michael C . Wu" , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver Message-ID: <20010321120620.A932@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <200103211114.f2LBE0h57371@mobile.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from riel@conectiva.com.br on Wed, Mar 21, 2001 at 01:31:45PM -0300 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 21, 2001 at 01:31:45PM -0300, Rik van Riel scribbled: | On Wed, 21 Mar 2001, Peter Wemm wrote: For those interested in this system: I have put up the kernel profiles at http://zoo.ee.ntu.edu.tw/~keichii/kernel_profiles/ This is kgmon -rb ;sleep 30;kgmon -hp ran every minute on the system by cron. i will let this run for more than 72 hours to get a feel for the usage peak and lows. In addition, this should provide for a good study of how FreeBSD 4.2 operates under high load in SMP. ckbdevent+0x1b9 atkbd_intr(c029c860,0,bfbfd2a4,c0227dbf,c029c860) at atkbd_intr+0x22 atkbd_isa_intr(c029c860,0,3011002f,2f,bfbf002f) at atkbd_isa_intr+0x18 Xresume1() at Xresume1+0x35 interrupt, eip = 0x807ca7b, esp = 0xf5cbffe0, ebp = 0xbfbfd2a4 db> Well, I know this trace is somewhat useless because of ctrl-alt-esc interrupt. The box did not crash today after we : A) Took out MFS/Md0 B) Added 3gb of swap on one drive, 1gb of swap on a raid volume another 1gb swap on another raid volume C) enabled vfs.vmiodirenable and kern.ipc.shm_use_phys -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 12:35:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 9E6D237B752 for ; Wed, 21 Mar 2001 12:35:06 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2LKTvh01013; Wed, 21 Mar 2001 12:29:59 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103212029.f2LKTvh01013@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: thomas@cuivre.fr.eu.org Cc: freebsd-hackers@freebsd.org Subject: Re: SCSI-over-* hacks In-reply-to: Your message of "Wed, 21 Mar 2001 11:32:39 +0100." <20010321113239.B37126@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Wed, 21 Mar 2001 12:29:57 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > SCSI is way of encapsulating scanner commands so that you can transpo= rt = > > them to the scanner. So is USB. The command set your scanner uses i= s = > > probably the same as the SCSI command set, but this is not what a CAM= = > > transport would give you - it would only give you the layers beneath,= = > > which would not be useful, since you already have this in the form of= USB. > = > Um. The CAM tranport in question would not be a reimplementation of > the USB layer, of course. What I was mentioning was the possibility > of having a CAM transport that wraps a uscan device (just as there is > one already that wraps umass devices to make them appear as SCSI disks)= =2E umass is useful because it allows reuse of the 'da' driver. There isn't = an equivalent for scanners, which is my point. > This would allow all USB scanners that use an SCSI command set to be > accessible through pass*, and thus be supported by any scanning softwar= e > that can use a SCSI scanner. It would be simpler (and more sensible) to simply fix this software to = send the SCSI commands via the ugen interface. -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 12:36:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 37D7237B71C for ; Wed, 21 Mar 2001 12:36:19 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2LKVGh01261; Wed, 21 Mar 2001 12:31:16 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103212031.f2LKVGh01261@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Soren Schmidt Cc: thomas@cuivre.fr.eu.org, freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI-over-* hacks In-reply-to: Your message of "Wed, 21 Mar 2001 11:48:01 +0100." <200103211048.LAA35280@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Wed, 21 Mar 2001 12:31:16 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It is a possible solution for me to be able to use cdparanoia and cdr= dao > > with my ATAPI CD drive. An alternative solution would be to implement= > > an atapi-cd ioctl to send a raw command to an ATAPI device, and make > > libscg use that. > = > Exactly, I coule dream up an API for that shoving ATAPI commands into > the ATA driver, that would make at least some sense... As long as you can make it work for ATA commands as well, this would let = us port/whatever the 'hdparm' tool as well, which would make a lot of = people happy. -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 12:41:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 39B2837B71C for ; Wed, 21 Mar 2001 12:41:07 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2LKcNh01400; Wed, 21 Mar 2001 12:38:23 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103212038.f2LKcNh01400@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Marco van de Voort" Cc: freebsd-hackers@freebsd.org Subject: Re: Opinion asked: unicode encoding In-reply-to: Your message of "Wed, 21 Mar 2001 19:51:49 +0100." <20010321190042.37A822E802@hermes.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Mar 2001 12:38:23 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The fpc core team is currently working on unicode support for Free > Pascal, a pascal compiler that runs on FreeBSD/i386, and I would > like to ask your opinion about what encoding to choose for the > default multibyte string type. (Delphi's WideString), choices are UTF- > 8 , -16 or UCS4. Read the NFSv4 specification (rfc3010) for a good discussion on why they chose UTF-8. I suspect that if FreeBSD makes a decision, it will probably go the same way. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 12:55: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id D872037B72E for ; Wed, 21 Mar 2001 12:54:49 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2LKpZM96124; Wed, 21 Mar 2001 12:51:35 -0800 (PST) (envelope-from obrien) Date: Wed, 21 Mar 2001 12:51:35 -0800 From: "David O'Brien" To: "Alexander N. Kabaev" Cc: hackers@FreeBSD.ORG Subject: Re: GCC Upgrade? Message-ID: <20010321125134.B95898@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010321094638.E92274@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ak03@gte.com on Wed, Mar 21, 2001 at 01:35:30PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 21, 2001 at 01:35:30PM -0500, Alexander N. Kabaev wrote: > This patch will work. According to Berndt Schimidt, there are some problems > with it on HP/UX and that was the main reason why it was backed out. That I knew, but I never saw the details (I may have missed them in the GCC mailing lists). Nor why they couldn't add conditional code to do the old way on hpux, and fixed sjlj exceptions everywhere else. Since this bug greatly affects both FreeBSD and OpenBSD (Linux does not use sjlj), we BSD's are the greatest consumer of the sjlj code. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 13: 1:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id 5DB0B37B71A for ; Wed, 21 Mar 2001 13:01:31 -0800 (PST) (envelope-from reichert@natto.numachi.com) Received: (qmail 16454 invoked by uid 3001); 21 Mar 2001 19:10:26 -0000 Received: from natto.numachi.com (198.175.254.216) by numachi.numachi.com with SMTP; 21 Mar 2001 19:10:26 -0000 Received: (qmail 47332 invoked by uid 1001); 21 Mar 2001 19:10:25 -0000 Date: Wed, 21 Mar 2001 14:10:25 -0500 From: Brian Reichert To: freebsd-hackers@freebsd.org Subject: FreeBSD on BookPC Message-ID: <20010321141025.X55383@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had luck with everything (but not X) with one of those slick little BookPCs and FreeBSD 4.2. Some notes here: I'd be happy to post more, of anyone can think of a particular set of stats they want to see... -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 13: 8:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.communitech.net (titan.communitech.net [209.15.2.49]) by hub.freebsd.org (Postfix) with SMTP id BD85D37B720 for ; Wed, 21 Mar 2001 13:08:35 -0800 (PST) (envelope-from troyc@titan.communitech.net) Received: from localhost ([209.15.2.49]) by titan.communitech.net ; Wed, 21 Mar 2001 21:06:04 -0000 Date: Wed, 21 Mar 2001 15:06:04 -0600 (CST) From: Troy Corbin To: Brian Reichert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on BookPC In-Reply-To: <20010321141025.X55383@numachi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian- On a cheapo spending spree, I bought 4 of the BookPC's and threw 4.2 on them. After disabling the modem, soundcard, etc in the BIOS, the only BAD thing ive experienced with them is occassional high latency to my gateway. Usually a reboot fixes this... Lately ive blamed it on the off-brand onboard NIC, but havent had time to dive into the problem deeper. Oh well, still a decent cheap solution. -troy On Wed, 21 Mar 2001, Brian Reichert wrote: > I've had luck with everything (but not X) with one of those slick > little BookPCs and FreeBSD 4.2. > > Some notes here: > > > > I'd be happy to post more, of anyone can think of a particular set > of stats they want to see... > > -- > Brian 'you Bastard' Reichert > 37 Crystal Ave. #303 Daytime number: (603) 434-6842 > Derry NH 03038-1713 USA Intel architecture: the left-hand path > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 13:11:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-97-45.gte.com [132.197.97.45]) by hub.freebsd.org (Postfix) with ESMTP id 88E1C37B718; Wed, 21 Mar 2001 13:11:06 -0800 (PST) (envelope-from ak03@gte.com) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.11.3/8.11.3) id f2LL93j77109; Wed, 21 Mar 2001 16:09:03 -0500 (EST) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.4.7p2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010321125134.B95898@dragon.nuxi.com> Date: Wed, 21 Mar 2001 16:09:03 -0500 (EST) Organization: Verizon Laboratories Inc. From: "Alexander N. Kabaev" To: "David O'Brien" Subject: Re: GCC Upgrade? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OpenBSD has my other patch committed for quite some time now. The patch fixes sjlj problems but does not deal with insane memory consumption in flow optimization - that is why I ported gcc-devel branch changes back to GCC 2.95.x and recommend everyone to use the new patch instead. On 21-Mar-2001 David O'Brien wrote: > On Wed, Mar 21, 2001 at 01:35:30PM -0500, Alexander N. Kabaev wrote: >> This patch will work. According to Berndt Schmidt, there are some problems >> with it on HP/UX and that was the main reason why it was backed out. > > That I knew, but I never saw the details (I may have missed them in the > GCC mailing lists). Something was going wrong when GCC was trying to run instruction scheduling pass on PA/RISC AFAIK. Berndt never really posted details about the problem though and I didn't ask because I couldn't help him anyway. > Nor why they couldn't add conditional code to do the > old way on hpux, and fixed sjlj exceptions everywhere else. Since this > bug greatly affects both FreeBSD and OpenBSD (Linux does not use sjlj), > we BSD's are the greatest consumer of the sjlj code. Um, my wild guess will be because they do not care as long as bug does not affect Linux. Furthermore, they seem to care about HP/UX more than about all BSDs of the universe together - hardly the news you didn't know already :) > > -- > -- David (obrien@FreeBSD.org) > GNU is Not Unix / Linux Is Not UniX ---------------------------------- E-Mail: Alexander N. Kabaev Date: 21-Mar-2001 Time: 15:53:05 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 13:23:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 44AB337B71E for ; Wed, 21 Mar 2001 13:23:45 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA11341; Wed, 21 Mar 2001 13:23:40 -0800 Date: Wed, 21 Mar 2001 13:23:35 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Brian Reichert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on BookPC In-Reply-To: <20010321141025.X55383@numachi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Really? DOes the davicom driver now work? BTW- I really haven't much liked my BooKPC. The NVRAM frotzed on it, and *just* try getting them on the phone... > I've had luck with everything (but not X) with one of those slick > little BookPCs and FreeBSD 4.2. > > Some notes here: > > > > I'd be happy to post more, of anyone can think of a particular set > of stats they want to see... > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 13:31:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id DE55C37B722 for ; Wed, 21 Mar 2001 13:31:27 -0800 (PST) (envelope-from reichert@natto.numachi.com) Received: (qmail 19916 invoked by uid 3001); 21 Mar 2001 21:31:25 -0000 Received: from natto.numachi.com (198.175.254.216) by numachi.numachi.com with SMTP; 21 Mar 2001 21:31:25 -0000 Received: (qmail 57447 invoked by uid 1001); 21 Mar 2001 21:31:25 -0000 Date: Wed, 21 Mar 2001 16:31:25 -0500 From: Brian Reichert To: Matthew Jacob Cc: Brian Reichert , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on BookPC Message-ID: <20010321163125.A55383@numachi.com> References: <20010321141025.X55383@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Wed, Mar 21, 2001 at 01:23:35PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 21, 2001 at 01:23:35PM -0800, Matthew Jacob wrote: > > Really? DOes the davicom driver now work? What, the sound driver? I only got as far as playing mp3s, and listening to CDs. I really have tried recording, etc... > BTW- I really haven't much liked my BooKPC. The NVRAM frotzed on it, and > *just* try getting them on the phone... I don't mind mine, but I'm having an awful time with my USB NIC killing the kernel. Given that that's happening on my laptop as well, I'm willing to blame the NIC there... -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 13:41:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id 4EE8237B71A; Wed, 21 Mar 2001 13:41:31 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA91416; Wed, 21 Mar 2001 21:55:06 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103212055.VAA91416@freebsd.dk> Subject: Re: SCSI-over-* hacks In-Reply-To: <200103212031.f2LKVGh01261@mass.dis.org> from Mike Smith at "Mar 21, 2001 12:31:16 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Wed, 21 Mar 2001 21:55:05 +0100 (CET) Cc: thomas@cuivre.fr.eu.org, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Mike Smith wrote: > > > It is a possible solution for me to be able to use cdparanoia and cdrdao > > > with my ATAPI CD drive. An alternative solution would be to implement > > > an atapi-cd ioctl to send a raw command to an ATAPI device, and make > > > libscg use that. > > > > Exactly, I coule dream up an API for that shoving ATAPI commands into > > the ATA driver, that would make at least some sense... > > As long as you can make it work for ATA commands as well, this would let > us port/whatever the 'hdparm' tool as well, which would make a lot of > people happy. What does hdparm do ? set modes and stuff right ? thats atacontrols job. I'll think up an API for getting ATAPI commands through, thats actually quite easy, we just have to get it right first time... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 13:49:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BE2C337B71A for ; Wed, 21 Mar 2001 13:49:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA11512; Wed, 21 Mar 2001 13:49:12 -0800 Date: Wed, 21 Mar 2001 13:49:07 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Brian Reichert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on BookPC In-Reply-To: <20010321163125.A55383@numachi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Mar 2001, Brian Reichert wrote: > On Wed, Mar 21, 2001 at 01:23:35PM -0800, Matthew Jacob wrote: > > > > Really? DOes the davicom driver now work? > > What, the sound driver? I only got as far as playing mp3s, and > listening to CDs. I really have tried recording, etc... Naw, the ethernet port... Larry McVoy (bitkeeper) has a pile of these and never could get the FreeBSD davicom driver working > > > BTW- I really haven't much liked my BooKPC. The NVRAM frotzed on it, and > > *just* try getting them on the phone... > > I don't mind mine, but I'm having an awful time with my USB NIC > killing the kernel. Given that that's happening on my laptop as > well, I'm willing to blame the NIC there... Oh- it's now got a USB nic? Maybe this is a different toy... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 13:59:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.numachi.com (numachi.numachi.com [198.175.254.2]) by hub.freebsd.org (Postfix) with SMTP id AFF0837B71A for ; Wed, 21 Mar 2001 13:59:22 -0800 (PST) (envelope-from reichert@natto.numachi.com) Received: (qmail 20691 invoked by uid 3001); 21 Mar 2001 21:59:19 -0000 Received: from natto.numachi.com (198.175.254.216) by numachi.numachi.com with SMTP; 21 Mar 2001 21:59:19 -0000 Received: (qmail 59487 invoked by uid 1001); 21 Mar 2001 21:59:19 -0000 Date: Wed, 21 Mar 2001 16:59:19 -0500 From: Brian Reichert To: Matthew Jacob Cc: Brian Reichert , freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on BookPC Message-ID: <20010321165919.B55383@numachi.com> References: <20010321163125.A55383@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Wed, Mar 21, 2001 at 01:49:07PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 21, 2001 at 01:49:07PM -0800, Matthew Jacob wrote: > On Wed, 21 Mar 2001, Brian Reichert wrote: > > > On Wed, Mar 21, 2001 at 01:23:35PM -0800, Matthew Jacob wrote: > > > > > > Really? DOes the davicom driver now work? > > > > What, the sound driver? I only got as far as playing mp3s, and > > listening to CDs. I really have tried recording, etc... > > Naw, the ethernet port... Larry McVoy (bitkeeper) has a pile of these and > never could get the FreeBSD davicom driver working Sorry, I was confused: the BookPC I have uses the sis(4) driver. This NIC is built onto the motherboard. It comes with two USB ports; I tried to use my USB NIC with this machine, and ran into a whole lot of grief. -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA Intel architecture: the left-hand path To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 14:26:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from kzsu.stanford.edu (KZSU.Stanford.EDU [171.66.118.90]) by hub.freebsd.org (Postfix) with ESMTP id 5440337B719 for ; Wed, 21 Mar 2001 14:26:30 -0800 (PST) (envelope-from romain@kzsu.stanford.edu) Received: (from romain@localhost) by kzsu.stanford.edu (8.9.3/8.9.3) id OAA71857 for hackers@FreeBSD.ORG; Wed, 21 Mar 2001 14:26:29 -0800 (PST) (envelope-from romain) Date: Wed, 21 Mar 2001 14:26:29 -0800 (PST) From: Romain Kang Message-Id: <200103212226.OAA71857@kzsu.stanford.edu> To: hackers@FreeBSD.ORG Subject: gdb /dev/mem? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there some way to make gdb work as a kernel memory reader on 4.2-RELEASE? It seems to insist on trying /proc/$$/mem: # gdb -k kernel.debug /dev/mem GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 3190784 initial pcb at 5b6b000 panic messages: --- --- #0 mi_switch () at ../../kern/kern_synch.c:858 858 if (switchtime.tv_sec == 0) (kgdb) x/d devtab_count 0x14: error reading /proc/454/mem Thanks, Romain Kang Disclaimer: I speak for myself alone, romain@kzsu.stanford.edu except when indicated otherwise. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 14:41: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from barry.mail.mindspring.net (barry.mail.mindspring.net [207.69.200.25]) by hub.freebsd.org (Postfix) with ESMTP id E9A0137B719 for ; Wed, 21 Mar 2001 14:41:04 -0800 (PST) (envelope-from cbsears@ix.netcom.com) Received: from ix.netcom.com (user-2ivfkg4.dialup.mindspring.com [165.247.210.4]) by barry.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id RAA29133; Wed, 21 Mar 2001 17:40:18 -0500 (EST) Message-ID: <3AB92ECF.EAACE3D8@ix.netcom.com> Date: Wed, 21 Mar 2001 14:44:31 -0800 From: Chris Sears X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.17-21mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: Alexey Dokuchaev Cc: freebsd-hackers@freebsd.org Subject: Re: Linux -> FreeBSD VM functions References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexey > static inline unsigned long > get_kvirt_address(unsigned long address) > { > } This function returns 0 if a virtual address is not mapped. Otherwise it returns the linear address associated with that virtual address by traversing the page table and extracting the physical address from mem_map, the reverse-mapped software pagetable. > Is simple PHYS_TO_VM_PAGE will do? No actually it would the other way around: VM_PAGE_TO_PHYS. But you have to get the vm_page of the virtual address first. Perhaps pmap_extract(pmap, va) might be more helpful but you will need the pmap of the process. > if (PageReserved(mem_map + GET_MAP_NR(page))) { ... } PG_reserved means that the page is reserved to the kernel. *Maybe* PG_UNMANAGED might be analogous. > > /* Page flag bit values */ > #define PG_locked 0 > #define PG_error 1 > #define PG_referenced 2 > #define PG_dirty 3 > #define PG_uptodate 4 > #define PG_free_after 5 > #define PG_decr_after 6 > #define PG_swap_unlock_after 7 > #define PG_DMA 8 > #define PG_Slab 9 > #define PG_swap_cache 10 > #define PG_skip 11 > #define PG_reserved 31 > > How do those relate to FreeBSD vision of things? Look at vm_page.h You should spend some quality time with Understanding the Linux Kernel especially chapter 6, and/or the Linux Commentary. And chapter 5 of Design and Implementation of 4.4BSD. And since the 4.4BSD vm is really the Mach vm you should look at that stuff too. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 14:51:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 861A337B71E for ; Wed, 21 Mar 2001 14:51:54 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2LMnNh02785; Wed, 21 Mar 2001 14:49:23 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103212249.f2LMnNh02785@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexey Dokuchaev Cc: freebsd-hackers@freebsd.org Subject: Re: Some PCI-related programming things In-reply-to: Your message of "Wed, 21 Mar 2001 15:25:34 +0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Mar 2001 14:49:22 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Because dinking with PCI configuration space is usually the wrong thing > > to do from userland. > > So what about pciconf(8)? It's a special case. > > > This code is used, actually, in char device driver. > > > > Mm, so what's it doing in userspace? 8) > > Did I say I'm doing it from userspace?! If I did (too lazy to dig into > sent-mail), I beg your pardon :) Your FreeBSD sample involved making an ioctl call, so it must have been from userspace. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 14:55:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 10D3337B71A for ; Wed, 21 Mar 2001 14:55:18 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2LMpah02805; Wed, 21 Mar 2001 14:51:36 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103212251.f2LMpah02805@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Chris Sears Cc: Alexey Dokuchaev , freebsd-hackers@freebsd.org Subject: Re: Linux -> FreeBSD VM functions In-reply-to: Your message of "Wed, 21 Mar 2001 14:44:31 PST." <3AB92ECF.EAACE3D8@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Mar 2001 14:51:36 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I appear to have missed the original version of this message. Oops. > Alexey > > > static inline unsigned long > > get_kvirt_address(unsigned long address) > > { > > } > > This function returns 0 if a virtual address is not mapped. If you're looking at using this function, you're almost certainly at the wrong level. FreeBSD provides a more complete mechanism for getting virtual mappings of device physical apertures, and you should use it. > No actually it would the other way around: VM_PAGE_TO_PHYS. > But you have to get the vm_page of the virtual address first. > Perhaps pmap_extract(pmap, va) might be more helpful > but you will need the pmap of the process. Typically, in non-PCI, non-PNP cases you would use pmap_mapdev(). Again, I'm sorry that I missed your previous message; I may be misunderstanding what you're trying to do here. If you could resend it privately, I'd appreciate it. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 14:57:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id E5F3337B718 for ; Wed, 21 Mar 2001 14:57:48 -0800 (PST) (envelope-from danfe@inet.ssc.nsu.ru) Received: (qmail 1335 invoked from network); 21 Mar 2001 22:57:44 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 21 Mar 2001 22:57:44 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id EAA26618; Thu, 22 Mar 2001 04:57:24 +0600 Date: Thu, 22 Mar 2001 04:57:24 +0600 (NOVT) From: Alexey Dokuchaev To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: Some PCI-related programming things In-Reply-To: <200103212249.f2LMnNh02785@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Mar 2001, Mike Smith wrote: > > > > This code is used, actually, in char device driver. > > > > > > Mm, so what's it doing in userspace? 8) > > > > Did I say I'm doing it from userspace?! If I did (too lazy to dig into > > sent-mail), I beg your pardon :) > > Your FreeBSD sample involved making an ioctl call, so it must have been > from userspace. Is anything wrong with using ioctl calls from device driver? -- WBR, Alexey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 15: 4:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 390AB37B71B for ; Wed, 21 Mar 2001 15:04:11 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2LN1Oh03009; Wed, 21 Mar 2001 15:01:24 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103212301.f2LN1Oh03009@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexey Dokuchaev Cc: freebsd-hackers@freebsd.org Subject: Re: Some PCI-related programming things In-reply-to: Your message of "Thu, 22 Mar 2001 04:57:24 +0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Mar 2001 15:01:24 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > Mm, so what's it doing in userspace? 8) > > > > > > Did I say I'm doing it from userspace?! If I did (too lazy to dig into > > > sent-mail), I beg your pardon :) > > > > Your FreeBSD sample involved making an ioctl call, so it must have been > > from userspace. > > Is anything wrong with using ioctl calls from device driver? Please go read a book on Unix device drivers, and perhaps the source for a couple of FreeBSD drivers before you ask any more questions. You're making my head hurt. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 15: 7:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C413F37B722 for ; Wed, 21 Mar 2001 15:07:16 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2LN4lh03035; Wed, 21 Mar 2001 15:04:47 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103212304.f2LN4lh03035@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexey Dokuchaev Cc: freebsd-hackers@freebsd.org Subject: Re: Some PCI-related programming things In-reply-to: Your message of "Thu, 22 Mar 2001 04:57:24 +0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Mar 2001 15:04:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Did I say I'm doing it from userspace?! If I did (too lazy to dig into > > > sent-mail), I beg your pardon :) > > > > Your FreeBSD sample involved making an ioctl call, so it must have been > > from userspace. > > Is anything wrong with using ioctl calls from device driver? Perhaps a more polite answer is called for. 8) Ioctls allow user processes to make function calls within a device driver; they are a mechanism for exporting functionality from a device driver out into userspace. You don't call them from other device drivers, no. There are exported interfaces inside the kernel for doing this, and you will understand everything much better if you go look at a simple FreeBSD PCI device driver, particularly the _probe and _attach functions. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 15:19:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id 9226137B71F for ; Wed, 21 Mar 2001 15:19:08 -0800 (PST) (envelope-from danfe@inet.ssc.nsu.ru) Received: (qmail 1544 invoked from network); 21 Mar 2001 23:19:06 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 21 Mar 2001 23:19:06 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id FAA26677; Thu, 22 Mar 2001 05:18:50 +0600 Date: Thu, 22 Mar 2001 05:18:50 +0600 (NOVT) From: Alexey Dokuchaev To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: Some PCI-related programming things In-Reply-To: <200103212304.f2LN4lh03035@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Mar 2001, Mike Smith wrote: > > > > Did I say I'm doing it from userspace?! If I did (too lazy to dig into > > > > sent-mail), I beg your pardon :) > > > > > > Your FreeBSD sample involved making an ioctl call, so it must have been > > > from userspace. > > > > Is anything wrong with using ioctl calls from device driver? > > Perhaps a more polite answer is called for. 8) > > Ioctls allow user processes to make function calls within a device > driver; they are a mechanism for exporting functionality from a device > driver out into userspace. I know that, of course. > You don't call them from other device drivers, no. There are exported > interfaces inside the kernel for doing this, and you will understand > everything much better if you go look at a simple FreeBSD PCI device > driver, particularly the _probe and _attach functions. Look, I am *not* coding a PCI driver. I have looked at various examples in sound/pci/ and I know what PCI device driver should look like. What I am doing is *porting* linux *character* device driver to FreeBSD. That is, if original version called all that linuxish pci_whatever() functions, I have to provide the same functionality under FreeBSD. I didn't know how to do this. What I did was, I said man pci, from there I figured out about pciconf utility. I took a look at it, and thought, ok, this must be the way I have to go for under FreeBSD. At first, I thought I calling ioctl's from kernel space is probably at least weird idea (if not to call it bad). But I was unable to find any PCI-related doc which would answer my questions. Trust me, if I wanted to code a PCI dev driver, I would certainly not do this. I have a code to take a look at, and I only ask questions when I seem to fail to comprehend going of things from the code. It's not written anywhere I can't use ioctl from char device driver. Or is it? -- Me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 15:24:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from titan.communitech.net (titan.communitech.net [209.15.2.49]) by hub.freebsd.org (Postfix) with SMTP id D132537B71E for ; Wed, 21 Mar 2001 15:24:40 -0800 (PST) (envelope-from troyc@titan.communitech.net) Received: from localhost ([209.15.2.49]) by titan.communitech.net ; Wed, 21 Mar 2001 23:24:35 -0000 Date: Wed, 21 Mar 2001 17:24:35 -0600 (CST) From: Troy Corbin To: reichert@numachi.com, freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on BookPC Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian- On a cheapo spending spree, I bought 4 of the BookPC's and threw 4.2 on them. After disabling the modem, soundcard, etc in the BIOS, the only BAD thing ive experienced with them is occassional high latency to my gateway. Usually a reboot fixes this... Lately ive blamed it on the off-brand onboard NIC, but havent had time to dive into the problem deeper. Oh well, still a decent cheap solution. -troy On Wed, 21 Mar 2001, Brian Reichert wrote: > I've had luck with everything (but not X) with one of those slick > little BookPCs and FreeBSD 4.2. > > Some notes here: > > > > I'd be happy to post more, of anyone can think of a particular set > of stats they want to see... > > -- > Brian 'you Bastard' Reichert > 37 Crystal Ave. #303 Daytime number: (603) 434-6842 > Derry NH 03038-1713 USA Intel architecture: the left-hand path > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 15:30: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id EB42C37B71E for ; Wed, 21 Mar 2001 15:30:05 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2LNReh03247; Wed, 21 Mar 2001 15:27:40 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103212327.f2LNReh03247@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexey Dokuchaev Cc: hackers@freebsd.org Subject: Re: Some PCI-related programming things In-reply-to: Your message of "Thu, 22 Mar 2001 05:18:50 +0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 21 Mar 2001 15:27:40 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Ioctls allow user processes to make function calls within a device > > driver; they are a mechanism for exporting functionality from a device > > driver out into userspace. > > I know that, of course. This wasn't clear from your example. > > You don't call them from other device drivers, no. There are exported > > interfaces inside the kernel for doing this, and you will understand > > everything much better if you go look at a simple FreeBSD PCI device > > driver, particularly the _probe and _attach functions. > > Look, I am *not* coding a PCI driver. I have looked at various examples > in sound/pci/ and I know what PCI device driver should look like. Ok. So why are you attempting to manipulate PCI configuration space? > What I am doing is *porting* linux *character* device driver to FreeBSD. A device driver still talks to hardware, and by the sound of it, your hardware is PCI hardware. Since you won't actually tell me what it is you're actually doing with any sort of useful level of detail, it is very hard to give you useful answers. > That is, if original version called all that linuxish pci_whatever() > functions, I have to provide the same functionality under FreeBSD. I > didn't know how to do this. What I did was, I said man pci, from there I > figured out about pciconf utility. I took a look at it, and thought, ok, > this must be the way I have to go for under FreeBSD. You're writing a device driver. Look at other device drivers that behave similarly. Whether the driver has a character interface or not is more or less irrelevant at this stage. 8) > Trust me, if I wanted to code a PCI dev driver, I would certainly not do > this. I have a code to take a look at, and I only ask questions when I > seem to fail to comprehend going of things from the code. It's not > written anywhere I can't use ioctl from char device driver. Or is it? Firstly, there is no such thing as "a character device driver". Secondly, if it's running inside the kernel, it doesn't matter what it is; you don't make ioctl calls (exception: ABI shims). If you're not going to explain, in more specific terms, what it is you're doing, I'm just going to have to keep guessing. So far, I don't have enough to go on to give you very good answers; the more detail you give me, the better I can help you. If you don't like the answers you're getting, this should be a clue to you that you're not giving me enough detail. 8) Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 15:41:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.219.91]) by hub.freebsd.org (Postfix) with SMTP id 86F0137B718 for ; Wed, 21 Mar 2001 15:41:49 -0800 (PST) (envelope-from danfe@inet.ssc.nsu.ru) Received: (qmail 1584 invoked from network); 21 Mar 2001 23:41:48 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 21 Mar 2001 23:41:48 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.9.3/8.9.3) with ESMTP id FAA26741; Thu, 22 Mar 2001 05:41:31 +0600 Date: Thu, 22 Mar 2001 05:41:31 +0600 (NOVT) From: Alexey Dokuchaev To: Mike Smith Cc: hackers@freebsd.org Subject: Re: Some PCI-related programming things In-Reply-To: <200103212327.f2LNReh03247@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 21 Mar 2001, Mike Smith wrote: > > > Ioctls allow user processes to make function calls within a device > > > driver; they are a mechanism for exporting functionality from a device > > > driver out into userspace. > > > > I know that, of course. > > This wasn't clear from your example. Oh, OK, sorry... > > > You don't call them from other device drivers, no. There are exported > > > interfaces inside the kernel for doing this, and you will understand > > > everything much better if you go look at a simple FreeBSD PCI device > > > driver, particularly the _probe and _attach functions. > > > > Look, I am *not* coding a PCI driver. I have looked at various examples > > in sound/pci/ and I know what PCI device driver should look like. > > Ok. So why are you attempting to manipulate PCI configuration space? > > > What I am doing is *porting* linux *character* device driver to FreeBSD. > > A device driver still talks to hardware, and by the sound of it, your > hardware is PCI hardware. Since you won't actually tell me what it is > you're actually doing with any sort of useful level of detail, it is very > hard to give you useful answers. > > > That is, if original version called all that linuxish pci_whatever() > > functions, I have to provide the same functionality under FreeBSD. I > > didn't know how to do this. What I did was, I said man pci, from there I > > figured out about pciconf utility. I took a look at it, and thought, ok, > > this must be the way I have to go for under FreeBSD. > > You're writing a device driver. Look at other device drivers that behave > similarly. Whether the driver has a character interface or not is more > or less irrelevant at this stage. 8) OK, I'll do. Frankly, device driver is easy part, I would eventually figure it out. What makes me worry is that VM staff... > > Trust me, if I wanted to code a PCI dev driver, I would certainly not do > > this. I have a code to take a look at, and I only ask questions when I > > seem to fail to comprehend going of things from the code. It's not > > written anywhere I can't use ioctl from char device driver. Or is it? > > Firstly, there is no such thing as "a character device driver". > Secondly, if it's running inside the kernel, it doesn't matter what it > is; you don't make ioctl calls (exception: ABI shims). OK, I understand. Thanks for explanations, and sorry for somewhat lame questions. The rest is probably going to be rather obvious, given your information + tons of source code I will surely look at :) -- Me To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 17:28:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id 6888337B71C for ; Wed, 21 Mar 2001 17:28:44 -0800 (PST) (envelope-from cbsears@ix.netcom.com) Received: from ix.netcom.com (user-2ivfm4q.dialup.mindspring.com [165.247.216.154]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id UAA15133 for ; Wed, 21 Mar 2001 20:28:42 -0500 (EST) Message-ID: <3AB95647.B8F646DE@ix.netcom.com> Date: Wed, 21 Mar 2001 17:32:55 -0800 From: Chris Sears X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.17-21mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: Linux -> FreeBSD VM functions References: <200103212251.f2LMpah02805@mass.dis.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike > > FreeBSD provides a more complete mechanism for getting virtual mappings > of device physical apertures, and you should use it. > > > No actually it would the other way around: VM_PAGE_TO_PHYS. > > But you have to get the vm_page of the virtual address first. > > Perhaps pmap_extract(pmap, va) might be more helpful > > but you will need the pmap of the process. > > Typically, in non-PCI, non-PNP cases you would use pmap_mapdev(). He was looking for virtual to physical mapping rather than allocation. pmap_mapdev allocates: /* * Map a set of physical memory pages into the kernel virtual * address space. Return a pointer to where it is mapped. This * routine is intended to be used for mapping device memory, * NOT real memory. The non-cacheable bits are set on each * mapped page. */ But in any case, he should hit the books. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 17:52:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 50E7637B71F for ; Wed, 21 Mar 2001 17:52:47 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id UAA88304 for ; Wed, 21 Mar 2001 20:52:45 -0500 (EST) Message-Id: <200103220152.UAA88304@cs.rpi.edu> To: hackers@freebsd.org Subject: gif(4) question Date: Wed, 21 Mar 2001 20:52:45 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently tried (for the first time) to get gif running under FreeBSD 4.3-BETA (cvsup-ed yesterday). I noticed the following: gifconfig gif0 inet 10.1.1.1 10.1.2.1 ifconfig gif0 192.168.1.1 192.168.1.2 netmask 0xffffff00 and then I 'ping 192.168.1.1' it will try to route the packet instead of reply directly. I need to 'route add 192.168.1.1 127.0.0.1' to have it reply to the packet directly. I don't need to do this for other types of interfaces... did I mess something up, is this how it is supposed to be (doesn't seem to be documented as such). -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 20:25: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 20D1A37B71F; Wed, 21 Mar 2001 20:24:58 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id UAA11694; Wed, 21 Mar 2001 20:24:52 -0800 (PST) Date: Wed, 21 Mar 2001 20:24:51 -0800 (PST) From: Julian Elischer To: Alexey Dokuchaev Cc: Mike Smith , hackers@freebsd.org Subject: Re: Some PCI-related programming things In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look at the sample device driver in /usr/share/examples/drivers make_device_driver.sh The one in -current is 'up to date' (retreive it from the CVS web pages) the one in -stable is hopelessly out of date. I'd MFC but I don't know what needs to be changed to make it work in 4.x and I don't have a 4.x machine.. It should pretty much work for PCI devices in -stable On Thu, 22 Mar 2001, Alexey Dokuchaev wrote: > > OK, I understand. Thanks for explanations, and sorry for somewhat lame > questions. The rest is probably going to be rather obvious, given your > information + tons of source code I will surely look at :) > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 20:40:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 1157A37B718 for ; Wed, 21 Mar 2001 20:40:49 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2M4egJ01573; Wed, 21 Mar 2001 20:40:42 -0800 (PST) (envelope-from obrien) Date: Wed, 21 Mar 2001 20:40:41 -0800 From: "David O'Brien" To: Matt Simerson Cc: freebsd-hackers@freebsd.org Subject: Re: 4.3-BETA world crashing 4.2-RELEASE kernel ? Message-ID: <20010321204041.A1425@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <8D18712B2604D411A6BB009027F6449801B4B53D@0SEA01EXSRV1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8D18712B2604D411A6BB009027F6449801B4B53D@0SEA01EXSRV1>; from mpsimerson@hostpro.com on Wed, Mar 21, 2001 at 12:58:04PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First let me say to anyone reading the email I am replying to: ____ _ _ ___ _____ _ _ _ _ | _ \ ___ | \ | |/ _ \_ _| __| | ___ | |_| |__ (_)___ | | | |/ _ \ | \| | | | || | / _` |/ _ \ | __| '_ \| / __| | |_| | (_) | | |\ | |_| || | | (_| | (_) | | |_| | | | \__ \ |____/ \___/ |_| \_|\___/ |_| \__,_|\___/ \__|_| |_|_|___/ On Wed, Mar 21, 2001 at 12:58:04PM -0700, Matt Simerson wrote: > # cd /usr/src > # make buildkernel KERNEL= > # cd /usr/src; make buildworld > # make installworld > # make installkernel > # mergemaster > # reboot The order or "make buildworld" and "make buildkernel" are 100% totally BACKWARDS. Lets explain why: There are times when the kernel source is changed to use constructs of newer compiler/assembler/linker tools. Thus the kernel will not build with an older set of tools. The what "make buildkernel" does is use the tools (ie, those built from the most up to date sources) that are built during "make buildworld" to compile a new kernel. Thus "make buildworld" must PROCEED "make buildkernel". Second, the install order above is not the conservative, careful approach. One should issue "make installkernel && reboot" after the "make buildkernel" to ensure the new kernel works sufficiently well. If not, one can always fall back to ``kernel.old''. Since there is no ``world.old''; after one does the "make installworld" backup tapes are the only way of taking the system back to its previous state. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 20:50:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id B269D37B71A; Wed, 21 Mar 2001 20:50:15 -0800 (PST) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id UAA11790; Wed, 21 Mar 2001 20:52:05 -0800 (PST) Date: Wed, 21 Mar 2001 20:52:04 -0800 (PST) From: Julian Elischer To: "David O'Brien" Cc: Matt Simerson , freebsd-hackers@freebsd.org Subject: Re: In general, how to upgrade by rebuilding.. In-Reply-To: <20010321204041.A1425@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would also add that new kernels are almost always capable of running old binaries but the reverse is often not true.. Old kernels can often not run new binaries. (new API additions etc.) So alwyas make and install a new kernel first. (Even if you call it kernel.new or something) that way if it is bad you can still boot you old system. Then build and install your new system, running on the new kernel. On Wed, 21 Mar 2001, David O'Brien wrote: > First let me say to anyone reading the email I am replying to: > > ____ _ _ ___ _____ _ _ _ _ > | _ \ ___ | \ | |/ _ \_ _| __| | ___ | |_| |__ (_)___ > | | | |/ _ \ | \| | | | || | / _` |/ _ \ | __| '_ \| / __| > | |_| | (_) | | |\ | |_| || | | (_| | (_) | | |_| | | | \__ \ > |____/ \___/ |_| \_|\___/ |_| \__,_|\___/ \__|_| |_|_|___/ > > > > On Wed, Mar 21, 2001 at 12:58:04PM -0700, Matt Simerson wrote: > > # cd /usr/src > > # make buildkernel KERNEL= > > # cd /usr/src; make buildworld > > # make installworld > > # make installkernel > > # mergemaster > > # reboot > > > The order or "make buildworld" and "make buildkernel" are 100% totally > BACKWARDS. > > Lets explain why: There are times when the kernel source is changed to > use constructs of newer compiler/assembler/linker tools. Thus the kernel > will not build with an older set of tools. The what "make buildkernel" > does is use the tools (ie, those built from the most up to date sources) > that are built during "make buildworld" to compile a new kernel. Thus > "make buildworld" must PROCEED "make buildkernel". > > Second, the install order above is not the conservative, careful > approach. One should issue "make installkernel && reboot" after the > "make buildkernel" to ensure the new kernel works sufficiently well. If > not, one can always fall back to ``kernel.old''. Since there is no > ``world.old''; after one does the "make installworld" backup tapes are > the only way of taking the system back to its previous state. > > -- > -- David (obrien@FreeBSD.org) > GNU is Not Unix / Linux Is Not UniX > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 22:43: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.prod.itd.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 63F9A37B71B for ; Wed, 21 Mar 2001 22:42:58 -0800 (PST) (envelope-from gvirdi@gvirdi.com) Received: from dhgfhcpps5nhe1 (ip89.schiller-park8.il.pub-ip.psi.net [38.31.125.89]) by snipe.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id WAA14847 for ; Wed, 21 Mar 2001 22:42:56 -0800 (PST) Message-ID: <000d01c0b29b$2196cd60$050101c0@dhgfhcpps5nhe1> From: "Gurpratap Virdi" To: Subject: Fw: Debugging kernel crashes Date: Thu, 22 Mar 2001 00:41:29 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I made some modifications to the FreeBSD kernel which causes it to crash. I was trying to determine the line number and file of the code that causes the crash using the instructions given at http://www.freebsd.org/handbook/kerneldebug.html I have the following questions related to the above instructions though. I understand we can use dumpon(8) to tell the kernel to dump the core file to a swap partition. If our system is only configured with one swap partition, can we still point the kernel to this partition? I mean would the core file get overwritten when the system reboots and uses the space as swap again. Now, supposedly the kernel is able to write the core file to the swap partition and the system reboots without overwriting the core file, how do we access the core file? Thanks in advance for your help!! Regards, Virdi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 22:47:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id DC50237B71B for ; Wed, 21 Mar 2001 22:47:32 -0800 (PST) (envelope-from dscheidt@tumbolia.com) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.11.1/8.11.2) with ESMTP id f2M6lRl73857; Thu, 22 Mar 2001 00:47:27 -0600 (CST) (envelope-from dscheidt@tumbolia.com) Date: Thu, 22 Mar 2001 00:47:26 -0600 (CST) From: David Scheidt X-Sender: dscheidt@shell-2.enteract.com To: Gurpratap Virdi Cc: freebsd-hackers@freebsd.org Subject: Re: Fw: Debugging kernel crashes In-Reply-To: <000d01c0b29b$2196cd60$050101c0@dhgfhcpps5nhe1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Mar 2001, Gurpratap Virdi wrote: :Hi, : : :I have the following questions related to the above instructions though. :I understand we can use dumpon(8) to tell the kernel to dump the core file :to a swap partition. If our system is only configured with one swap :partition, can we still point the kernel to this partition? I mean would Yes. Your dump partition should be at least as large as your physical memory. :the core file get overwritten when the system reboots and uses the space as :swap again. Now, supposedly the kernel is able to write the core file to the :swap partition and the system reboots without overwriting the core file, how :do we access the core file? savecore(8) will copy the dump to /var/crash at startup. /var/crash needs to be big enough ot hold the dump, and the running kernel. -- dscheidt@tumbolia.com Bipedalism is only a fad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 22:59:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from w250.z064001178.sjc-ca.dsl.cnc.net (w250.z064001178.sjc-ca.dsl.cnc.net [64.1.178.250]) by hub.freebsd.org (Postfix) with SMTP id 7C05437B71B for ; Wed, 21 Mar 2001 22:59:33 -0800 (PST) (envelope-from josb@cncdsl.com) Received: (qmail 64273 invoked by uid 1000); 22 Mar 2001 06:59:45 -0000 Date: Wed, 21 Mar 2001 22:59:23 -0800 From: Jos Backus To: freebsd-hackers@freebsd.org Subject: make .PREFIX question Message-ID: <20010321225923.A64237@lizzy.bugworks.com> Reply-To: Jos Backus Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /tmp% cat Makefile .SUFFIXES: .txt foo/bar.txt: a b @echo ${.TARGET}, ${.OODATE}, ${.ALLSRC}, ${.PREFIX} a b: echo $* /tmp% mkdir foo /tmp% touch b; make gives foo/bar.txt, b, a b, foo/bar instead of foo/bar.txt, b, a b, bar even though man make(1) says .PREFIX The file prefix of the file, containing only the file portion, no suffix or preceding directory components; also known as `*'. What am I missing? Thanks, -- Jos Backus _/ _/_/_/ "Modularity is not a hack." _/ _/ _/ -- D. J. Bernstein _/ _/_/_/ _/ _/ _/ _/ josb@cncdsl.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Mar 21 23:46:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.newst.irs.ru (newst.irs.ru [212.164.94.1]) by hub.freebsd.org (Postfix) with ESMTP id 1D28637B71C for ; Wed, 21 Mar 2001 23:46:15 -0800 (PST) (envelope-from fjoe@newst.net) Received: from lark.nsk.bsgdesign.com (lark.nsk.bsgdesign.com [192.168.3.21]) by mail.newst.irs.ru (8.11.1/8.11.0) with ESMTP id f2M7k3h47189; Thu, 22 Mar 2001 13:46:09 +0600 (NOVT) (envelope-from fjoe@newst.net) Date: Thu, 22 Mar 2001 13:46:03 +0600 (NOVT) From: Max Khon X-Sender: fjoe@localhost To: Titus von Boxberg Cc: hackers@FreeBSD.ORG Subject: Re: GCC Upgrade? In-Reply-To: <3AB7C787.96200D6C@pleach-hamburg.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Tue, 20 Mar 2001, Titus von Boxberg wrote: > Is there a link available to documentation that explains DWARF and fsjlf except.c from gcc sources (/usr/src/contrib/gcc/except.c) /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 2:18:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id 1268037B719; Thu, 22 Mar 2001 02:18:08 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.chronias.ninth-circle.org (root@cable.ninth-circle.org [195.38.232.6]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id f2MAI5i87231; Thu, 22 Mar 2001 11:18:05 +0100 (CET) Received: (from asmodai@localhost) by daemon.chronias.ninth-circle.org (8.11.2/8.11.0) id f2MAHxX07751; Thu, 22 Mar 2001 11:17:59 +0100 (CET) (envelope-from asmodai) Date: Thu, 22 Mar 2001 11:17:58 +0100 From: Jeroen Ruigrok/Asmodai To: "David E. Cross" Cc: net@freebsd.org Subject: Re: gif(4) question Message-ID: <20010322111758.A7147@daemon.ninth-circle.org> References: <200103220152.UAA88304@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200103220152.UAA88304@cs.rpi.edu>; from crossd@cs.rpi.edu on Wed, Mar 21, 2001 at 08:52:45PM -0500 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [This question is more appropriate for -net IMHO] -On [20010322 03:00], David E. Cross (crossd@cs.rpi.edu) wrote: >I recently tried (for the first time) to get gif running under FreeBSD >4.3-BETA (cvsup-ed yesterday). I noticed the following: > >gifconfig gif0 inet 10.1.1.1 10.1.2.1 >ifconfig gif0 192.168.1.1 192.168.1.2 netmask 0xffffff00 > >and then I 'ping 192.168.1.1' it will try to route the packet instead of >reply directly. I need to 'route add 192.168.1.1 127.0.0.1' to have it >reply to the packet directly. I don't need to do this for other types >of interfaces... did I mess something up, is this how it is supposed to >be (doesn't seem to be documented as such). I think that's how it is supposed to be given that gif's main function is to tunnel things and it works on a point-to-point basis. I might be wrong, in which case I am sure UMEMOTO-san or ITOJUN-san will correct me. -- Jeroen Ruigrok van der Werven/Asmodai .oUo. asmodai@[wxs.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 What is to be, will be. And what isn't to be sometimes happens... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 3: 5:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from db.wireless.net (adsl-gte-la-216-86-194-70.mminternet.com [216.86.194.70]) by hub.freebsd.org (Postfix) with ESMTP id 521E237B71F for ; Thu, 22 Mar 2001 03:05:39 -0800 (PST) (envelope-from dbutter@wireless.net) Received: from dbm.wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with SMTP id SAA46341; Mon, 19 Mar 2001 18:13:53 -0800 (PST) (envelope-from dbutter@wireless.net) Content-Type: text/plain; charset="iso-8859-1" From: Devin Butterfield To: Will Andrews , Dennis Subject: Re: Routing latency Date: Mon, 19 Mar 2001 18:11:55 -0800 X-Mailer: KMail [version 1.2] Cc: Thierry Herbelot , =?iso-8859-1?q?M=E5rten=20Wikstr=F6m?= , "'freebsd-hackers@freebsd.org'" References: <5.0.0.25.0.20010319191312.03fd65d0@mail.etinc.com> <5.0.0.25.0.20010319194401.040862b0@mail.etinc.com> <20010319193604.Q61859@ohm.physics.purdue.edu> In-Reply-To: <20010319193604.Q61859@ohm.physics.purdue.edu> MIME-Version: 1.0 Message-Id: <01031918115500.51096@dbm.wireless.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday 19 March 2001 4:36, Will Andrews wrote: > On Mon, Mar 19, 2001 at 07:46:53PM -0500, Dennis wrote: > > I never got an answer (as usual) from bill paul when I made the > > suggestions, and noone seemed interested in getting it fixed. He seems to > > get insulted when I infer that he did something wrong. > > It's like they say: "money talks". Similarly, "patches talk". > Suggestions don't really do that. I'm not defending Dennis here, but this statement infers that nothing gets done unless maintainers are a) paid or b) someone else does the work for them. I certainly hope this is not the case. -- Regards, Devin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 3: 8:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hell.branda.to (61-216-80-11.HINET-IP.hinet.net [61.216.80.11]) by hub.freebsd.org (Postfix) with ESMTP id 6656237B71F for ; Thu, 22 Mar 2001 03:08:14 -0800 (PST) (envelope-from thinker@branda.to) Received: from localhost (localhost [127.0.0.1]) (uid 1000) by hell.branda.to with local; Thu, 22 Mar 2001 19:10:57 +0000 Date: Thu, 22 Mar 2001 19:10:57 +0000 From: thinker To: Rik van Riel Cc: hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver Message-ID: <20010322191057.A46607@hell.branda.to> References: <200103211840.f2LIeYA16476@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from riel@conectiva.com.br on Wed, Mar 21, 2001 at 04:14:32PM -0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 21, 2001 at 04:14:32PM -0300, Rik van Riel wrote: > The (maybe too lightweight) structure I have in my patch > looks like this: > > struct pte_chain { > struct pte_chain * next; > pte_t * ptep; > }; > > Each pte_chain hangs off a page of physical memory and the > ptep is a pointer to a page table entry. > > The page struct of the page table page itself is used to > note down which address space and offset we have. This means > that FreeBSD's pv_pmap, pv_va and pv_ptem are in the page > table page and NOT in each pte_chain structure... How about portability? It maybe efficient, but it is not easy to port to other platforms. -- thinker@branda.to Branda Open Site (BOS) thinker.bbs@bbs.yzu.edu.tw http://www.branda.to/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 4:33:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from germes.levi.spb.ru (ip65.levi.spb.ru [212.119.175.65]) by hub.freebsd.org (Postfix) with ESMTP id 8CCD737B722 for ; Thu, 22 Mar 2001 04:33:16 -0800 (PST) (envelope-from dms@wplus.net) Received: from wplus.net (IDENT:dms@pike.levi.spb.ru [10.246.8.43]) by germes.levi.spb.ru (8.11.1/8.11.1) with ESMTP id f2MCXE719792 for ; Thu, 22 Mar 2001 15:33:15 +0300 Message-ID: <3AB9F10A.714B2433@wplus.net> Date: Thu, 22 Mar 2001 15:33:14 +0300 From: Dmitry Samersoff Organization: LeviSoft X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.18 i686) X-Accept-Language: ru, en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Help please (Server crash) Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have server under FreeBSD 4.2 with apache fired simple C++ CGI for each connection. Aproximately every 12H uptime server stop responding. Kernel answers to ping, establish TCP connection but unable to fork process. (no messages in /var/log/messages) This is statisitics (netstat -nm & top ) just before crash. Any ideas? Thank you! # Thu Mar 22 00:50:00 MSK 2001 # 4945/6928/40960 mbufs in use (current/peak/max): # 2604 mbufs allocated to data # 2341 mbufs allocated to packet headers # 2530/3804/10240 mbuf clusters in use (current/peak/max) # 9340 Kbytes allocated to network (30% of mb_map in use) # 0 requests for memory denied # 0 requests for memory delayed # 0 calls to protocol drain routines # last pid: 44768; load averages: 0.47, 0.38, 0.35 up 0+10:24:07 00:50:00 # 175 processes: 1 running, 163 sleeping, 11 zombie # Mem: 22M Active, 35M Inact, 42M Wired, 6516K Cache, 35M Buf, 144M Free # Swap: 500M Total, 6220K Used, 494M Free, 1% Inuse -- Dmitry Samersoff, dms@wplus.net, ICQ:3161705 http://devnull.wplus.net * There will come soft rains ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 5:30:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 4D1C437B744 for ; Thu, 22 Mar 2001 05:30:20 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 22 Mar 2001 13:30:19 +0000 (GMT) Date: Thu, 22 Mar 2001 13:30:19 +0000 From: David Malone To: Dmitry Samersoff Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Help please (Server crash) Message-ID: <20010322133019.A93965@walton.maths.tcd.ie> References: <3AB9F10A.714B2433@wplus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3AB9F10A.714B2433@wplus.net>; from dms@wplus.net on Thu, Mar 22, 2001 at 03:33:14PM +0300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 22, 2001 at 03:33:14PM +0300, Dmitry Samersoff wrote: > Any ideas? With hangs like this using the debugger to find out what the kernel is doing is often the best bet. You'll need to compile the debugger into the kernel and then leave the server on a vty that doesn't have X running. When it hangs try breakin into the debugger (ctl-alt-esc) and get a trace (type trace). You may need to do this a few times to get an idea of what's going on. The kernel debugging section of the handbook has more details on this sort of thing. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 6: 9:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from germes.levi.spb.ru (ip65.levi.spb.ru [212.119.175.65]) by hub.freebsd.org (Postfix) with ESMTP id 843AF37B718 for ; Thu, 22 Mar 2001 06:09:30 -0800 (PST) (envelope-from dms@wplus.net) Received: from wplus.net (IDENT:dms@pike.levi.spb.ru [10.246.8.43]) by germes.levi.spb.ru (8.11.1/8.11.1) with ESMTP id f2ME9S726485 for ; Thu, 22 Mar 2001 17:09:29 +0300 Message-ID: <3ABA0798.B32079C2@wplus.net> Date: Thu, 22 Mar 2001 17:09:28 +0300 From: Dmitry Samersoff Organization: LeviSoft X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.18 i686) X-Accept-Language: ru, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Attemt to compile with INVARIANTS failed Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG root@ds101:DS101#make linking kernel.debug vm_zone.o: In function `zalloci': /sys/compile/DS101/../../vm/vm_zone.h:81: undefined reference to `zerror' /sys/compile/DS101/../../vm/vm_zone.h:91: undefined reference to `zerror' vm_zone.o: In function `zfreei': /sys/compile/DS101/../../vm/vm_zone.h:106: undefined reference to `zerror' vm_zone.o: In function `_zget': /sys/compile/DS101/../../vm/vm_zone.c:380: undefined reference to `zerror' *** Error code 1 -- Dmitry Samersoff, dms@wplus.net, ICQ:3161705 http://devnull.wplus.net * There will come soft rains ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 7:59:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.orem.verio.net (gatekeeper.orem.verio.net [192.41.0.8]) by hub.freebsd.org (Postfix) with ESMTP id 273CD37B71B for ; Thu, 22 Mar 2001 07:59:50 -0800 (PST) (envelope-from fclift@verio.net) Received: from mx.dmz.orem.verio.net (mx.dmz.orem.verio.net [10.1.1.10]) by gatekeeper.orem.verio.net (Postfix) with ESMTP id 494C33BF127 for ; Thu, 22 Mar 2001 08:59:49 -0700 (MST) Received: from vespa.dmz.orem.verio.net (vespa.dmz.orem.verio.net [10.1.1.59]) by mx.dmz.orem.verio.net (8.11.1/8.11.1) with ESMTP id f2MFxjn46739; Thu, 22 Mar 2001 08:59:46 -0700 (MST) (envelope-from fclift@verio.net) Date: Thu, 22 Mar 2001 09:28:07 -0700 (MST) From: Fred Clift X-Sender: fred@vespa.dmz.orem.verio.net To: Thierry Herbelot Cc: Paul Saab , freebsd-hackers@FreeBSD.ORG Subject: Re: Remote boot, but not diskless operation In-Reply-To: <3AB31FB7.FF6AD0F7@herbelot.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > they've done this, but their newest BIOS (8 days old) still has a 0.78 > PXE revision (I've seen more recent DELL machines with a 0.99 - I assume > this is better) I have many intel MBs with built-in fxp nics that have 0.78 that work with 4.2's pxeboot just fine - I'm not trying to boot kernel remotely for local filesystesm, but I can't see why it wouldn't work. Off hand I'd guess that you have to put the right options in your dhcp server to tell it to find a 'local' root disk. Good luck. Fred -- Fred Clift - fclift@verio.net -- Remember: If brute force doesn't work, you're just not using enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 8:19:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postfix.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id EED6137B71F for ; Thu, 22 Mar 2001 08:19:45 -0800 (PST) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by postfix.conectiva.com.br (Postfix) with SMTP id 5952116EEE for ; Thu, 22 Mar 2001 13:19:42 -0300 (EST) Received: (qmail 21491 invoked by uid 0); 22 Mar 2001 16:19:04 -0000 Received: from dial11.ras.conectiva (HELO imladris.rielhome.conectiva) (root@10.0.8.11) by burns.conectiva with SMTP; 22 Mar 2001 16:19:04 -0000 Received: from localhost (IDENT:riel@localhost [127.0.0.1]) by imladris.rielhome.conectiva (8.11.2/8.11.2) with ESMTP id f2MEx9h24575; Thu, 22 Mar 2001 11:59:09 -0300 Date: Thu, 22 Mar 2001 11:59:09 -0300 (BRST) From: Rik van Riel X-Sender: riel@imladris.rielhome.conectiva To: thinker Cc: hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver In-Reply-To: <20010322191057.A46607@hell.branda.to> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Mar 2001, thinker wrote: > On Wed, Mar 21, 2001 at 04:14:32PM -0300, Rik van Riel wrote: > > The (maybe too lightweight) structure I have in my patch > > looks like this: > > > > struct pte_chain { > > struct pte_chain * next; > > pte_t * ptep; > > }; > > > > Each pte_chain hangs off a page of physical memory and the > > ptep is a pointer to a page table entry. > > > > The page struct of the page table page itself is used to > > note down which address space and offset we have. This means > > that FreeBSD's pv_pmap, pv_va and pv_ptem are in the page > > table page and NOT in each pte_chain structure... > > How about portability? It maybe efficient, but it is not easy > to port to other platforms. IIRC the pmap layer is in the architecture-dependent code in the BSDs. For Linux we have forward pagetables in every architecture, whether it be in software or hardware. They turn out to be quite adequate as an alternative to vnodes ;) regards, Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com.br/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 8:31:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from news.lucky.net (news.lucky.net [193.193.193.102]) by hub.freebsd.org (Postfix) with ESMTP id A7E4537B71B for ; Thu, 22 Mar 2001 08:30:56 -0800 (PST) (envelope-from news@news.ntu-kpi.kiev.ua) Received: (from mail@localhost) by news.lucky.net (8.Who.Cares/8.Who.Cares) id SLW02852 for freebsd-hackers@freebsd.org; Thu, 22 Mar 2001 18:30:53 +0200 (envelope-from news@news.ntu-kpi.kiev.ua) From: "Andrey Simonenko" To: freebsd-hackers@freebsd.org Subject: question about BPF programming Date: Thu, 22 Mar 2001 18:15:50 +0300 Organization: NTUU "KPI" Message-ID: <99d8mo$2cbo$1@igloo.uran.net.ua> X-Trace: igloo.uran.net.ua 985277976 78200 10.18.54.109 (22 Mar 2001 16:19:36 GMT) X-Complaints-To: newsmaster@news.ntu-kpi.kiev.ua X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I read bpf(4) man page and have one question about BPF. Suppose I open one of free BPF devices /dev/bpf??. I can dup(2) descriptor of opened BPF device and get so called shared interface. Can I setup different filters on each descriptor for opened BPF device? If I can do it, how can I do the same with pcap(3) library? Thanks for answers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 9:38: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 207A937B71E for ; Thu, 22 Mar 2001 09:38:01 -0800 (PST) (envelope-from scanner@jurai.net) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id MAA62798 for ; Thu, 22 Mar 2001 12:37:59 -0500 (EST) Date: Thu, 22 Mar 2001 12:37:59 -0500 (EST) From: To: freebsd-hackers@freebsd.org Subject: Intel driver doc's Take 2. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just got off the phone with Linda Sanchez at our favorite company Intel. She is a Sr. "Marketing Engineer" (What is a marketing engineer?) for their LAN products. She is itnerested in helping us get the information we need to write drivers for their cards. But she also knows NDA's are not going away. She wants to meet us halfway in the short term. Somewhere between a datasheet and a programming manual, that we can get with no NDA. I know alot of you are totally fed up with Intel and at this point couldnt give two hoots about Intel or their cards. But she is willing to work with us to get us what we need. I told her it sounds like an all or nothing proposition that we NEED the programming manuals. Not datasheets, not fluffy reference drivers. But for the short term that is not going to happen. Sigh. She does want to try and help us like I said. She need's specific information that we need that we cant get unless we sign NDA's for the doc's so she can try and get them merged into a reference product somewhere between the datasheet (worthless) and the programming manual (NDA). I know this is not ideal or what bill, jonathon, or others want. They would rather Intel just get a friggin clue and stop being anal. And while in the long term this may change it isn't going to be soon. She is willing to compromise and try and get us doc's on the bits we need. Is anyone willing to try and work on a middle of the road to keep support current for Intel nic's? Or has everyone decided to just not waste the effort or time on Intel idiocy anymore? Either way is fine. It's not like we only support one brand of NIC's. I'm just making an offer, the only offer from Intel, to help work with OS developers. I completely understand everyone's attitude towards Intel and I think it's totally justified. And I am usually an all or nothing person. I don't do middle of the road. But thats the offer on the table. Try and get us what we need in manual in between the datasheet and the programming doc's. But it will be available without an NDA. This is the option we currently have. Any takers? If there are she want's me to collect specific item's that are needed. Like the recent PHY debacle. What item's do we need programming doc's on? Specific parts? Etc. In the long term maybe Intel will get a clue but I am not holding my breath. But this is a chance to try and get what we need under a non-NDA arrangement. So if anyone has any care whatsoever to make one last effort to support Intel hardware and wants to work on getting the information we need. Let me know. I *think* we can get her to piecemeal the info we need into a non NDA doc for us, piece by piece that is as good or better as the programming doc's. Anyway if there are any takers that want to work with me on getting the doc's required let me know. Otherwise i'm just like everyone else I dont have a 50 megaton nuclear device to beat Intel with to get them to do the right thing. And Intel support can be dropped. ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tomorrow?" BSD: "Are you guys coming or what?" ============================================================================= irc.openprojects.net #FreeBSD -Join the revolution! ICQ: 20016186 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 9:50:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from vieo.com (vieo.com [216.30.79.131]) by hub.freebsd.org (Postfix) with ESMTP id 5662D37B718 for ; Thu, 22 Mar 2001 09:50:25 -0800 (PST) (envelope-from johng@vieo.com) Received: (from johng@localhost) by vieo.com (8.11.2/8.11.2) id f2MHoOw20094; Thu, 22 Mar 2001 11:50:24 -0600 (CST) (envelope-from johng) Date: Thu, 22 Mar 2001 11:50:24 -0600 (CST) From: John Gregor Message-Id: <200103221750.f2MHoOw20094@vieo.com> To: freebsd-hackers@FreeBSD.ORG, scanner@jurai.net Subject: Re: Intel driver doc's Take 2. In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Random idea from the peanut gallery... Find someone who is NDA'd and knows both the programming manual and the needs of the device driver. Have that person compose a list of those bits of the manual most necessary for getting a working driver. This would be an explicit list of figures, diagrams, tables and text sections. I would assume that Intel legal would then go through the list and give a yea/nay for each item requested. For the contested items, perhaps a redacted/simplified version could be proposed instead, but hopefully the bulk of the request would accepted. Just my $0.02 -JohnG (neither NDA'd or working on the driver) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 10: 7:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id A7D5537B720 for ; Thu, 22 Mar 2001 10:07:56 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p59-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.124]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id DAA09782; Fri, 23 Mar 2001 03:07:42 +0900 (JST) Message-ID: <3ABA3EB1.B3DDE35B@newsguy.com> Date: Fri, 23 Mar 2001 03:04:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: scanner@jurai.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG scanner@jurai.net wrote: > > She need's specific information that we need that we cant get > unless we sign NDA's for the doc's so she can try and get them merged into > a reference product somewhere between the datasheet (worthless) and the > programming manual (NDA). I know this is not ideal or what bill, jonathon, > or others want. They would rather Intel just get a friggin clue and stop > being anal. And while in the long term this may change it isn't going to > be soon. She is willing to compromise and try and get us doc's on the bits > we need. Let me just pipe in a bit. Compromise seems just like the kind of thing marketing or legal would want to do. The problem is that _we_ cannot compromise because one cannot write a "half-way there" driver. It's a technical impossibility. Now, if Bill Paul, Jonathan Lemon or whoever can come up with a "compromise" that would work, fine. But otherwise, and I think otherwise is likely, please explain the above to this person. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net It's a rewarding life, but hey, somebody has to have all the fun, right? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 10:11:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 6E16A37B720 for ; Thu, 22 Mar 2001 10:11:25 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f2MI7K421522; Thu, 22 Mar 2001 12:07:20 -0600 (CST) (envelope-from jlemon) Date: Thu, 22 Mar 2001 12:07:20 -0600 (CST) From: Jonathan Lemon Message-Id: <200103221807.f2MI7K421522@prism.flugsvamp.com> To: scanner@jurai.net, hackers@freebsd.org Subject: Re: Intel driver doc's Take 2. X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: > She need's specific information that we need that we cant get >unless we sign NDA's for the doc's so she can try and get them merged into >a reference product somewhere between the datasheet (worthless) and the >programming manual (NDA). Well, I applaud your effort, but I can't really think of how this would work. The information in the programming manual is required to program the chip. It is already a fairly concise manual, and if you axe anything out of it, it would mean that feature wouldn't be supported. A programming manual generally looks something like the following (completely made up) example: control register: offset 0, length 2 words bit 31: MWI enable bit 29-30: duplex settings 00 = full duplex 01 = half duplex 1x = auto negotiate In order for duplex settings to take effect, the chip must first be be reset to idle state, then the link settings changed bit 28: receiver enable 0 = disable 1 = enable before enabling the receiver, the receive control register must be set up appropriately, as well as the receive ring base and length registers. .... Exactly what in the above (fictional) example is it possible to axe out and still come up with a functional driver? Descriptions of each bit and their position in the register? The rules/caveats associated with each bit? I hate to say it, but anything that gets axed out of the manual basically means that those features of the chip will not be used. I honestly don't think that the marketer you talked to really understands this; I can't for the life of me see how anything less than the programming manual will be sufficient. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 10:15:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 3D57937B71D for ; Thu, 22 Mar 2001 10:15:39 -0800 (PST) (envelope-from scanner@jurai.net) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id NAA63871; Thu, 22 Mar 2001 13:15:25 -0500 (EST) Date: Thu, 22 Mar 2001 13:15:24 -0500 (EST) From: To: "Daniel C. Sobral" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: <3ABA3EB1.B3DDE35B@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Mar 2001, Daniel C. Sobral wrote: > Let me just pipe in a bit. Compromise seems just like the kind of thing > marketing or legal would want to do. The problem is that _we_ cannot > compromise because one cannot write a "half-way there" driver. It's a > technical impossibility. I agree 100%. I don't think this will fly either. I am just making the effort to work with Intel to get what we need. It's not going to happen overnight. Period. They are not going to change their NDA policy. In the future maybe. Actually I will forward the email she sent me this last time after I got off the phone with her an hour ago. I mentioned the problems Jonathan had with the GigE card. That's why she refers to him. Anyway I will forward it in a sec to the list. > Now, if Bill Paul, Jonathan Lemon or whoever can come up with a > "compromise" that would work, fine. But otherwise, and I think otherwise > is likely, please explain the above to this person. Well I have a feeling if bill even reads this, which he will probably see Intel in the subject and delete it, or has a procmail filter for 'Intel' :-) he will probably just get more frustrated then he is. Jonathan, I dont know. He is probably as fed up as everyone else. ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tomorrow?" BSD: "Are you guys coming or what?" ============================================================================= irc.openprojects.net #FreeBSD -Join the revolution! ICQ: 20016186 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 10:15:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 3702F37B720 for ; Thu, 22 Mar 2001 10:15:49 -0800 (PST) (envelope-from babolo@links.ru) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id VAA07815; Thu, 22 Mar 2001 21:15:43 +0300 (MSK) Message-Id: <200103221815.VAA07815@aaz.links.ru> Subject: Re: Help please (Server crash) In-Reply-To: <3AB9F10A.714B2433@wplus.net> from "Dmitry Samersoff" at "Mar 22, 1 03:33:14 pm" To: dms@wplus.net (Dmitry Samersoff) Date: Thu, 22 Mar 2001 21:15:43 +0300 (MSK) Cc: freebsd-hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Samersoff writes: > I have server under FreeBSD 4.2 with apache fired simple C++ CGI for > each connection. > > Aproximately every 12H uptime server stop responding. > > Kernel answers to ping, establish TCP connection but unable to fork > process. > (no messages in /var/log/messages) Looks like you reach some of limits, may be maxproc for user httpd runs as. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 10:22: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 5238437B71F for ; Thu, 22 Mar 2001 10:21:58 -0800 (PST) (envelope-from scanner@jurai.net) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id NAA64074 for ; Thu, 22 Mar 2001 13:21:57 -0500 (EST) Date: Thu, 22 Mar 2001 13:21:57 -0500 (EST) From: To: freebsd-hackers@freebsd.org Subject: RE: information on Intel Fast Ethernet and Gigabit (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ---------- Forwarded message ---------- Hello Mr. Chris Watson Thanks for taking the time to discuss with me your concerns. Could you take the the time to forward me some sort of representative list of the types of information that FreeBSD developers require to do driver development? Would like to focus on the pieces not covered by data sheet and non-NDA type documentation that you are using today, as we discussed. I would like to review this list and see if there's something that we can do about this. Also could you forward me more specific info on the issues with the FreeBSD driver written by J. Lemon. I would like to see what I can do to help out with these issues too. In the meantime, if you have any questions, please do not hesitate to call me. Thanks Linda P. Sanchez Sr. Product Marketing Engineer Network Communications Group LAN Access Division To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 10:33:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 931A737B71C for ; Thu, 22 Mar 2001 10:33:32 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA15288; Thu, 22 Mar 2001 10:33:34 -0800 Date: Thu, 22 Mar 2001 10:33:29 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: scanner@jurai.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For what it's worth, I believe I'm still committed to work on the GigE driver. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 10:34:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8FAB937B718 for ; Thu, 22 Mar 2001 10:34:05 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA15301; Thu, 22 Mar 2001 10:34:07 -0800 Date: Thu, 22 Mar 2001 10:34:02 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: scanner@jurai.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG btw- *I* have no problem with an NDA as long as it includes a rider that says what we could release as open source. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 10:37:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 91D9537B71E for ; Thu, 22 Mar 2001 10:37:30 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f2MIXQR22409; Thu, 22 Mar 2001 12:33:26 -0600 (CST) (envelope-from jlemon) Date: Thu, 22 Mar 2001 12:33:26 -0600 (CST) From: Jonathan Lemon Message-Id: <200103221833.f2MIXQR22409@prism.flugsvamp.com> To: mjacob@feral.com, hackers@freebsd.org Subject: Re: Intel driver doc's Take 2. X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: > >btw- *I* have no problem with an NDA as long as it includes a rider that says >what we could release as open source. Hah, me neither. In fact, if you want to try out a binary of my Intel GigE driver, it is at http://www.flugsvamp.com/~jlemon/fbsd/drivers -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 10:37:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2DE1737B726 for ; Thu, 22 Mar 2001 10:37:54 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA15356; Thu, 22 Mar 2001 10:37:53 -0800 Date: Thu, 22 Mar 2001 10:37:49 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Daniel C. Sobral" Cc: scanner@jurai.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: <3ABA3EB1.B3DDE35B@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > scanner@jurai.net wrote: > > > > She need's specific information that we need that we cant get > > unless we sign NDA's for the doc's so she can try and get them merged into > > a reference product somewhere between the datasheet (worthless) and the > > programming manual (NDA). I know this is not ideal or what bill, jonathon, > > or others want. They would rather Intel just get a friggin clue and stop > > being anal. And while in the long term this may change it isn't going to > > be soon. She is willing to compromise and try and get us doc's on the bits > > we need. > > Let me just pipe in a bit. Compromise seems just like the kind of thing > marketing or legal would want to do. The problem is that _we_ cannot > compromise because one cannot write a "half-way there" driver. It's a > technical impossibility. No, no, no, no, no. You can write an open source driver that contains all the basic features one would want (i.e., Networking works). But advanced features in the manuals that a company considers valuable IP might not be open sourced (e.g., vlan tagging, teaming, crc offloading). Frankly, that's dumb, but as long as the basic reasonable support for a NIC is there I believe that meets a reasonable 'support' test. > > Now, if Bill Paul, Jonathan Lemon or whoever can come up with a > "compromise" that would work, fine. But otherwise, and I think otherwise > is likely, please explain the above to this person. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 10:40: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E15D537B719 for ; Thu, 22 Mar 2001 10:40:04 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA15366; Thu, 22 Mar 2001 10:40:03 -0800 Date: Thu, 22 Mar 2001 10:39:58 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jonathan Lemon Cc: scanner@jurai.net, hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: <200103221807.f2MI7K421522@prism.flugsvamp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I hate to say it, but anything that gets axed out of the manual basically > means that those features of the chip will not be used. I honestly don't > think that the marketer you talked to really understands this; I can't > for the life of me see how anything less than the programming manual > will be sufficient. You should be allowed the whole manual, but some list of what can be made visible should not be all that hard to do- certainly after you've looked over the manual and you work with Intel to figure what is and isn't releasable. I have a personal contact with a manager in the LAN group at Intel who I'm visiting this weekend. We'll see if he has some influence in this matter. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 10:45:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id B38B637B718 for ; Thu, 22 Mar 2001 10:45:50 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f2MIfgk22749; Thu, 22 Mar 2001 12:41:42 -0600 (CST) (envelope-from jlemon) Date: Thu, 22 Mar 2001 12:41:42 -0600 From: Jonathan Lemon To: Matthew Jacob Cc: Jonathan Lemon , scanner@jurai.net, hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. Message-ID: <20010322124142.V82645@prism.flugsvamp.com> References: <200103221807.f2MI7K421522@prism.flugsvamp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 22, 2001 at 10:39:58AM -0800, Matthew Jacob wrote: > > > > I hate to say it, but anything that gets axed out of the manual basically > > means that those features of the chip will not be used. I honestly don't > > think that the marketer you talked to really understands this; I can't > > for the life of me see how anything less than the programming manual > > will be sufficient. > > You should be allowed the whole manual, but some list of what can be made > visible should not be all that hard to do- certainly after you've looked over > the manual and you work with Intel to figure what is and isn't releasable. Sure. If intel would simply say: " we don't want the driver to support cisco ISL, checksum offloading, VLAN, or Wake On Lan features " I suppose I could work with that. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 11:51:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relayout1.micronpc.com (meihost.micronpc.com [209.19.139.2]) by hub.freebsd.org (Postfix) with ESMTP id 4879C37B718; Thu, 22 Mar 2001 11:51:20 -0800 (PST) (envelope-from mpsimerson@hostpro.com) Received: from mei00wssout01.micron.com (mei00wssout01.micronpc.com [172.30.41.216]) by relayout1.micronpc.com (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with SMTP id MAA03064; Thu, 22 Mar 2001 12:50:58 -0700 Received: from 172.30.41.146 by mei00wssout01.micron.com with ESMTP ( Tumbleweed MMS SMTP Relay(WSS) v4.5); Thu, 22 Mar 2001 12:50:59 -0700 X-Server-Uuid: 6b1d535a-5b27-11d3-bf09-00902786a6a3 Received: by imcout1.micronpc.com with Internet Mail Service ( 5.5.2650.21) id ; Thu, 22 Mar 2001 12:51:26 -0700 Message-ID: <8D18712B2604D411A6BB009027F6449801B4B542@0SEA01EXSRV1> From: "Matt Simerson" To: "'freebsd-hackers@freebsd.org'" Cc: "'David O'Brien'" Subject: RE: 4.3-BETA world crashing 4.2-RELEASE kernel ? Date: Thu, 22 Mar 2001 12:51:00 -0700 X-Mailer: Internet Mail Service (5.5.2650.21) MIME-Version: 1.0 X-WSS-ID: 16A4882946892-01-01 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: David O'Brien [mailto:obrien@freebsd.org] > Sent: Wednesday, March 21, 2001 8:41 PM > To: Matt Simerson > Cc: freebsd-hackers@freebsd.org > Subject: Re: 4.3-BETA world crashing 4.2-RELEASE kernel ? > > First let me say to anyone reading the email I am replying to: > > don't do this > > On Wed, Mar 21, 2001 at 12:58:04PM -0700, Matt Simerson wrote: > > # cd /usr/src > > # make buildkernel KERNEL= > > # cd /usr/src; make buildworld > > # make installworld > > # make installkernel > > # mergemaster > > # reboot > > The order or "make buildworld" and "make buildkernel" are 100% totally > BACKWARDS. Actually, they aren't backwards. You've gone and snipped the parts of my original message that show that the commands are being executed at the same time. If either fails (for one reason or another as may happen) then I'll be able to plainly see why the build failed and correct it or go about fixing it manually. > Lets explain why: There are times when the kernel source is changed to > use constructs of newer compiler/assembler/linker tools. Thus the kernel > will not build with an older set of tools. The what "make buildkernel" > does is use the tools (ie, those built from the most up to date sources) > that are built during "make buildworld" to compile a new kernel. Thus > "make buildworld" must PROCEED "make buildkernel". Maybe I'm understanding you incorrectly here but according to what you just said, a "make buildkernel" will fail unless you have a set of compiler/assembler/linker tools in /usr/obj that were built from the make buildworld process. This is inaccurate at best and I suspect it's just plain wrong. I can "rm -r /usr/obj/*", "cd /usr/src; make clean", and then "make buildkernel KERNEL=" and it will succeed and build a happy little fully functionaly kernel. I've done this hundreds of times with success. So, I guess I'm not understanding your logic here. Would you care to explain further why this doesn't work? > Second, the install order above is not the conservative, careful > approach. One should issue "make installkernel && reboot" after the > "make buildkernel" to ensure the new kernel works > sufficiently well. Maybe that's _YOUR_ method for installing but it's not necessarily the best one. Kernel's are not guaranteed to be backwards compatible and I've installed a shiny new kernel that worked just fine and allowed my machine to come up single user but because of some rude change in /etc/rc, ipfw, or any of a number of places the machine couldn't make it to multi-user and allow me to get back in (via the network). When most of your servers are in a data-center 50 miles away and the rest are thousands of miles away, you'd rather not spend the next two hours talking a NOC monkey through a 10 minute process (if you have console). I prefer to do everything possible to make sure the system is going to boot correctly the first time and let me regain access. Success at building and installing the kernel, world, AND running mergemaster gives me a reasonably good chance that when I issue the reboot, it'll come up nice and happy. Second, if I'm going through the bother of compiling a buildworld it's because I want the latest version of world on my system. If there are some problems with the new kernel, I'm not going to revert back to world.old. I'll fix whatever is screwed up with kernel and proceed. Last, but not least, is that I don't have a warm body near all of my servers. I often want to do the make buildworld & kernel, installworld & kernel, and mergemaster and NOT reboot. Then I'll pop an email off to a warm body nearby and, at his leisure, have him give it a CTRL-ALT-DEL on the console and watch it to make sure it comes back up. > If not, one can always fall back to ``kernel.old''. One can fall back to kernel.old regardless. Even if I happen to have world.new installed, kernel.old will still work. There may be issues but if there is, they are surely no worse than running kernel.new with world.old. So, which is worse, the cart without a horse or a horse without a cart? > Since there is no > ``world.old''; after one does the "make installworld" backup tapes are > the only way of taking the system back to its previous state. I don't know many people who do buildworlds just for fun. If I'm doing a buildworld it's because I want the newer world installed. If I'm doing it on a server, it's because I've tested it on a dev box and I know it works the way I want. At that point, I have no reason to fall back to the previous world. Matt > -- > -- David (obrien@FreeBSD.org) > GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 11:53:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E295637B719 for ; Thu, 22 Mar 2001 11:53:15 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2MJrCm09963; Thu, 22 Mar 2001 11:53:12 -0800 (PST) Date: Thu, 22 Mar 2001 11:53:12 -0800 From: Alfred Perlstein To: Terry Lambert Cc: hackers@FreeBSD.ORG Subject: Re: 4MB pages Message-ID: <20010322115312.Y9431@fw.wintelcom.net> References: <200103221946.MAA15517@usr06.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103221946.MAA15517@usr06.primenet.com>; from tlambert@primenet.com on Thu, Mar 22, 2001 at 07:46:30PM +0000 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Terry Lambert [010322 11:47] wrote: > I know that this is going to look like I should have posted it > on the "-arch-questions" list, but there isn't one, and it > involves future work (I think), so here goes... > > > Has anyone tried playing with 4MB pages for doing other things? > [snip] > As usual, I'm playing with 4.x, not 5.x, so feel free to tell > me that this has already been thought of, and therefore is not > an issue for -arch. I think -hackers is more appropriate. As far as using 4MB pages, it would be nice to be able to add it for: 1) shm segements 2) mlock'd regions. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Represent yourself, show up at BABUG http://www.babug.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 11:53:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D01C737B71A for ; Thu, 22 Mar 2001 11:53:33 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2MJrEG81982; Thu, 22 Mar 2001 11:53:14 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3ABA0798.B32079C2@wplus.net> Date: Thu, 22 Mar 2001 11:53:03 -0800 (PST) From: John Baldwin To: Dmitry Samersoff Subject: RE: Attemt to compile with INVARIANTS failed Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Mar-01 Dmitry Samersoff wrote: > > root@ds101:DS101#make > linking kernel.debug > vm_zone.o: In function `zalloci': > /sys/compile/DS101/../../vm/vm_zone.h:81: undefined reference to > `zerror' > /sys/compile/DS101/../../vm/vm_zone.h:91: undefined reference to > `zerror' > vm_zone.o: In function `zfreei': > /sys/compile/DS101/../../vm/vm_zone.h:106: undefined reference to > `zerror' > vm_zone.o: In function `_zget': > /sys/compile/DS101/../../vm/vm_zone.c:380: undefined reference to > `zerror' > *** Error code 1 INARIANTS requires INVARIANT_SUPPORT, there is a note to this effect in LINT. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 12:28:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 3F1A837B71C; Thu, 22 Mar 2001 12:28:53 -0800 (PST) (envelope-from keichii@peorth.iteration.net) Received: by peorth.iteration.net (Postfix, from userid 1001) id B902B59293; Thu, 22 Mar 2001 14:28:52 -0600 (CST) Date: Thu, 22 Mar 2001 14:28:52 -0600 From: "Michael C . Wu" To: fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver Message-ID: <20010322142852.A19619@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <200103211114.f2LBE0h57371@mobile.wemm.org> <20010321120620.A932@peorth.iteration.net> <200103211817.f2LIHR416007@earth.backplane.com> <20010321102836.N12319@fw.wintelcom.net> <200103211907.f2LJ7cp17933@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103211907.f2LJ7cp17933@earth.backplane.com>; from dillon@earth.backplane.com on Wed, Mar 21, 2001 at 11:07:38AM -0800 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just an update on the lovely loaded BBS server. We made our record-breaking number of users last night. After implementing the changes suggested, and kqueue'ifying the BBS daemon. We saw a dramatic increase in server power. Top number of users was 4704 users. Serving SSH, HTTP, SMTP, innd, BBSD with no delays. (Meanwhile, we had kernel profiling ON :) ) We had peak load averages of 100.0, read: no delay. I am certain that we could taken on 6000 users had we had that many users. (It died due to unrelated reason, not because of the load since the number of users had gone down to 4400.) iostat became a fraction of what it used to be before we set vfs.vmiodirenable=1. (Why is vfs.vmiodirenable=1 not enabled by default?) We used to die at about 4200 users with average loads of 200.0 even 300.0 For those still interested in kq'ed BBSD stats: http://zoo.ee.ntu.edu.tw/~keichii I'm ponder if this should have been posted to FreeBSD-Advocacy. :^) -- +-----------------------------------------------------------+ | keichii@iteration.net | keichii@freebsd.org | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +-----------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 12:34:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 002E437B71A; Thu, 22 Mar 2001 12:34:35 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f2MKYSp11302; Thu, 22 Mar 2001 12:34:28 -0800 (PST) Date: Thu, 22 Mar 2001 12:34:28 -0800 From: Alfred Perlstein To: "Michael C . Wu" Cc: fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver Message-ID: <20010322123428.D9431@fw.wintelcom.net> References: <200103211114.f2LBE0h57371@mobile.wemm.org> <20010321120620.A932@peorth.iteration.net> <200103211817.f2LIHR416007@earth.backplane.com> <20010321102836.N12319@fw.wintelcom.net> <200103211907.f2LJ7cp17933@earth.backplane.com> <20010322142852.A19619@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010322142852.A19619@peorth.iteration.net>; from keichii@iteration.net on Thu, Mar 22, 2001 at 02:28:52PM -0600 X-all-your-base: are belong to us. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Michael C . Wu [010322 12:29] wrote: > Just an update on the lovely loaded BBS server. > We made our record-breaking number of users last night. > > After implementing the changes suggested, and kqueue'ifying > the BBS daemon. We saw a dramatic increase in server power. > > Top number of users was 4704 users. Serving SSH, HTTP, SMTP, innd, BBSD > with no delays. (Meanwhile, we had kernel profiling ON :) ) > We had peak load averages of 100.0, read: no delay. I am certain > that we could taken on 6000 users had we had that many users. > (It died due to unrelated reason, not because of the load since the > number of users had gone down to 4400.) iostat became a fraction of what > it used to be before we set vfs.vmiodirenable=1. > > (Why is vfs.vmiodirenable=1 not enabled by default?) It's not a good thing for boxes with < 128megs of ram IMO. It wastes a bunch of ram. When I get a chance I'm going to look at having FreeBSD auto tune such things as maxusers and things like vfs.vmiodirenable for large installs. Actually, i'm tempted to change the defaults for large installs then leave the "optimizations" for small machines to the people who have small machines. :) > We used to die at about 4200 users with average loads of 200.0 even 300.0 > For those still interested in kq'ed BBSD stats: > http://zoo.ee.ntu.edu.tw/~keichii > > I'm ponder if this should have been posted to FreeBSD-Advocacy. :^) Why not write up an article about this BBS scene and get it posted to slashdot or daemonnews? It would really make good press: "FreeBSD community responds to BBS problem with spectacular results." or something. :) -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 12:40:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C4C2F37B742 for ; Thu, 22 Mar 2001 12:40:08 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f2MKbrs01583; Thu, 22 Mar 2001 12:37:54 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103222037.f2MKbrs01583@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: scanner@jurai.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-reply-to: Your message of "Thu, 22 Mar 2001 13:15:24 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Mar 2001 12:37:53 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 23 Mar 2001, Daniel C. Sobral wrote: > > > Let me just pipe in a bit. Compromise seems just like the kind of thing > > marketing or legal would want to do. The problem is that _we_ cannot > > compromise because one cannot write a "half-way there" driver. It's a > > technical impossibility. > > I agree 100%. I don't think this will fly either. I am just making the > effort to work with Intel to get what we need. It's not going to happen > overnight. Period. They are not going to change their NDA policy. In the > future maybe. Actually I will forward the email she sent me this last time > after I got off the phone with her an hour ago. I mentioned the problems > Jonathan had with the GigE card. That's why she refers to him. Anyway I > will forward it in a sec to the list. [Speaking here from some experience with this set of issues.] The compromise that you want to strike, and really the *only* compromise that is going to work, is that the *documents* will remain undisclosed, but information from the documents that is necessary to produce a functional, high-performance driver may be disclosed, but *only* through the source code of the driver. Thus one or a small group of people sign the NDA, and keep the documentation. The driver is then developed and maintained by this team, who also have the opportunity to interact with Intel's engineering people. The source code resulting from this effort is then released publically. Intel should probably retain the right to veto code that you might want to put in the driver if they feel that it risks disclosure they don't want, but you don't have to suggest this to them unless you feel you need it as a bargaining chip. This would put them in the same situation as they are already in with their source-available Linux driver; it should not present any more intellectual property risks than they already face, and as a bonus, it gets us a better-supported driver. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 12:55:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 0338F37B719; Thu, 22 Mar 2001 12:55:35 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2MKtCG84074; Thu, 22 Mar 2001 12:55:12 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <8D18712B2604D411A6BB009027F6449801B4B542@0SEA01EXSRV1> Date: Thu, 22 Mar 2001 12:55:02 -0800 (PST) From: John Baldwin To: Matt Simerson Subject: RE: 4.3-BETA world crashing 4.2-RELEASE kernel ? Cc: "David O'Brien" Cc: "David O'Brien" , "freebsd-hackers@freebsd.org" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Mar-01 Matt Simerson wrote: >> Lets explain why: There are times when the kernel source is changed to >> use constructs of newer compiler/assembler/linker tools. Thus the kernel >> will not build with an older set of tools. The what "make buildkernel" >> does is use the tools (ie, those built from the most up to date sources) >> that are built during "make buildworld" to compile a new kernel. Thus >> "make buildworld" must PROCEED "make buildkernel". > > Maybe I'm understanding you incorrectly here but according to what you just > said, a "make buildkernel" will fail unless you have a set of > compiler/assembler/linker tools in /usr/obj that were built from the make > buildworld process. This is inaccurate at best and I suspect it's just plain > wrong. I can "rm -r /usr/obj/*", "cd /usr/src; make clean", and then "make > buildkernel KERNEL=" and it will succeed and build a happy little > fully functionaly kernel. I've done this hundreds of times with success. > > So, I guess I'm not understanding your logic here. Would you care to explain > further why this doesn't work? Hmm, maybe because you've been lucky to have done it wrong? Case in point: for 4.1 release, we upgraded to a new set of binutils (assembler, linker, etc.). Because the old asssembler was so broken, the new assembler could not compile the old code that had hacks in it to work around the bugs in the old assembler. Thus, if you tried to build a kernel without building world with the new assembler, the compile would fail. Thus, one needs to do the buildworld first to ensure the tools to compile the kernel are up to date. Please go read the archives if you want more of the hairy details. The process David described (which is the one that is in src/UPDATING) is the one that is supported. Other methods may work some of the time, but they won't work all of the time, and if it breaks for you it is your fault for not following the rather clear instructions that have been provided. :) >> Second, the install order above is not the conservative, careful >> approach. One should issue "make installkernel && reboot" after the >> "make buildkernel" to ensure the new kernel works >> sufficiently well. > > Maybe that's _YOUR_ method for installing but it's not necessarily the best > one. Kernel's are not guaranteed to be backwards compatible and I've Breakges of this time or very rare, and only in -current that I can remember. In fact, the only bad ones I've seen are when struct ucred changes causing mountd to start doing stupid things, but that has been permamently fixed in -current. However, as other people have pointed out, it is much easier to boot kernel.old if your new kernel is hosed and use that stable kernel to fix either the new kernel or the new world as appropriate. Really, if you wish to blow your own foot off that is fine, but do be aware that a) you shouldn't tell others to blow their feet off, and b) if you blow your own feet off it's your fault. :) In fact, if you are careful, you will note that src/UPDATING recommends that you do the installworld and /etc update in single user mode, not multiuser, which would avoid the problems you have seen with new kernels and old worlds. >> If not, one can always fall back to ``kernel.old''. > > One can fall back to kernel.old regardless. Even if I happen to have > world.new installed, kernel.old will still work. There may be issues but if > there is, they are surely no worse than running kernel.new with world.old. > So, which is worse, the cart without a horse or a horse without a cart? > >> Since there is no >> ``world.old''; after one does the "make installworld" backup tapes are >> the only way of taking the system back to its previous state. > > I don't know many people who do buildworlds just for fun. If I'm doing a > buildworld it's because I want the newer world installed. If I'm doing it on > a server, it's because I've tested it on a dev box and I know it works the > way I want. At that point, I have no reason to fall back to the previous > world. You don't run -current much it seems. :) (Not that I blame you, it is not for production machines.) The procedure described is the most robust one that has been come up with thus far. It has the greatest chance of success, though it is also somewhat painful (installworld in single user for example). You can do it differently if you wish (I do), but realize that if you do, you are on your own. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 12:55:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id E511937B720 for ; Thu, 22 Mar 2001 12:55:43 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2MKtao45569; Thu, 22 Mar 2001 12:55:36 -0800 (PST) (envelope-from obrien) Date: Thu, 22 Mar 2001 12:55:36 -0800 From: "David O'Brien" To: Matt Simerson Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: 4.3-BETA world crashing 4.2-RELEASE kernel ? Message-ID: <20010322125536.B43860@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <8D18712B2604D411A6BB009027F6449801B4B542@0SEA01EXSRV1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8D18712B2604D411A6BB009027F6449801B4B542@0SEA01EXSRV1>; from mpsimerson@hostpro.com on Thu, Mar 22, 2001 at 12:51:00PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 22, 2001 at 12:51:00PM -0700, Matt Simerson wrote: > Actually, they aren't backwards. You've gone and snipped the parts of my > original message that show that the commands are being executed at the same > time. I read you message twice and came away with the same idea. You should write more clearly. > Maybe I'm understanding you incorrectly here but according to what you just > said, a "make buildkernel" will fail unless you have a set of > compiler/assembler/linker tools in /usr/obj that were built from the make > buildworld process. This is inaccurate at best and I suspect it's just plain > wrong. I can "rm -r /usr/obj/*", "cd /usr/src; make clean", and then "make > buildkernel KERNEL=" and it will succeed and build a happy little > fully functionaly kernel. I've done this hundreds of times with success. The ability to do a `make buildkernel' with an empty /usr/obj is a new feature. But back to your misunderstanding. What part about "if the kernel source is changed to use language features not supported by the existing installed tools, you cannot build a kernel with them" do you not understand?? You obviously was not active when 4.x upgraded Binutils from 2.9.1 to 2.10.0 and the many of the asm bits were changed at the same time to remove work arounds and bogusness done to satisfy Binutils 2.9.1. > > Second, the install order above is not the conservative, careful > > approach. One should issue "make installkernel && reboot" after the > > "make buildkernel" to ensure the new kernel works > > sufficiently well. > > Maybe that's _YOUR_ method for installing but it's not necessarily the best > one. Kernel's are not guaranteed to be backwards compatible and I've > installed a shiny new kernel that worked just fine and allowed my machine to > come up single user but because of some rude change in /etc/rc, ipfw, or any > of a number of places the machine couldn't make it to multi-user and allow > me to get back in (via the network). That you're doing this remotely is your problem. Ask any of the developers living on -CURRENT where often one wants to back out of a newly compiled world. The method I gave is the most sure and careful way. That you don't have consoles on your machines so you could do this properly doesn't mean what I posted isn't the safest and should be followed unless has special needs. > Success at building and installing the kernel, world, AND running > mergemaster gives me a reasonably good chance that when I issue the reboot, > it'll come up nice and happy. I'm happy for you. But you have major flaws in your method where problems can bite you hard. As I said, I want users to know and use the safest method. I've seen enough email from users that were all confused about the right steps -- often getting confused from posts such as yours where you [hopefully] understand the consequences of your method and can deal with them. Many do not want to or cannot. > Second, if I'm going through the bother of compiling a buildworld it's > because I want the latest version of world on my system. Want != ability. I want a latest version of 5-CURRENT on my laptop, but CardBus is broken right now, so I am living with a Dec world. Such is life. > If there are some problems with the new kernel, I'm not going to revert > back to world.old. I'll fix whatever is screwed up with kernel and > proceed. Oh! Want a job as a kernel hacker then? I'd like to have my CardBus working again (in current). Also my AHA-2930u2 on a K6-2 machine... -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 13:46:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ajax1.sovam.com (ajax1.sovam.com [194.67.1.172]) by hub.freebsd.org (Postfix) with ESMTP id 2230737B71C; Thu, 22 Mar 2001 13:46:06 -0800 (PST) (envelope-from avn@any.ru) Received: from ts9-a178.dial.sovam.com ([195.239.70.178]:1066 "EHLO ts9-a178.dial.sovam.com" ident: "avn" whoson: "-unregistered-" smtp-auth: TLS-CIPHER: TLS-PEER: ) by ajax1.sovam.com with ESMTP id ; Fri, 23 Mar 2001 00:45:46 +0300 Date: Fri, 23 Mar 2001 00:49:28 +0300 (MSK) From: "Alexey V. Neyman" X-X-Sender: To: "Michael C . Wu" Cc: , Subject: Re: tuning a VERY heavily (30.0) loaded s cerver In-Reply-To: <20010322142852.A19619@peorth.iteration.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello there! On Thu, 22 Mar 2001, Michael C . Wu wrote: >(Why is vfs.vmiodirenable=1 not enabled by default?) By the way, is there any all-in-one-place description of sysctl tuneables? Looking all the man pages and collecting notices about MIB variables seems rather tiresome and, I think, pointless. I doubt if they are all documented in man pages. # Alexey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 16:14:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 3BF7E37B71A; Thu, 22 Mar 2001 16:14:28 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2N0EBC61507; Thu, 22 Mar 2001 16:14:11 -0800 (PST) (envelope-from dillon) Date: Thu, 22 Mar 2001 16:14:11 -0800 (PST) From: Matt Dillon Message-Id: <200103230014.f2N0EBC61507@earth.backplane.com> To: "Michael C . Wu" Cc: fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver References: <200103211114.f2LBE0h57371@mobile.wemm.org> <20010321120620.A932@peorth.iteration.net> <200103211817.f2LIHR416007@earth.backplane.com> <20010321102836.N12319@fw.wintelcom.net> <200103211907.f2LJ7cp17933@earth.backplane.com> <20010322142852.A19619@peorth.iteration.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :(Why is vfs.vmiodirenable=1 not enabled by default?) : The only reason it isn't enabled by default is some unresolved filesystem corruption that occurs very rarely (with or without it) that Kirk and I are still trying to nail down. I want to get that figured out first. It is true that some people have brought up memory use issues, but I don't consider memory use to really be that much of an issue. This is a cache, after all, so the blocks can be reused at just about any time. And directory blocks do not get cached well at all with vmiodirenable turned off. So the net result should be an increase in performance even on low-memory boxes. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 17: 1:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relayout1.micronpc.com (meihost.micronpc.com [209.19.139.2]) by hub.freebsd.org (Postfix) with ESMTP id 0E0DC37B71F for ; Thu, 22 Mar 2001 17:01:37 -0800 (PST) (envelope-from mpsimerson@hostpro.com) Received: from mei00wssout01.micron.com (mei00wssout01.micronpc.com [172.30.41.216]) by relayout1.micronpc.com (2.5 Build 2640 (Berkeley 8.8.6)/8.8.4) with SMTP id SAA05283 for ; Thu, 22 Mar 2001 18:01:14 -0700 Received: from 172.30.41.146 by mei00wssout01.micron.com with ESMTP ( Tumbleweed MMS SMTP Relay(WSS) v4.5); Thu, 22 Mar 2001 18:01:16 -0700 X-Server-Uuid: 6b1d535a-5b27-11d3-bf09-00902786a6a3 Received: by imcout1.micronpc.com with Internet Mail Service ( 5.5.2650.21) id ; Thu, 22 Mar 2001 18:01:42 -0700 Message-ID: <8D18712B2604D411A6BB009027F6449801B4B544@0SEA01EXSRV1> From: "Matt Simerson" To: "'freebsd-hackers@freebsd.org'" Subject: The "right" way to build a new world WAS: 4.3-BETA world crashin g 4.2-RELEASE kernel ? Date: Thu, 22 Mar 2001 18:01:16 -0700 X-Mailer: Internet Mail Service (5.5.2650.21) MIME-Version: 1.0 X-WSS-ID: 16A47FD682592-01-01 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, let's approach this from a little different angle: Below is the appropriate entries from /usr/src/UPDATING on a FreeBSD 4-stable machine. As of 2/2/2001, the most correct and safest method for updating your FreeBSD machine is as follows: cd /usr/src make buildworld make kernel KERNCONF= reboot (single user) make installworld mergemaster reboot I have found that there IS a variety of reasons NOT to do it that way. The most obvious is that you might not have console access, thus making it pretty hard to access the machine while it's in single user mode. I can also think of a couple instances where this method could cause pain. The first is changing of any of the files used at boot time. I don't allow telnet access to any of my machines so SSH is often as close as I can get to console. If anything changes enough that we don't cleanly make it through rc and friends, processing stops, sshd won't be running and I can't get in. The one time this happened the machine didn't make it multi user. Fortunately that machine was in my basement so I walked down, looked at the errors on the console and finished the upgrade. IPFW changes. This one isn't quite obvious but if you don't compile your kernel with IPFW_DEFAULT_TO_ACCEPT and changes are made to the kernel or userland portions and not the other (as will happen in the above scenario) then upon reboot, if your ruleset doesn't get applied, you won't be able to access your machine via the network. Ouch. I always compile in the DEFAULT_TO_ACCEPT for this reason and then add a default deny rule to the IFPW ruleset. Even so, I find it's best to get my kernel, world, and config files synced before rebooting. Changes like that aren't terribly infrequent and if you aren't paying attention, can bite you. This (and a few other things) have prompted me to completely skip the first reboot. Also, I tend to keep everything I use in a location (/usr/local) other than the default places installworld wants to be touching. So, I can almost always get away with doing an installworld without changing my runlevel. The last thing, which is seldom mentioned but which I habitually do is another make installkernel after the system comes back up and is happy. The reason(s) should be obvious. So, my procedure looks a lot like this: cd /usr/src make buildworld make kernel KERNCONF= make installworld mergemaster reboot cd /usr/src make installkernel KERNEL= One can also often get away with making a new kernel without first building world but do so at your own peril (as I often do). :-) I often issue the buildkernel and buildworld at the same time and then leave for the day. My reasons for doing this are: laziness, impatience, and wanting to have the entire compilation done when I return. Doing so can be risky but in my experience, works just fine with the -stable tree. Others have been quick to point out the possible hazards of doing so but they mostly apply when playing with -current. Matt From /usr/src/UPDATING (on FreeBSD 4-STABLE): COMMON ITEMS: To build a kernel ----------------- cd /usr/src # If you have not already done so, please buildworld here # You will also need to update your config file to 4.x. Usually # people tend to start with GENERIC from 4.x and hack from there. make buildkernel KERNCONF= make installkernel KERNCONF= # Verify that the new kernel works, it will be installed as # /kernel To rebuild disk /dev entries ---------------------------- MAKEDEV should be copied from src/etc/MAKEDEV to /dev before starting the following: For N in the list of disks MAKEDEV N # eg ad0 for M in the list of slices MAKEDEV NsMa # eg ad0s1a To rebuild everything --------------------- make world Except when it doesn't work :-) To update from 4.0-RELEASE or later to the most current 4.x-STABLE ---------- make buildworld make buildkernel KERNCONF=YOUR_KERNEL_HERE make installkernel KERNCONF=YOUR_KERNEL_HERE reboot (in single user) [1] make installworld mergemaster reboot [1] You can often get away without doing this step as the system will be properly updated. During the running of the installworld, however, system components may break and other oddities may happen. Don't do this on systems that aren't otherwise quiet as unpredictable results may happen. If in doubt, reboot into single user. For remote installs, keep a separate kernel around and use a serial console if at all possible. > -----Original Message----- > From: David O'Brien [mailto:obrien@freebsd.org] > Sent: Thursday, March 22, 2001 12:56 PM > To: Matt Simerson > Cc: 'freebsd-hackers@freebsd.org' > Subject: Re: 4.3-BETA world crashing 4.2-RELEASE kernel ? > > > On Thu, Mar 22, 2001 at 12:51:00PM -0700, Matt Simerson wrote: > > Actually, they aren't backwards. You've gone and snipped > the parts of my > > original message that show that the commands are being > executed at the same > > time. > > I read you message twice and came away with the same idea. You should > write more clearly. I wrote the commands exactly as they would be issued, how much more clear can one possibly get? Because you lack familiarity with the tool I was using (screen) doesn't make my writing unclear. Your ignorance != my unclarity. To make matters worse, you snipped out all the parts you didn't understand and then reposted it with my name attached AND criticized it's behaviour which you had incorrectly interpreted. > > Maybe that's _YOUR_ method for installing but it's not necessarily the best > > one. Kernel's are not guaranteed to be backwards compatible and I've > > installed a shiny new kernel that worked just fine and allowed my machine to > > come up single user but because of some rude change in /etc/rc, ipfw, or any > > of a number of places the machine couldn't make it to multi-user and allow > > me to get back in (via the network). > > That you're doing this remotely is your problem. Ask any of the > developers living on -CURRENT where often one wants to back out of a > newly compiled world. I'm not running on -CURRENT and I certainly would never run -current on a machine that I didn't have ready access to the console of. I've tracked 5.0-current months ago when I needed a feature that wasn't in the 4-stable tree yet (dare I admit it was support for a sound card?). I find it to be highly annoying when I have to babysit the buildworld process and manually fix things to get a clean compile. > The method I gave is the most sure and careful > way. That you don't have consoles on your machines so you could do this > properly doesn't mean what I posted isn't the safest and should be > followed unless has special needs. > > I'm happy for you. But you have major flaws in your method where > problems can bite you hard. How so? If the buildkernel fails, odds are really good that it won't successfully finish the compile, I won't get a kernel, I can't install a kernel that isn't compiled, and there isn't a problem other than that I don't have the new kernel I wanted. I can address this problem very easily and it's not likely to cause any further pain. > As I said, I want users to know and use the > safest method. I've seen enough email from users that were all confused > about the right steps -- often getting confused from posts such as yours > where you [hopefully] understand the consequences of your method and can > deal with them. Many do not want to or cannot. OK then, the safest (and recommended) way to build 4-STABLE world is: make buildworld make kernel reboot (into single user) make installworld mergemaster reboot Many sysadmins will find this doesn't work in their environment (for a variety of reasons). The most obvious is that they need some custom features in their kernel. So, make a copy of GENERIC in /sys/i386/conf/, edit it accordingly (adding support for your sound card, x10 controller, IPFW, GB ether card, quotas, and whatever else). The procedure will likely work exactly that same: make buildworld make kernel KERNCONF= (1) reboot make installworld mergemaster reboot 1. /usr/src/UPDATING > > Second, if I'm going through the bother of compiling a buildworld it's > > because I want the latest version of world on my system. > > Want != ability. I want a latest version of 5-CURRENT on my laptop, but > CardBus is broken right now, so I am living with a Dec world. Such is > life. Such is life on -current. I think this is the majority of our desparity. You live in a -current world where you're content to live with hacking and tweaking source as a "normal" part of the buildworld process. It's nice that you have console on all your boxes. I live in -stable where I can't remember the last time a make buildworld failed. In fact, it's been quite some time since building a kernel the new way "make buildkernel" failed and I think that was on a 4.1.1-release machine that I was upgrading to 4.3-stable. It required building via ./config KERNEL; cd ../../compile/KERNEL/; etc.... In my world where uptime matters, I don't normally have the luxury of installing world in single user mode either. I have a Portmaster at home so I can access console on my own machines but my "console" for all the machines that live in our datacenters is a portable KVM and a NOC monkey. Ouch. :-( > > If there are some problems with the new kernel, I'm not going to revert > > back to world.old. I'll fix whatever is screwed up with kernel and > > proceed. > > Oh! Want a job as a kernel hacker then? No thanks, that's why I'm back to tracking -stable. My dozens of FreeBSD machines have jobs to do and building world every week trying to get a version with only tolerable bugs isn't a very productive use of time. > I'd like to have my CardBus working again (in current). > Also my AHA-2930u2 on a K6-2 machine... I'm sure you would but I have other things to spend time on. Tracking -current on FreeBSD is just like tracking the latest releases of IOS on Cisco. You know it's full of undocumented features for you to test and report to the engineers. The only difference is that most of the bugs don't make it into the -stable releases of FreeBSD where they do in IOS. In older IOS though, all the bugs^H^H^H^Hundocumented features are well documented. :-P Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 17:23:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id B84FF37B71D for ; Thu, 22 Mar 2001 17:23:30 -0800 (PST) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-135-105.nnj.dialup.bellatlantic.net [151.198.135.105]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id UAA04305; Thu, 22 Mar 2001 20:23:17 -0500 (EST) Message-ID: <3ABAA57B.1E3BAF05@bellatlantic.net> Date: Thu, 22 Mar 2001 20:23:07 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: Jonathan Lemon Cc: scanner@jurai.net, hackers@freebsd.org Subject: Re: Intel driver doc's Take 2. References: <200103221807.f2MI7K421522@prism.flugsvamp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan Lemon wrote: > > In article you write: > > She need's specific information that we need that we cant get > >unless we sign NDA's for the doc's so she can try and get them merged into > >a reference product somewhere between the datasheet (worthless) and the > >programming manual (NDA). > > Well, I applaud your effort, but I can't really think of how this > would work. The information in the programming manual is required > to program the chip. It is already a fairly concise manual, and if > you axe anything out of it, it would mean that feature wouldn't be > supported. How about meeting half-way in a different way ? Suppose they provide the manual with NDA but in the NDA agreement they state that the source code of the driver developed using this manual may be published. To reiterate, the manual itself would still be their trade secret but the results of development done based on this manual would be free. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 17:36:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 09B4A37B720 for ; Thu, 22 Mar 2001 17:36:48 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2N1aMG93085; Thu, 22 Mar 2001 17:36:22 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <8D18712B2604D411A6BB009027F6449801B4B544@0SEA01EXSRV1> Date: Thu, 22 Mar 2001 17:36:15 -0800 (PST) From: John Baldwin To: Matt Simerson Subject: RE: The "right" way to build a new world WAS: 4.3-BETA world cra Cc: "freebsd-hackers@freebsd.org" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Mar-01 Matt Simerson wrote: > OK, let's approach this from a little different angle: > > Below is the appropriate entries from /usr/src/UPDATING on a FreeBSD > 4-stable machine. As of 2/2/2001, the most correct and safest method for > updating your FreeBSD machine is as follows: > > cd /usr/src > make buildworld > make kernel KERNCONF= > reboot (single user) > make installworld > mergemaster > reboot > > I have found that there IS a variety of reasons NOT to do it that way. The > most obvious is that you might not have console access, thus making it > pretty hard to access the machine while it's in single user mode. I can also > think of a couple instances where this method could cause pain. All of the ones you list below are not a problem if one has a serial console (single user implies console access). :) It _is_ the safest and most correct way, but it's not always convenient and/or feasible. And while you can deviate from it, you should only do so once you are comfortable with the process and know how to get yourself out of a jam if it blows up in your face. New users don't have all this background yet, so following the directions above is the best thing for them to do. Make sense? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Mar 22 19:24:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D440637B71E for ; Thu, 22 Mar 2001 19:24:49 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.1/8.11.1) with ESMTP id f2N3OnV70003 for ; Thu, 22 Mar 2001 19:24:49 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f2N3Omv29568; Thu, 22 Mar 2001 19:24:48 -0800 (PST) (envelope-from jdp) Date: Thu, 22 Mar 2001 19:24:48 -0800 (PST) Message-Id: <200103230324.f2N3Omv29568@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Reply-To: hackers@freebsd.org Subject: Re: SCSI-over-* hacks In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Max Khon wrote: > hi, there! > > On Tue, 20 Mar 2001, Mike Smith wrote: > > > > Has anyone implemented/thought of implementing: > > > - a CAM transport for ATAPI devices; > > > > Yes. It's not a lot of work. > > that would be GREAT for cd recording on IDE CD-RW (one will be able to > use cdrdao and cdrecord instead of burncd) Yes! It would definitely be nice if cdrecord worked with ATAPI CD-RW drives on FreeBSD. John, who just bought an ATAPI CD-RW drive -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 0:21:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ncmail.netcentralen.dk (ncmail.netcentralen.dk [195.24.7.103]) by hub.freebsd.org (Postfix) with ESMTP id 9ECDF37B719 for ; Fri, 23 Mar 2001 00:21:24 -0800 (PST) (envelope-from mar@netcentralen.dk) Received: from mother.netcentralen.dk (mother.netcentralen.dk [195.24.7.107]) by ncmail.netcentralen.dk (8.9.3/8.9.3) with ESMTP id JAA14933 for ; Fri, 23 Mar 2001 09:22:45 +0100 (CET) (envelope-from mar@netcentralen.dk) Received: by mother.netcentralen.dk with Internet Mail Service (5.5.2650.21) id ; Fri, 23 Mar 2001 09:28:29 +0100 Message-ID: <9164771DDCABD3118333005004E9446E43265B@mother.netcentralen.dk> From: Michael Aronsen To: "'hackers@freebsd.org'" Subject: Fingerprint authentication? Date: Fri, 23 Mar 2001 09:28:20 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Dont quite know where to throw this question but i thought maybe hackers@freebsd.org might be the right place. Has anyone been working on or know of any work being done on getting any fingerprint gadgets working in FreeBSD? Michael Aronsen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 0:33:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bom2.vsnl.net.in (bom2.vsnl.net.in [202.54.1.1]) by hub.freebsd.org (Postfix) with ESMTP id D7F5A37B71E for ; Fri, 23 Mar 2001 00:33:33 -0800 (PST) (envelope-from toner1@asianwired.net) Received: from 202.54.1.1 (rsvp-208-187-151-175.ac05.dlls.eli.net [208.187.151.175]) by bom2.vsnl.net.in (Postfix) with SMTP id 210885297; Fri, 23 Mar 2001 14:03:20 +0530 (GMT+5:30) To: customer@republic.com Date: Thu, 22 Mar 01 03:22:20 EST From: toner1@asianwired.net Subject: toner supplies Message-Id: <20010323083320.210885297@bom2.vsnl.net.in> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG PLEASE FORWARD TO THE PERSON RESPONSIBLE FOR PURCHASING YOUR LASER PRINTER SUPPLIES **** VORTEX SUPPLIES **** -SPECIALS OF THE DAY ON LASER TONER SUPPLIES AT DISCOUNT PRICES-- LASER PRINTER TONER CARTRIDGES COPIER AND FAX CARTRIDGES WE ARE -->THE<-- PLACE TO BUY YOUR TONER CARTRIDGES BECAUSE YOU SAVE UP TO 30% FROM OFFICE DEPOT'S, QUILL'S OR OFFICE MAX'S EVERY DAY LOW PRICES ORDER BY PHONE:1-888-288-9043 ORDER BY FAX: 1-888-977-1577 CUSTOMER SERVICE: 1-888-248-2015 E-MAIL REMOVAL LINE: 1-888-248-4930 UNIVERSITY AND/OR SCHOOL PURCHASE ORDERS WELCOME. (NO CREDIT APPROVAL REQUIRED) ALL OTHER PURCHASE ORDER REQUESTS REQUIRE CREDIT APPROVAL. PAY BY CHECK (C.O.D), CREDIT CARD OR PURCHASE ORDER (NET 30 DAYS). IF YOUR ORDER IS BY CREDIT CARD PLEASE LEAVE YOUR CREDIT CARD # PLUS EXPIRATION DATE. IF YOUR ORDER IS BY PURCHASE ORDER LEAVE YOUR SHIPPING/BILLING ADDRESSES AND YOUR P.O. NUMBER NO SHIPPING CHARGES FOR ORDERS $49 OR OVER ADD $4.75 FOR ORDERS UNDER $49. C.O.D. ORDERS ADD $4.5 TO SHIPPING CHARGES. FOR THOSE OF YOU WHO REQUIRE MORE INFORMATION ABOUT OUR COMPANY INCUDING FEDERAL TAX ID NUMBER, CLOSEST SHIPPING OR CORPORATE ADDRESS IN THE CONTINENTAL U.S. OR FOR CATALOG REQUESTS PLEASE CALL OUR CUSTOMER SERVICE LINE 1-888-248-2015 OUR NEW , LASER PRINTER TONER CARTRIDGE, PRICES ARE AS FOLLOWS: (PLEASE ORDER BY PAGE NUMBER AND/OR ITEM NUMBER) HEWLETT PACKARD: (ON PAGE 2) ITEM #1 LASERJET SERIES 4L,4P (74A)------------------------$44 ITEM #2 LASERJET SERIES 1100 (92A)-------------------------$44 ITEM #3 LASERJET SERIES 2 (95A)-------------------------------$39 ITEM #4 LASERJET SERIES 2P (75A)-----------------------------$54 ITEM #5 LASERJET SERIES 5P,6P,5MP, 6MP (3903A)--$44 ITEM #6 LASERJET SERIES 5SI, 5000 (29A)------------------$95 ITEM #7 LASERJET SERIES 2100 (96A)-------------------------$74 ITEM #8 LASERJET SERIES 8100 (82X)-----------------------$145 ITEM #9 LASERJET SERIES 5L/6L (3906A0------------------$35 ITEM #10 LASERJET SERIES 4V-------------------------------------$95 ITEM #11 LASERJET SERIES 4000 (27X)-------------------------$72 ITEM #12 LASERJET SERIES 3SI/4SI (91A)--------------------$54 ITEM #13 LASERJET SERIES 4, 4M, 5,5M-----------------------$49 HEWLETT PACKARD FAX (ON PAGE 2) ITEM #14 LASERFAX 500, 700 (FX1)----------$49 ITEM #15 LASERFAX 5000,7000 (FX2)------$54 ITEM #16 LASERFAX (FX3)------------------------$59 ITEM #17 LASERFAX (FX4)------------------------$54 LEXMARK/IBM (ON PAGE 3) OPTRA 4019, 4029 HIGH YIELD---------------$89 OPTRA R, 4039, 4049 HIGH YIELD---------$105 OPTRA E----------------------------------------------------$59 OPTRA N--------------------------------------------------$115 OPTRA S--------------------------------------------------$165 - EPSON (ON PAGE 4) ACTION LASER 7000,7500,8000,9000-------$105 ACTION LASER 1000,1500-------------------------$105 CANON PRINTERS (ON PAGE 5) PLEASE CALL FOR MODELS AND UPDATED PRICES FOR CANON PRINTER CARTRIDGES PANASONIC (0N PAGE 7) NEC SERIES 2 MODELS 90 AND 95----------$105 APPLE (0N PAGE 8) LASER WRITER PRO 600 or 16/600------------$49 LASER WRITER SELECT 300,320,360---------$74 LASER WRITER 300 AND 320----------------------$54 LASER WRITER NT, 2NT------------------------------$54 LASER WRITER 12/640--------------------------------$79 CANON FAX (ON PAGE 9) LASERCLASS 4000 (FX3)---------------------------$59 LASERCLASS 5000,6000,7000 (FX2)---------$54 LASERFAX 5000,7000 (FX2)----------------------$54 LASERFAX 8500,9000 (FX4)----------------------$54 CANON COPIERS (PAGE 10) PC 3, 6RE, 7 AND 11 (A30)---------------------$69 PC 300,320,700,720 and 760 (E-40)--------$89 IF YOUR CARTRIDGE IS NOT LISTED CALL CUSTOMER SERVICE AT 1-888-248-2015 90 DAY UNLIMITED WARRANTY INCLUDED ON ALL PRODUCTS. ALL TRADEMARKS AND BRAND NAMES LISTED ABOVE ARE PROPERTY OF THE RESPECTIVE HOLDERS AND USED FOR DESCRIPTIVE PURPOSES ONLY. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 0:53:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bom2.vsnl.net.in (bom2.vsnl.net.in [202.54.1.1]) by hub.freebsd.org (Postfix) with ESMTP id AEA5737B720; Fri, 23 Mar 2001 00:52:40 -0800 (PST) (envelope-from toner1@asianwired.net) Received: from 202.54.1.1 (rsvp-208-187-151-175.ac05.dlls.eli.net [208.187.151.175]) by bom2.vsnl.net.in (Postfix) with SMTP id 9B0C32B28B; Fri, 23 Mar 2001 14:20:28 +0530 (GMT+5:30) To: customer@republic.com Date: Thu, 22 Mar 01 03:22:20 EST From: toner1@asianwired.net Subject: toner supplies Message-Id: <20010323085039.9B0C32B28B@bom2.vsnl.net.in> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG PLEASE FORWARD TO THE PERSON RESPONSIBLE FOR PURCHASING YOUR LASER PRINTER SUPPLIES **** VORTEX SUPPLIES **** -SPECIALS OF THE DAY ON LASER TONER SUPPLIES AT DISCOUNT PRICES-- LASER PRINTER TONER CARTRIDGES COPIER AND FAX CARTRIDGES WE ARE -->THE<-- PLACE TO BUY YOUR TONER CARTRIDGES BECAUSE YOU SAVE UP TO 30% FROM OFFICE DEPOT'S, QUILL'S OR OFFICE MAX'S EVERY DAY LOW PRICES ORDER BY PHONE:1-888-288-9043 ORDER BY FAX: 1-888-977-1577 CUSTOMER SERVICE: 1-888-248-2015 E-MAIL REMOVAL LINE: 1-888-248-4930 UNIVERSITY AND/OR SCHOOL PURCHASE ORDERS WELCOME. (NO CREDIT APPROVAL REQUIRED) ALL OTHER PURCHASE ORDER REQUESTS REQUIRE CREDIT APPROVAL. PAY BY CHECK (C.O.D), CREDIT CARD OR PURCHASE ORDER (NET 30 DAYS). IF YOUR ORDER IS BY CREDIT CARD PLEASE LEAVE YOUR CREDIT CARD # PLUS EXPIRATION DATE. IF YOUR ORDER IS BY PURCHASE ORDER LEAVE YOUR SHIPPING/BILLING ADDRESSES AND YOUR P.O. NUMBER NO SHIPPING CHARGES FOR ORDERS $49 OR OVER ADD $4.75 FOR ORDERS UNDER $49. C.O.D. ORDERS ADD $4.5 TO SHIPPING CHARGES. FOR THOSE OF YOU WHO REQUIRE MORE INFORMATION ABOUT OUR COMPANY INCUDING FEDERAL TAX ID NUMBER, CLOSEST SHIPPING OR CORPORATE ADDRESS IN THE CONTINENTAL U.S. OR FOR CATALOG REQUESTS PLEASE CALL OUR CUSTOMER SERVICE LINE 1-888-248-2015 OUR NEW , LASER PRINTER TONER CARTRIDGE, PRICES ARE AS FOLLOWS: (PLEASE ORDER BY PAGE NUMBER AND/OR ITEM NUMBER) HEWLETT PACKARD: (ON PAGE 2) ITEM #1 LASERJET SERIES 4L,4P (74A)------------------------$44 ITEM #2 LASERJET SERIES 1100 (92A)-------------------------$44 ITEM #3 LASERJET SERIES 2 (95A)-------------------------------$39 ITEM #4 LASERJET SERIES 2P (75A)-----------------------------$54 ITEM #5 LASERJET SERIES 5P,6P,5MP, 6MP (3903A)--$44 ITEM #6 LASERJET SERIES 5SI, 5000 (29A)------------------$95 ITEM #7 LASERJET SERIES 2100 (96A)-------------------------$74 ITEM #8 LASERJET SERIES 8100 (82X)-----------------------$145 ITEM #9 LASERJET SERIES 5L/6L (3906A0------------------$35 ITEM #10 LASERJET SERIES 4V-------------------------------------$95 ITEM #11 LASERJET SERIES 4000 (27X)-------------------------$72 ITEM #12 LASERJET SERIES 3SI/4SI (91A)--------------------$54 ITEM #13 LASERJET SERIES 4, 4M, 5,5M-----------------------$49 HEWLETT PACKARD FAX (ON PAGE 2) ITEM #14 LASERFAX 500, 700 (FX1)----------$49 ITEM #15 LASERFAX 5000,7000 (FX2)------$54 ITEM #16 LASERFAX (FX3)------------------------$59 ITEM #17 LASERFAX (FX4)------------------------$54 LEXMARK/IBM (ON PAGE 3) OPTRA 4019, 4029 HIGH YIELD---------------$89 OPTRA R, 4039, 4049 HIGH YIELD---------$105 OPTRA E----------------------------------------------------$59 OPTRA N--------------------------------------------------$115 OPTRA S--------------------------------------------------$165 - EPSON (ON PAGE 4) ACTION LASER 7000,7500,8000,9000-------$105 ACTION LASER 1000,1500-------------------------$105 CANON PRINTERS (ON PAGE 5) PLEASE CALL FOR MODELS AND UPDATED PRICES FOR CANON PRINTER CARTRIDGES PANASONIC (0N PAGE 7) NEC SERIES 2 MODELS 90 AND 95----------$105 APPLE (0N PAGE 8) LASER WRITER PRO 600 or 16/600------------$49 LASER WRITER SELECT 300,320,360---------$74 LASER WRITER 300 AND 320----------------------$54 LASER WRITER NT, 2NT------------------------------$54 LASER WRITER 12/640--------------------------------$79 CANON FAX (ON PAGE 9) LASERCLASS 4000 (FX3)---------------------------$59 LASERCLASS 5000,6000,7000 (FX2)---------$54 LASERFAX 5000,7000 (FX2)----------------------$54 LASERFAX 8500,9000 (FX4)----------------------$54 CANON COPIERS (PAGE 10) PC 3, 6RE, 7 AND 11 (A30)---------------------$69 PC 300,320,700,720 and 760 (E-40)--------$89 IF YOUR CARTRIDGE IS NOT LISTED CALL CUSTOMER SERVICE AT 1-888-248-2015 90 DAY UNLIMITED WARRANTY INCLUDED ON ALL PRODUCTS. ALL TRADEMARKS AND BRAND NAMES LISTED ABOVE ARE PROPERTY OF THE RESPECTIVE HOLDERS AND USED FOR DESCRIPTIVE PURPOSES ONLY. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 2:22:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay1.kpn-telecom.nl (relay1.kpn-telecom.nl [145.7.200.6]) by hub.freebsd.org (Postfix) with ESMTP id 6D86637B719 for ; Fri, 23 Mar 2001 02:22:36 -0800 (PST) (envelope-from j.schripsema@kpn.com) Received: from hdiro010.kpn.com (hdiro010.kpn.com [145.7.200.10]) by relay1.kpn-telecom.nl (8.11.1/8.11.1) with SMTP id f2NAMXY01475 for ; Fri, 23 Mar 2001 11:22:34 +0100 Received: from 10.1.88.11 by hdiro010.kpn.com (InterScan E-Mail VirusWall NT); Fri, 23 Mar 2001 11:22:01 +0100 (Romance Standard Time) Received: from tmail001s.telecom.ptt.nl (tmail001s.pc.telecom.ptt.nl [145.7.210.58]) by sat-relay1.pc.telecom.ptt.nl (8.11.1/8.11.1) with ESMTP id f2NALxx10992 for ; Fri, 23 Mar 2001 11:21:59 +0100 Received: by tmail001s with Internet Mail Service (5.5.2448.0) id ; Fri, 23 Mar 2001 11:21:59 +0100 Message-ID: From: j.schripsema@kpn.com To: freebsd-hackers@freebsd.org Subject: NFS: "got bad cookie" error (again?) Date: Fri, 23 Mar 2001 11:21:55 +0100 Importance: high X-Priority: 1 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Running bonnie++ on a NFS mounted files system doesn't work. Bonnie exits with a fatal error caused by an attempt to remove a non-empty directory. Bonnie tries to remove all files in a directory by calling 'readdir' an 'unlink' in a loop. This works fine on a local filesystem (UFS) but not on a NFS mounted filesystem (also UFS on the server). I'm running FreeBSD 4.2-RELEASE on both the nfs-server and nfs-client. I have used several NFS configs (v2/v3). I have seen references to this problem in old archives (1997, FBSD 2.2.5/6), but it seems the problem has never been fixed. Is this correct? I even read the manual :-( but could not find a solution. Below you will find a small program that reveals the problem, including a fix., which I do not like, because it requires a change in user programs. Regards, Jakob Schripsema sch@kpn.com ------------------------------- #include #include #include #include #define BASEDIR "/FS/testdir" /* NFS mounted */ #define NFILES 1024 main() { create_files(); delete_files(); } create_files() { int i,fd; char buf[2048]; for(i = 0 ; i < NFILES ; i++) { snprintf(buf,2048,"%s/%04d",BASEDIR,i); if ((fd = open(buf,O_CREAT | O_TRUNC | O_WRONLY, 0644)) < 0) { perror(buf); return(-1); } close(fd); } } delete_files() { DIR *dirp; struct dirent *dp; char buf[2048]; if ((dirp = opendir(BASEDIR)) == NULL) { perror("opendir"); return (-1); } while ((dp = readdir(dirp)) != NULL) { if (dp->d_name[0] == '.') continue; snprintf(buf,2048,"%s/%s",BASEDIR,dp->d_name); fprintf(stderr,"%s\n",buf); if (unlink(buf) < 0) { perror(buf); return (-1); } /* This fixes the problem */ rewinddir(dirp); /* End fix */ } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 4:14:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 3A46137B71A for ; Fri, 23 Mar 2001 04:14:49 -0800 (PST) (envelope-from roam@orbitel.bg) Received: (qmail 48736 invoked by uid 1000); 23 Mar 2001 12:13:56 -0000 Date: Fri, 23 Mar 2001 14:13:56 +0200 From: Peter Pentchev To: Matt Simerson Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: The "right" way to build a new world WAS: 4.3-BETA world crashin g 4.2-RELEASE kernel ? Message-ID: <20010323141356.H17216@ringworld.oblivion.bg> Mail-Followup-To: Matt Simerson , "'freebsd-hackers@freebsd.org'" References: <8D18712B2604D411A6BB009027F6449801B4B544@0SEA01EXSRV1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8D18712B2604D411A6BB009027F6449801B4B544@0SEA01EXSRV1>; from mpsimerson@hostpro.com on Thu, Mar 22, 2001 at 06:01:16PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Mar 22, 2001 at 06:01:16PM -0700, Matt Simerson wrote: > OK, let's approach this from a little different angle: > > Below is the appropriate entries from /usr/src/UPDATING on a FreeBSD > 4-stable machine. As of 2/2/2001, the most correct and safest method for > updating your FreeBSD machine is as follows: > > cd /usr/src > make buildworld > make kernel KERNCONF= > reboot (single user) > make installworld > mergemaster > reboot > > I have found that there IS a variety of reasons NOT to do it that way. The > most obvious is that you might not have console access, thus making it > pretty hard to access the machine while it's in single user mode. I can also > think of a couple instances where this method could cause pain. OK, some of your reasons stated below are valid, some are not quite so; in particular, the procedure you are following - running the buildworld and buildkernel at the same time - is not only not-quite-right, but also potentially dangerous - AFAIK, the buildkernel process uses compiler bits from /usr/obj, which might get changed during the compile, leaving you with largely incompatible object/executable files, and no error messages. I understand your reason for wanting both to complete when you get back to work; are you aware that make(1) can process more than one target on the command line, and only build the second target if the first one finishes successfully? What I do is, usually at the end of the day: mergemaster # mergemaster is interactive, yes, but it doesn't # take too much time ;) # and it is sometimes SORELY needed if e.g. mtree files # have changed, potentially breaking the subsequent builds make buildworld buildkernel installkernel installworld # (and I have a KERNCONF?=whatever in my /etc/make.conf) ..thus having the best of both worlds :) G'luck, Peter -- This would easier understand fewer had omitted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 4:49:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dazed.slacker.com (dazed.slacker.com [64.81.115.65]) by hub.freebsd.org (Postfix) with SMTP id 0D53437B71E for ; Fri, 23 Mar 2001 04:49:10 -0800 (PST) (envelope-from nugget@dazed.slacker.com) Received: (qmail 30060 invoked by uid 1000); 23 Mar 2001 12:49:08 -0000 Date: Fri, 23 Mar 2001 06:49:08 -0600 From: David McNett To: Michael Aronsen Cc: "'hackers@freebsd.org'" Subject: Re: Fingerprint authentication? Message-ID: <20010323064908.A28521@dazed.slacker.com> References: <9164771DDCABD3118333005004E9446E43265B@mother.netcentralen.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="AqsLC8rIMeq19msA" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <9164771DDCABD3118333005004E9446E43265B@mother.netcentralen.dk>; from mar@netcentralen.dk on Fri, Mar 23, 2001 at 09:28:20AM +0100 X-Operating-System: FreeBSD 4.2-STABLE i386 X-Distributed: Join the Effort! http://www.distributed.net/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --AqsLC8rIMeq19msA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 23-Mar-2001, Michael Aronsen wrote: > Has anyone been working on or know of any work being done on getting any > fingerprint gadgets working in FreeBSD? This is mostly off-topic, but I wanted to take the opportunity to point out an excellent treatment of the downsides of biometrics (fingerprint gadgets being the most popular such device these days) and concerns that you should be aware of if you're considering adopting biometrics for authentication in your environment. Inside Risks 110, Communications of the ACM, vol 42, n 8, Aug 1999 "Biometrics: Uses and Abuses" by Bruce Schneier http://www.counterpane.com/insiderisks1.html --=20 ________________________________________________________________________ |David McNett |To ensure privacy and data integrity this message has| |nugget@slacker.com|been encrypted using dual rounds of ROT-13 encryption| |Austin, TX USA |Please encrypt all important correspondence with PGP!| --AqsLC8rIMeq19msA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: http://members.slacker.com/~nugget/ iD8DBQE6u0ZEs3nEpeQ8X8MRAlasAJ0akSrs+WCgoyKj0rqZ+m86jEYNngCgpJEq EpptpLSrk46JD2fJvmJBEoc= =WVqD -----END PGP SIGNATURE----- --AqsLC8rIMeq19msA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 5:45: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9974037B71F; Fri, 23 Mar 2001 05:44:52 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f2NDi9h27008; Fri, 23 Mar 2001 08:44:29 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 23 Mar 2001 08:44:09 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Alexey V. Neyman" Cc: "Michael C . Wu" , fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Mar 2001, Alexey V. Neyman wrote: > On Thu, 22 Mar 2001, Michael C . Wu wrote: > > >(Why is vfs.vmiodirenable=1 not enabled by default?) > By the way, is there any all-in-one-place description of sysctl tuneables? > Looking all the man pages and collecting notices about MIB variables seems > rather tiresome and, I think, pointless. I doubt if they are all > documented in man pages. sysctl(3) describes a number of the constant-named sysctl variables, and a number of sysctl's are described in the man pages associated with the features tweaked by the sysctl's. For example, the jail(8) man page describes the jail.* namespace. However, you're right that there are vast hoards of under-documented sysctl's. That said, probably only the "tweakable" (writable) sysctl's need to be documented in the general case, since many are used for the sole purpose of exporting kernel data for supported interfaces, whereas the sysctl's are subject to change. For example, a large number of read-only sysctl's were introduced to support the non-setgid-kmem operation of top, systat, and various other *stat's recently. Also, many sysctl's are "self-documenting", in that the declaration of the sysctl macros in-kernel include a description field. I don't think sysctl(8) currently knows how to read that field, but if you look at the SYSCTL definitions in the kernel source, they're probably a decent starting point. A magic script to extract the sysctl names, types, and descriptions might be useful.. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 5:54:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from xyzzy.intranet.snsonline.net (CPE-61-9-165-100.vic.bigpond.net.au [61.9.165.100]) by hub.freebsd.org (Postfix) with ESMTP id 901CD37B73C; Fri, 23 Mar 2001 05:54:43 -0800 (PST) (envelope-from mark.sergeant@snsonline.net) Received: from xyzzy.intranet.snsonline.net (localhost [127.0.0.1]) by xyzzy.intranet.snsonline.net (8.11.3/8.11.1) with SMTP id f2NDsgO00354; Sat, 24 Mar 2001 00:54:42 +1100 (EST) (envelope-from mark.sergeant@snsonline.net) Message-Id: <200103231354.f2NDsgO00354@xyzzy.intranet.snsonline.net> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit Mime-Version: 1.0 From: "Mark Sergeant" To: freebsd-hackers@FreeBSD.org Cc: freebsd-questions@FreeBSD.org Subject: Kernel compilation error. X-Mailer: Pronto v2.2.2 On freebsd Date: 23 Mar 2001 08:54:40 EST Reply-To: "Mark Sergeant" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to compile into my custom kernel sound support for my css audio chip. I have had no luck though using the suggested lint setting of... device css0 at isa? port 0x534 irq 5 drq 1 flags 0x08 And this fails when it gets to compiling the css options. If I remove this I can compile fine. uname -a output is... FreeBSD xyzzy.intranet.snsonline.net 4.3-RC FreeBSD 4.3-RC #19: Fri Mar 23 23:14:19 EST 2001 And the relevant (I think) dmesg listing for the sound device is... pci0: (vendor=0x8086, dev=0x7195) at 0.1 irq 5 pci0: (vendor=0x8086, dev=0x7196) at 0.2 irq 5 I know this says pci but using pcm / csa doesn't work either. I am running this on a sharp PC AX 20 notebook. cheers, Mark -- The rule on staying alive as a forcaster is to give 'em a number or give 'em a date, but never give 'em both at once. -- Jane Bryant Quinn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 6: 1:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cyclone.eis.ru (for.spb.ru [195.201.69.16]) by hub.freebsd.org (Postfix) with SMTP id 68B9337B71D for ; Fri, 23 Mar 2001 06:00:55 -0800 (PST) (envelope-from diwil@eis.ru) Received: (qmail 12152 invoked from network); 23 Mar 2001 14:04:03 -0000 Received: from good.for.spb.ru (HELO runnet-gw.marketsite.ru) (195.201.69.80) by for.spb.ru with SMTP; 23 Mar 2001 14:04:03 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200103231354.f2NDsgO00354@xyzzy.intranet.snsonline.net> Date: Fri, 23 Mar 2001 16:57:00 +0300 (MSK) Reply-To: diwil@eis.ru From: Dmitry Dicky To: Mark Sergeant Subject: RE: Kernel compilation error. Cc: freebsd-questions@FreeBSD.org, freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Mar-01 Mark Sergeant wrote: > pci0: (vendor=0x8086, dev=0x7195) at 0.1 irq 5 > pci0: (vendor=0x8086, dev=0x7196) at 0.2 irq 5 > Mark, this is Intel 440 MX sound. I sent the driver code to Cameron Grant a while ago. So, it should appear in the CVS tree soon. Dmitry. ********************************************************************* ("`-''-/").___..--''"`-._ (\ Dimmy the Wild UA1ACZ `6_ 6 ) `-. ( ).`-.__.`) Enterprise Information Sys (_Y_.)' ._ ) `._ `. ``-..-' Nevsky prospekt, 20 / 44 _..`--'_..-_/ /--'_.' ,' Saint Petersburg, Russia (il),-'' (li),' ((!.-' +7 (812) 3148860, 5585314 ********************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 6:45:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id D628237B718 for ; Fri, 23 Mar 2001 06:45:26 -0800 (PST) (envelope-from brandt@fokus.gmd.de) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id PAA02861 for ; Fri, 23 Mar 2001 15:45:24 +0100 (MET) Date: Fri, 23 Mar 2001 15:45:24 +0100 (CET) From: Harti Brandt To: Subject: Problems with new RPC Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I described the problem a couple of days on -current, but either I'm doing something dumb or nobody is using ypbind -- I got no answer up to now. So here is it again: the recent update to RPC causes ypbind to break. The problem is, that /usr/src/usr.sbin/ypbind/yp_ping.c mirrors some code from the RPC library, including the internal structure used for the CLIENT structure. The version in libc uses a struct sockaddr_storage (128 bytes) whereas yp_ping has a struct sockaddr_in (something lesser). The libc version also includes a member just at the end of the structure (struct pollfd) that the ypbind version does not have. Because the XDR buffers are allocate directly behind struct CLIENT, this makes the pointers into the buffer wrong. This causes the ypbind child to dump core, which in turn causes the parent to create a new child, which dumps core, causing the parent to create a new child, which dumps core ... A simple fix (rather a workaround is): Index: yp_ping.c =================================================================== RCS file: /usr/ncvs/src/usr.sbin/ypbind/yp_ping.c,v retrieving revision 1.8 diff -u -r1.8 yp_ping.c --- yp_ping.c 2001/03/19 12:50:12 1.8 +++ yp_ping.c 2001/03/20 13:46:24 @@ -93,6 +93,7 @@ #include #include #include +#include #include #include "yp_ping.h" @@ -126,7 +127,7 @@ struct cu_data { int cu_sock; bool_t cu_closeit; - struct sockaddr_in cu_raddr; + struct sockaddr_storage cu_raddr; int cu_rlen; struct timeval cu_wait; struct timeval cu_total; @@ -136,6 +137,7 @@ u_int cu_sendsz; char *cu_outbuf; u_int cu_recvsz; + struct pollfd cu_pollfd; char cu_inbuf[1]; }; Another problem which started at the day the RPC stuff was committed are error messages of the form yp_match: clnt_call: RPC: Program unavailable spit out from various programs, among them pine, tcpdump, tcptrace. How can I fix this (or at least find out, what's the problem)? harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 7: 7:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id DEC9D37B71B for ; Fri, 23 Mar 2001 07:07:16 -0800 (PST) (envelope-from nsouch@fr.alcove.com) Received: from nsouch by smtp.alcove.fr with local (Exim 3.12 #1 (Debian)) id 14gT9m-0003jb-00; Fri, 23 Mar 2001 16:07:14 +0100 Date: Fri, 23 Mar 2001 16:07:14 +0100 From: Nicolas Souchu To: Willem van Engen Cc: freebsd-hackers@freebsd.org Subject: Re: driver: probe not called when smbus child Message-ID: <20010323160714.A11585@ontario.alcove-fr> References: <3AB77C31.8213C158@stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: <3AB77C31.8213C158@stack.nl>; from wvengen@stack.nl on Tue, Mar 20, 2001 at 04:50:09PM +0100 Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Ecom?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 04:50:09PM +0100, Willem van Engen wrote: > I'm trying to write a module which should be a child of the smbus. > When I make the driver a child of the isa bus, identify, probe, > and attach functions are properly called. I use the following > code to do that: > DRIVER_MODULE(my, isa, my_driver, my_devclass, 0, 0); > But when I put it on the smbus using > DRIVER_MODULE(my, smbus, my_driver, my_devclass, 0, 0); > only identify is called. The identify function is as follows: > > static void > my_identify(driver_t *driver, device_t parent) > { > devclass_t dc; > device_t child; > > printf("my: my_identify called\n"); > dc = devclass_find("my"); > if (devclass_get_device(dc, 0)==NULL) { > child = BUS_ADD_CHILD(parent, 0, "my", -1); > } > } > > The driver only uses smbus calls, so I think the best parent > would be smbus. I'm currently working on this. > And when I do a smbus_request_bus, the call waits forever as > it seems. That seems sensible to me, because it asks the > parent for the bus and the isa bus can't grant requests for > the smbus. So I think the driver has to be a child of the smbus. requesting the smbus is needed when the smbus controller potentially share resources on another bus (like lpbb(4) does on ppbus). > Looking in the kernel sources, I see that the only smbus child > I can find, smb, (if there are others, I'm certainly interested) > is attached in the smbus code itself. So the next question rises: > Is it possible to have an smbus child in a dynamically loadable > module (I can't find smbus.ko in /modules, so loading the child > first and then smbus isn't an option I guess) ? Currently, smb is the only smbus child. This is due to the fact that most people prefer programming their SMB chips from user space. I have a patch and a complete modules/i2c tree for compiling smbus and smb as modules. You must be interested... But I have to fix some issues like identification and driver dynamic addition. -- Nicolas.Souchu@fr.alcove.com Alcôve - Open Source Software Engineer - http://www.alcove.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 7: 8:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from crotchety.newsbastards.org (netcop.newsbastards.org [193.162.153.124]) by hub.freebsd.org (Postfix) with ESMTP id EE46237B71D for ; Fri, 23 Mar 2001 07:08:52 -0800 (PST) (envelope-from news@news-feed.inet.tele.dk) Received: (from news@localhost) by crotchety.newsbastards.org (8.11.1/8.11.1) id f2NF8di91831; Fri, 23 Mar 2001 16:08:39 +0100 (CET) (envelope-from news@news-feed.inet.tele.dk) Date: Fri, 23 Mar 2001 16:08:39 +0100 (CET) Message-Id: <200103231508.f2NF8di91831@crotchety.newsbastards.org> X-Authentication-Warning: crotchety.newsbastards.org: news set sender to news@news-feed.inet.tele.dk using -f References: <200103221833.f2MIXQR22409_prism.flugsvamp.com> In-Reply-To: <200103221833.f2MIXQR22409_prism.flugsvamp.com> Cc: hackers@FreeBSD.ORG, usenet@tdk.net Reply-To: Tele Danmark Team of Newsbastards To: jlemon@flugsvamp.com From: Olibert Obdachlos Subject: Re: Intel driver doc's Take 2. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: Hah, me neither. In fact, if you want to try out a binary of my :: Intel GigE driver, it is at http://www.flugsvamp.com/~jlemon/fbsd/drivers :: Jonathan Wow, what I coincidence. I just did a search a couple days ago for any recent developments, and earlier today spent a bit of time with this very driver, with absolutely no idea this conversation had just taken place... A quick background -- some months ago I asked about a Gig ethernet driver when the wx driver didn't seem to work, and I had no e-mail address and was planning to be somewhere else. Well, I still have no e-mail address and I haven't escaped yet, but again, the reply address will reach the people who are in charge of the machinery, and I peek in on the lists now and then. Like now. If I may ask, this binary driver, which cards does it support and which cards does it *not* support? Or if releasing that info is restricted by the NDA, does your driver support the newer Intel Pro/1000 F cards, which had been mentioned here a couple months back (Livengood, if I remember, and which decidedly did not work with the driver by Matthew Jacob)? I did experiment with the driver and the card ealier today for an hour or so without complete success, like no network functionality at all, but I'm not going to rule out pilot error, though it seemed to exhibit similar lack of functionality to the wx driver. If it should work, I'll think about giving it another shot, but if it only works with the 1000 cards (not the F or T) then I won't try the impossible. Or consider this a possible problem report on the driver with the Pro 1000 F... Thanks! barry bouwsma, still stuck at cold snowy TDC internet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 8:43: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id CC5EB37B71A for ; Fri, 23 Mar 2001 08:42:56 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f2NGcgA64895; Fri, 23 Mar 2001 10:38:42 -0600 (CST) (envelope-from jlemon) Date: Fri, 23 Mar 2001 10:38:42 -0600 From: Jonathan Lemon To: Tele Danmark Team of Newsbastards Cc: jlemon@flugsvamp.com, hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. Message-ID: <20010323103842.D82645@prism.flugsvamp.com> References: <200103221833.f2MIXQR22409_prism.flugsvamp.com> <200103231508.f2NF8di91831@crotchety.newsbastards.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200103231508.f2NF8di91831@crotchety.newsbastards.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 23, 2001 at 04:08:39PM +0100, Olibert Obdachlos wrote: > If I may ask, this binary driver, which cards does it support and > which cards does it *not* support? Or if releasing that info is > restricted by the NDA, does your driver support the newer Intel > Pro/1000 F cards, which had been mentioned here a couple months > back (Livengood, if I remember, and which decidedly did not work > with the driver by Matthew Jacob)? I'm admittedly not familiar with Intels marketing nomenclature. But if by "1000 F", you mean the 82543/Livingood chip, then yes, this driver should work on that board. In fact, the driver was designed around the 82543, and then backported to 82542 (wiseman). It won't work with the 1000 T (twisted pair) just yet, since I haven't written the PHY support for that card. (I only have the fiber versions of the card here). But it should work with all the fiber mode cards. > I did experiment with the driver and the card ealier today for an > hour or so without complete success, like no network functionality > at all, but I'm not going to rule out pilot error, though it seemed > to exhibit similar lack of functionality to the wx driver. If it > should work, I'll think about giving it another shot, but if it > only works with the 1000 cards (not the F or T) then I won't try > the impossible. Or consider this a possible problem report on the > driver with the Pro 1000 F... Hmm. Send me details, the more information, the better. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 9:11:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 833AA37B71B for ; Fri, 23 Mar 2001 09:11:41 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2NHB9911637; Fri, 23 Mar 2001 10:11:10 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103231711.f2NHB9911637@harmony.village.org> To: "Matt Simerson" Subject: Re: The "right" way to build a new world WAS: 4.3-BETA world crashin g 4.2-RELEASE kernel ? Cc: "'freebsd-hackers@freebsd.org'" In-reply-to: Your message of "Thu, 22 Mar 2001 18:01:16 MST." <8D18712B2604D411A6BB009027F6449801B4B544@0SEA01EXSRV1> References: <8D18712B2604D411A6BB009027F6449801B4B544@0SEA01EXSRV1> Date: Fri, 23 Mar 2001 10:11:09 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <8D18712B2604D411A6BB009027F6449801B4B544@0SEA01EXSRV1> "Matt Simerson" writes: : I have found that there IS a variety of reasons NOT to do it that way. The : most obvious is that you might not have console access, thus making it : pretty hard to access the machine while it's in single user mode. I can also : think of a couple instances where this method could cause pain. The most obvious reason to do it is that it works. Updating a system can cause pain. Get used to it. There are often times that many of the binaries that are running in multiuser mode can crash your system, so you can't get up into multi user. On major upgrades, you can't even get through the installworld with the old kernel. Having said that, I have often done things not in single user when the jumps were small. I usually get away with it, but have at times really hozed my system. Once or twice to the point I had to take the disk out of the machine and over to a working machine for touch ups. : The first is changing of any of the files used at boot time. I don't allow : telnet access to any of my machines so SSH is often as close as I can get to : console. If anything changes enough that we don't cleanly make it through rc : and friends, processing stops, sshd won't be running and I can't get in. The : one time this happened the machine didn't make it multi user. Fortunately : that machine was in my basement so I walked down, looked at the errors on : the console and finished the upgrade. mountd is a big one why we wouldn't get through rc. I've had it crash the new kernel due to weaknesses in the kernel/user api that it uses. : IPFW changes. This one isn't quite obvious but if you don't compile your : kernel with IPFW_DEFAULT_TO_ACCEPT and changes are made to the kernel or : userland portions and not the other (as will happen in the above scenario) : then upon reboot, if your ruleset doesn't get applied, you won't be able to : access your machine via the network. Ouch. I always compile in the : DEFAULT_TO_ACCEPT for this reason and then add a default deny rule to the : IFPW ruleset. Even so, I find it's best to get my kernel, world, and config : files synced before rebooting. This introduces other problems. In the interrum between ifconfig and ipfw you are wide open to the world. Many attacks only need a few packets to gain root. : cd /usr/src : make buildworld : make kernel KERNCONF= : make installworld : mergemaster : reboot : cd /usr/src : make installkernel KERNEL= Why install the kernel twice? make kernel installs the kernel. : One can also often get away with making a new kernel without first building : world but do so at your own peril (as I often do). :-) I often issue the : buildkernel and buildworld at the same time and then leave for the day. My : reasons for doing this are: laziness, impatience, and wanting to have the : entire compilation done when I return. Doing so can be risky but in my : experience, works just fine with the -stable tree. Others have been quick to : point out the possible hazards of doing so but they mostly apply when : playing with -current. You can also run into problems with -stable. I've run into those problems. It is espeically accute when updating 4.0 machines to 4.3, for example. You are dodging a minefield in doing things this way. You'll also get better milage out of make -j N (say 3 or 4) and doing things sequentially. It is safer and runs just as fast. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 9:52:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 37B2037B71A for ; Fri, 23 Mar 2001 09:52:23 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f2NHqHh29948; Fri, 23 Mar 2001 12:52:17 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 23 Mar 2001 12:52:17 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Warner Losh Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: The "right" way to build a new world WAS: 4.3-BETA world crashin g 4.2-RELEASE kernel ? In-Reply-To: <200103231711.f2NHB9911637@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 23 Mar 2001, Warner Losh wrote: > You'll also get better milage out of make -j N (say 3 or 4) and doing > things sequentially. It is safer and runs just as fast. Dunno if it was a temporary compile problem, but I've actually found that: make -j 3 buildkernel hasn't worked properly for me. Either it was a temporary thing and may be fixed now, or it's a property of the buildkernel dependencies, and should probably be fixed (my kernel build is substantially faster with just a bit of parallelism to keep the CPU busy). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 10:20: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay2.wertep.com (relay2.wertep.com [194.44.90.130]) by hub.freebsd.org (Postfix) with ESMTP id F27D537B718; Fri, 23 Mar 2001 10:19:53 -0800 (PST) (envelope-from petro@She.wertep.com) Received: from She.wertep.com (she-tun-proxy [192.168.252.2]) by relay2.wertep.com (8.9.3/8.9.3) with ESMTP id UAA53092; Fri, 23 Mar 2001 20:19:50 +0200 (EET) (envelope-from petro@She.wertep.com) Received: from localhost (petro@localhost) by She.wertep.com (8.9.3/8.9.3) with ESMTP id UAA68386; Fri, 23 Mar 2001 20:20:44 +0200 (EET) (envelope-from petro@She.wertep.com) Date: Fri, 23 Mar 2001 20:20:39 +0200 (EET) From: petro To: freebsd-hackers@FreeBSD.ORG Cc: freebsd-net@FreeBSD.ORG Subject: PPPD! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Does anybody know about support pppunit in the ppp conf files, or may be can advice me where I can read about pppunit. Thank you very much. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 10:29:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id 38F1437B718; Fri, 23 Mar 2001 10:29:54 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.2/8.11.2) with ESMTP id f2NIU4D17798; Fri, 23 Mar 2001 18:30:04 GMT (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.3/8.11.3) with ESMTP id f2NIWgS13759; Fri, 23 Mar 2001 18:32:42 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200103231832.f2NIWgS13759@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: petro Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: PPPD! In-Reply-To: Message from petro of "Fri, 23 Mar 2001 20:20:39 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 23 Mar 2001 18:32:42 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi! > Does anybody know about support pppunit in the ppp conf files, or may be > can advice me where I can read about pppunit. > Thank you very much. I'm afraid I can't really help, but I believe ppp(8) can do the same thing with the -unit command line switch. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 10:35: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id D93F837B719; Fri, 23 Mar 2001 10:35:02 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f2NIZ1912015; Fri, 23 Mar 2001 11:35:01 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200103231835.f2NIZ1912015@harmony.village.org> To: Robert Watson Subject: Re: The "right" way to build a new world WAS: 4.3-BETA world crashin g 4.2-RELEASE kernel ? Cc: "'freebsd-hackers@freebsd.org'" In-reply-to: Your message of "Fri, 23 Mar 2001 12:52:17 EST." References: Date: Fri, 23 Mar 2001 11:35:01 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Robert Watson writes: : On Fri, 23 Mar 2001, Warner Losh wrote: : : > You'll also get better milage out of make -j N (say 3 or 4) and doing : > things sequentially. It is safer and runs just as fast. : : Dunno if it was a temporary compile problem, but I've actually found that: : : make -j 3 buildkernel : : hasn't worked properly for me. Either it was a temporary thing and may be : fixed now, or it's a property of the buildkernel dependencies, and should : probably be fixed (my kernel build is substantially faster with just a bit : of parallelism to keep the CPU busy). I think that it works. I know that the "old way" works with -j values up to 20 (haven't tried anything higher). There were issues with -j for a while, but those have been fixed. They were inadvertantly introduced when we went to building modules. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 11:57:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from roaming.cacheboy.net (host213-123-132-142.btopenworld.com [213.123.132.142]) by hub.freebsd.org (Postfix) with ESMTP id 9712637B718; Fri, 23 Mar 2001 11:57:33 -0800 (PST) (envelope-from adrian@roaming.cacheboy.net) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.1/8.11.1) id f2NJkkB05859; Fri, 23 Mar 2001 20:46:46 +0100 (CET) (envelope-from adrian) Date: Fri, 23 Mar 2001 20:11:03 +0100 From: Adrian Chadd To: Robert Watson Cc: "Alexey V. Neyman" , "Michael C . Wu" , fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver Message-ID: <20010323201103.A5828@roaming.cacheboy.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rwatson@FreeBSD.ORG on Fri, Mar 23, 2001 at 08:44:09AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 23, 2001, Robert Watson wrote: > > On Fri, 23 Mar 2001, Alexey V. Neyman wrote: > > > On Thu, 22 Mar 2001, Michael C . Wu wrote: > > > > >(Why is vfs.vmiodirenable=1 not enabled by default?) > > By the way, is there any all-in-one-place description of sysctl tuneables? > > Looking all the man pages and collecting notices about MIB variables seems > > rather tiresome and, I think, pointless. I doubt if they are all > > documented in man pages. > > sysctl(3) describes a number of the constant-named sysctl variables, and a > number of sysctl's are described in the man pages associated with the > features tweaked by the sysctl's. For example, the jail(8) man page > describes the jail.* namespace. However, you're right that there are vast > hoards of under-documented sysctl's. That said, probably only the > "tweakable" (writable) sysctl's need to be documented in the general case, > since many are used for the sole purpose of exporting kernel data for > supported interfaces, whereas the sysctl's are subject to change. For > example, a large number of read-only sysctl's were introduced to support > the non-setgid-kmem operation of top, systat, and various other *stat's > recently. Also, many sysctl's are "self-documenting", in that the > declaration of the sysctl macros in-kernel include a description field. I > don't think sysctl(8) currently knows how to read that field, but if you > look at the SYSCTL definitions in the kernel source, they're probably a > decent starting point. A magic script to extract the sysctl names, types, > and descriptions might be useful.. A while back I started running through the undocumented sysctls and documenting them. I didn't get through all of them, and the main reason I stopped was because there wasn't a nifty way to extract the sysctls short of writing a script to extract them from /usr/src. Someone did point out that you could stuff the sysctl's into an elf segment and only load it when needed, but I don't know much about elf. If someone would like to do this, I'm sure a small group of us (Asmodai? :-P) could walk the sysctl tree again and figure out what the undocumented sysctls are. :-) adrian -- Adrian Chadd "Programming is like sex: One mistake and you have to support for a lifetime." -- rec.humor.funny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 12:32:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [209.247.77.155]) by hub.freebsd.org (Postfix) with ESMTP id 490D637B718 for ; Fri, 23 Mar 2001 12:32:08 -0800 (PST) (envelope-from gordont@bluemtn.net) Received: from localhost (gordont@localhost) by sdmail0.sd.bmarts.com (8.11.3/8.11.2/BMA1.1) with ESMTP id f2NKVaL67317; Fri, 23 Mar 2001 12:31:36 -0800 (PST) Date: Fri, 23 Mar 2001 12:31:36 -0800 (PST) From: Gordon Tetlow X-X-Sender: To: Harti Brandt Cc: Subject: Re: Problems with new RPC In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you haven't, please please please, send-pr(1) this so the right people get a look at this. Last thing we need is a broken ypbind (not that I use it). More down below. On Fri, 23 Mar 2001, Harti Brandt wrote: > the recent update to RPC causes ypbind to break. The problem is, that > /usr/src/usr.sbin/ypbind/yp_ping.c mirrors some code from the RPC library, > including the internal structure used for the CLIENT structure. The > version in libc uses a struct sockaddr_storage (128 bytes) whereas yp_ping > has a struct sockaddr_in (something lesser). The libc version also > includes a member just at the end of the structure (struct pollfd) that > the ypbind version does not have. > Because the XDR buffers are allocate directly behind struct CLIENT, this > makes the pointers into the buffer wrong. This causes the ypbind child to > dump core, which in turn causes the parent to create a new child, which > dumps core, causing the parent to create a new child, which dumps core ... > > A simple fix (rather a workaround is): > > Index: yp_ping.c > =================================================================== > RCS file: /usr/ncvs/src/usr.sbin/ypbind/yp_ping.c,v > retrieving revision 1.8 > diff -u -r1.8 yp_ping.c > --- yp_ping.c 2001/03/19 12:50:12 1.8 > +++ yp_ping.c 2001/03/20 13:46:24 > @@ -93,6 +93,7 @@ > #include > #include > #include > +#include > #include > #include "yp_ping.h" > > @@ -126,7 +127,7 @@ > struct cu_data { > int cu_sock; > bool_t cu_closeit; > - struct sockaddr_in cu_raddr; > + struct sockaddr_storage cu_raddr; > int cu_rlen; > struct timeval cu_wait; > struct timeval cu_total; > @@ -136,6 +137,7 @@ > u_int cu_sendsz; > char *cu_outbuf; > u_int cu_recvsz; > + struct pollfd cu_pollfd; > char cu_inbuf[1]; > }; > > Another problem which started at the day the RPC stuff was committed are > error messages of the form > > yp_match: clnt_call: RPC: Program unavailable > > spit out from various programs, among them pine, tcpdump, tcptrace. > How can I fix this (or at least find out, what's the problem)? If I had to take a wild stab, if ypbind isn't working right, I suspect that tcpdump is doing RPC lookups on traffic going by. The rest? ah who knows. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 12:46: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.wuppy.net.ru (ns.WUPPY.NET.RU [212.30.189.130]) by hub.freebsd.org (Postfix) with ESMTP id DFB6337B719 for ; Fri, 23 Mar 2001 12:46:00 -0800 (PST) (envelope-from romanp@unshadow.net) Received: (from uucp@localhost) by ns.wuppy.net.ru (8.11.2/8.11.2) with UUCP id f2NKjd822061; Fri, 23 Mar 2001 23:45:39 +0300 (MSK) (envelope-from romanp@unshadow.net) Received: from localhost (localhost [127.0.0.1]) by abyss.unshadow.net (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f2NKfnG8001096; Fri, 23 Mar 2001 23:41:49 +0300 (MSK) Date: Fri, 23 Mar 2001 23:41:49 +0300 (MSK) From: "Roman V. Palagin" To: petro Cc: Subject: Re: PPPD! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mar 23, at 8:20pm +0200, petro wrote: > Does anybody know about support pppunit in the ppp conf files, or may be > can advice me where I can read about pppunit. > Thank you very much. pppunit is for pppd. Check out ftp://room101.wuppy.net.ru/pppd. - Roman --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 12:48:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from crotchety.newsbastards.org (netcop.newsbastards.org [193.162.153.124]) by hub.freebsd.org (Postfix) with ESMTP id 6AA4937B726 for ; Fri, 23 Mar 2001 12:48:00 -0800 (PST) (envelope-from news@news-feed.inet.tele.dk) Received: (from news@localhost) by crotchety.newsbastards.org (8.11.1/8.11.1) id f2NKlwU92669; Fri, 23 Mar 2001 21:47:58 +0100 (CET) (envelope-from news@news-feed.inet.tele.dk) Date: Fri, 23 Mar 2001 21:47:58 +0100 (CET) Message-Id: <200103232047.f2NKlwU92669@crotchety.newsbastards.org> X-Authentication-Warning: crotchety.newsbastards.org: news set sender to news@news-feed.inet.tele.dk using -f References: <200103221833.f2MIXQR22409@prism.flugsvamp.com> <200103231508.f2NF8di91831@crotchety.newsbastards.org> <20010323103842.D82645@prism.flugsvamp.com> In-Reply-To: <20010323103842.D82645@prism.flugsvamp.com> Cc: hackers@FreeBSD.ORG, usenet@tdk.net Reply-To: Tele Danmark Team of Newsbastards To: jlemon@flugsvamp.com From: Olibert Obdachlos Subject: Re: Intel driver doc's Take 2. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > restricted by the NDA, does your driver support the newer Intel > > Pro/1000 F cards, which had been mentioned here a couple months > I'm admittedly not familiar with Intels marketing nomenclature. But > if by "1000 F", you mean the 82543/Livingood chip, then yes, this > driver should work on that board. Thanks! That's exactly what I was hoping to know before getting too deep over my head. Consider yourself lucky -- I spent a while navigating the Intel website to see if much had changed. I did dig up the old message I had sent which isn't worth reposting, but may contain pointers to marketroid data and the like. It's from 19.Jan in -hardware, Message-ID: <200101192209.f0JM9pD93464@crotchety.newsbastards.org> or news:200101192209.f0JM9pD93464_crotchety.newsbastards.org@ns.sol.net but it's probably not worth digging out of the archive now. > In fact, the driver was designed > around the 82543, and then backported to 82542 (wiseman). I haven't had my sweaty hands over one of these cards, but I'll assume the 82543GC discussed in these messages is equivalent. I'll also try to get a close look at a card to know what is in use. > > the impossible. Or consider this a possible problem report on the > > driver with the Pro 1000 F... > > Hmm. Send me details, the more information, the better. I'll wait a second before passing on details I don't have at hand, because I can't say I trust the test machine it was placed in, which spontaneously rebooted on me at reboot time, and then wedged up at a following reboot. I think it needs a high-speed lesson through the machine room to meet Mister Floor. Also, I don't trust the configuration that dmesg reveals at boot -- I got stellar performance from a similar machine when it assigned IRQs like 20 and 21 to the fxp ethernet card, while on a different HP machine, I had hell trying to get both an ethernet card and a pile of sound cards to work, when IRQs were given similar to what this test machine wants to give, and I needed to do some juggling of cards to get anything to happen. Everything worked great when I got the high IRQs though. So it's quite possible that this machine needs to have the gigabit ethernet card swapped around -- it came up at irq5. This card is also installed in another machine currently doing production service and was given irq21 or something, so there is definitely some weird BIOS difference between the two machines. I hate PC hardware. This will probably wait til monday, and I'll also ask our techie who posted some details last time if he's seeing exactly the same thing now. I made some tests I didn't try last time, but before I make any claims, I want to eliminate the possibility of flaky hardware at this end and gather relevant details. Thanks, I'll get back to you about this... barry bouwsma, resident TDC internet netmangler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 14:42: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id 8E6C137B719 for ; Fri, 23 Mar 2001 14:42:02 -0800 (PST) (envelope-from rh@matriplex.com) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id OAA09662 for ; Fri, 23 Mar 2001 14:41:51 -0800 (PST) (envelope-from rh@matriplex.com) Date: Fri, 23 Mar 2001 14:41:51 -0800 (PST) From: Richard Hodges To: freebsd-hackers@FreeBSD.ORG Subject: Re: kern/23620: Fore PCA200E driver In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I hate to follow up on my own post, but I have not heard a word of comment, positive or negative... -Richard On Fri, 2 Mar 2001, Richard Hodges wrote: > Hi, all! > > A couple months ago, I submitted PR kern/23620 describing a problem > with the Fore PCA200E driver for HARP. It includes a description > of the problems and a patch. > > Could someone commit this to STABLE so that it has a chance of > making it into 4.3 RELEASE? ------------------------------------------- Richard Hodges | Matriplex, inc. Product Manager | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 14:45:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id DB0E537B71A for ; Fri, 23 Mar 2001 14:45:07 -0800 (PST) (envelope-from archie@dellroad.org) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id OAA07850; Fri, 23 Mar 2001 14:35:21 -0800 (PST) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.1/8.11.1) id f2NMYmf28390; Fri, 23 Mar 2001 14:34:48 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200103232234.f2NMYmf28390@arch20m.dellroad.org> Subject: Re: question about BPF programming In-Reply-To: <99d8mo$2cbo$1@igloo.uran.net.ua> "from Andrey Simonenko at Mar 22, 2001 06:15:50 pm" To: Andrey Simonenko Date: Fri, 23 Mar 2001 14:34:48 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrey Simonenko writes: > I read bpf(4) man page and have one question about BPF. > Suppose I open one of free BPF devices /dev/bpf??. I can dup(2) > descriptor of opened BPF device and get so called shared interface. > > Can I setup different filters on each descriptor for opened BPF device? Nope. Quoting dup(2): The object referenced by the descriptor does not distinguish between oldd and newd in any way. Thus if newd and oldd are duplicate references to an open file, read(2), write(2) and lseek(2) calls all move a single pointer into the file, and append mode, non-blocking I/O and asynchronous I/O options are shared between the references. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 18: 3:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id AC6AE37B71A for ; Fri, 23 Mar 2001 18:03:47 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2O23ie53119; Fri, 23 Mar 2001 18:03:44 -0800 (PST) (envelope-from obrien) Date: Fri, 23 Mar 2001 18:03:44 -0800 From: "David O'Brien" To: "Alexander N. Kabaev" Cc: hackers@FreeBSD.ORG, Max Khon Subject: Re: GCC Upgrade? Message-ID: <20010323180344.A53093@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010321094638.E92274@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ak03@gte.com on Wed, Mar 21, 2001 at 01:35:30PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Mar 21, 2001 at 01:35:30PM -0500, Alexander N. Kabaev wrote: > This patch will work. According to Berndt Schimidt, there are some problems > with it on HP/UX and that was the main reason why it was backed out. I never saw > any ill effects on i386 with this patch though, while good efects include: > > a) working sjlj exceptions > b) ability to compile QT2 with exceptions enabled and with -O2 flag without > consuming ~400M memory for abnormal call egdes in GCC flow optimization pass. It has been committed now and will be MFC'ed to stable after tax day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Mar 23 23:36:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 8B0C437B719 for ; Fri, 23 Mar 2001 23:36:29 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f2O7aU314303 for ; Sat, 24 Mar 2001 08:36:30 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: hackers@freebsd.org Subject: so where is our press-release about MacOS X ? From: Poul-Henning Kamp Date: Sat, 24 Mar 2001 08:36:30 +0100 Message-ID: <14301.985419390@critter> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shouldn't the FreeBSD project issue a press release welcoming Apple's MacOS X ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 0: 5:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 25B1437B71B; Sat, 24 Mar 2001 00:05:08 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from mobile.wemm.org (mobile.wemm.org [10.0.0.5]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f2O858p05108; Sat, 24 Mar 2001 00:05:08 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f2O856h92540; Sat, 24 Mar 2001 00:05:06 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200103240805.f2O856h92540@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Mike Smith Cc: scanner@jurai.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: <200103222037.f2MKbrs01583@mass.dis.org> Date: Sat, 24 Mar 2001 00:05:06 -0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > On Fri, 23 Mar 2001, Daniel C. Sobral wrote: > > > > > Let me just pipe in a bit. Compromise seems just like the kind of thing > > > marketing or legal would want to do. The problem is that _we_ cannot > > > compromise because one cannot write a "half-way there" driver. It's a > > > technical impossibility. > > > > I agree 100%. I don't think this will fly either. I am just making the > > effort to work with Intel to get what we need. It's not going to happen > > overnight. Period. They are not going to change their NDA policy. In the > > future maybe. Actually I will forward the email she sent me this last time > > after I got off the phone with her an hour ago. I mentioned the problems > > Jonathan had with the GigE card. That's why she refers to him. Anyway I > > will forward it in a sec to the list. > > [Speaking here from some experience with this set of issues.] > > The compromise that you want to strike, and really the *only* compromise > that is going to work, is that the *documents* will remain undisclosed, > but information from the documents that is necessary to produce a > functional, high-performance driver may be disclosed, but *only* through > the source code of the driver. > > Thus one or a small group of people sign the NDA, and keep the > documentation. The driver is then developed and maintained by this team, > who also have the opportunity to interact with Intel's engineering > people. The source code resulting from this effort is then released > publically. Intel should probably retain the right to veto code that you > might want to put in the driver if they feel that it risks disclosure > they don't want, but you don't have to suggest this to them unless you > feel you need it as a bargaining chip. > > This would put them in the same situation as they are already in with > their source-available Linux driver; it should not present any more > intellectual property risks than they already face, and as a bonus, it > gets us a better-supported driver. Yes, but for goodness's sake, make sure there are time limits on it! Try this: 1 - Give a select group of people the docs under NDA 2 - If there are any specific features Intel wants avoided, get them to identify them up front. 3 - Let them write a driver that uses whatever features that are useful, with header files that define the register bits etc that are reasonably related to the features used. 4 - Hand over the driver to intel for "final veto" with a pre-agreement in place so that if they do not respond in 30 days we can release it as-is. 5 - If they have specific features or register bit definitions that they want removed, then do so as long as it isn't going to hopelessly cripple the driver. If they want something removed that wasn't covered in the list at the start and is going to cause severe performance problems (say a 10% performance or efficiency drop), too bad. 6 - Repeat the loop for 'final veto' but with a week timeout instead of 30 days. Regarding step 5; if the information is already "out there" (other open source drivers, leaked onto the internet, etc) then it is fair game and we can use it. With somebody like Intel, it is pretty important to get this in some form of writing. They have a horrible habbit of "forgetting" things that are "too hard" (eg: sweeping your driver for unused information). The reason Intel keep a tight lid on this stuff is that they are very afraid of losing their "competitive advantage" of having functional fxp drivers in the Windows installation, while most of the other ethernet cards do not. If somebody can clone the 8255x series such that it is "close enough" from publically available documentation that it will work with the windoze CD drivers, then Intel loses the upper hand. *That* is what they are afraid of. If some taiwanese manufacturer makes a clone and intel goes after them, and they can point to the freebsd fxpreg.h file that thoughtfully defines every single bit and register in the NDA manuals, you can bet that Intel wont be happy. On the other hand, if it meant that they would have had to pull the drivers apart (illegal under DMCA in the US), Intel would be able to sue them to death if they ever tried to sell it in the US. And then there's always the 'trade secrets' lawsuits of death. (remember Intel vs VIA over the "Apollo" BX chipset workalike). The 'yellow manual' describes the chips, steppings, quirks, workarounds, etc in painful detail... In enough detail that one could do a legal 'clean room' implementation if the manual were freely available. However, there are lots of things that would never go into a FreeBSD driver. Things like the microcode interfaces for the wake-on-lan sequencer/filter, etc. There are a bunch of stuff that is totally irrelevant to us. There are a bunch of things on the chips that are so badly broken that they are not useful to us at all (eg: the checksum assistance on the 82559). I'm sure that we could arrange to leave out enough information to make the FreeBSD driver not useful for trying to clean-room a chipset from that would work under windows. On the other hand, maybe Intel do this "just because". Remember what happened with the AMD386 and 486? I bet they never want to take a chance that might happen again. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 0:17:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 294DE37B71A; Sat, 24 Mar 2001 00:17:15 -0800 (PST) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from deneb (deneb [128.130.111.2]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f2O8HBe23577; Sat, 24 Mar 2001 09:17:12 +0100 (MET) Date: Sat, 24 Mar 2001 09:17:12 +0100 (CET) From: Gerald Pfeifer To: , Subject: Displaying options for current NFS mounts Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried to get some responses to this on -questions a couple of months ago, but failed: What I'd like to see is `mount -v' printing mail:/var/mail on /var/mail (nfs: v3, udp) vexpert:/files7 on /system (nfs: v3, tcp) vexpert:/files5 on /.amd_mnt/vexpert/files5 (nfs: v3, udp) ^^^^^^^^^^^^ instead of mail:/var/mail on /var/mail (nfs) vexpert:/files7 on /system (nfs) vexpert:/files5 on /.amd_mnt/vexpert/files5 (nfs) ^^^ This kind of information is incredibly useful for debugging, yet I haven't found ANY way to obtain it, let alone such a natural one. Gerald To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 1:27:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (jason.argos.org [216.233.245.106]) by hub.freebsd.org (Postfix) with ESMTP id BD86137B71B for ; Sat, 24 Mar 2001 01:27:21 -0800 (PST) (envelope-from mike@jason.argos.org) Received: (from mike@localhost) by jason.argos.org (8.10.1/8.10.1) id f2O9CiK28823 for freebsd-hackers@freebsd.org; Sat, 24 Mar 2001 04:12:44 -0500 Date: Sat, 24 Mar 2001 04:09:12 -0500 From: Mike Nowlin To: David McNett Subject: Re: Fingerprint authentication? Message-ID: <20010324040912.A28324@argos.org> References: <9164771DDCABD3118333005004E9446E43265B@mother.netcentralen.dk> <20010323064908.A28521@dazed.slacker.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010323064908.A28521@dazed.slacker.com>; from nugget@slacker.com on Fri, Mar 23, 2001 at 06:49:08AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 0, David McNett wrote: > On 23-Mar-2001, Michael Aronsen wrote: > > Has anyone been working on or know of any work being done on getting any > > fingerprint gadgets working in FreeBSD? >=20 > This is mostly off-topic, but I wanted to take the opportunity to point > out an excellent treatment of the downsides of biometrics (fingerprint > gadgets being the most popular such device these days) and concerns that > you should be aware of if you're considering adopting biometrics for > authentication in your environment. Just read the article - he does bring up some good points, but he does (sort of) miss one point - biometrics are most useful when combined with some other form of authentication. (What you have (fingerprint), plus what you know (password)). On that note, I'll put this on-topic for -hackers... (In my opinion...) Due to the upcoming HIPAA regulations mandated by HCFA (see note 1), I am extremely interested in writing a driver to read data from one of the various fingerprint gizmos on the market. Does anyone have any experience with these (good/bad), or suggestions as to which ones might lend themselves toward a FBSD driver? mike Note 1 (as promised) -------------------- (Non-US residents - this doesn't apply to you... Be grateful... :) ) HIPAA (Health Insurance Portability and Accountability Act) is a set of rules scheduled to take effect in (last I checked - they keep changing it) October 2002 by HCFA (the Health Care Financing Administration), the federal agency that is responsible for Medicare, Medicaid, etc. Basically, HIPAA is designed to make sure that everyone gets a fair shot at medical insurance. However, there is a section in there that deals with privacy of medical records, and that's where the geek factor comes into play. The phrase going around the IT departments of health care providers right now goes something like "HIPAA will cost health care providers three to four times more money than Y2K did." (It's a big deal.) Essentially, the old "username and password" method of verification is completely inadequate - they want Smart Cards, fingerprints, retinal scans, infrared facial signatures, and the last four digits of your dog's Social Security number just to keep the guard, armed with an AK-47, to keep from shooting you as you walk up to the keyboard to type in your username and password. (OK, that's stretching it a little bit, but that's really the attitude they're taking with this.) =20 (Political statement starts here - sorry....) Ah, the joys of living in the USA... Can't let teachers discipline kids (and the parents get thrown in jail for doing so), but dammit, we'll make sure that nobody finds out that Joe Schmoe has high cholesterol and needs to get out and exercise a bit... (And yes, I do enjoy living here, but the political correctness of it gets to me at times.) --mike --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjq8ZDgACgkQJol4I8h9Gd83KQCgxWZfCrWiFpd5se4F/RE2C4QC T4UAnj8bS/dV5SiKIoUitpBkjnBso8Vi =UFaE -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 1:30: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-43.dsl.lsan03.pacbell.net [63.207.60.43]) by hub.freebsd.org (Postfix) with ESMTP id 46C1137B71A; Sat, 24 Mar 2001 01:29:55 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0242C66C3B; Sat, 24 Mar 2001 01:29:54 -0800 (PST) Date: Sat, 24 Mar 2001 01:29:54 -0800 From: Kris Kennaway To: Poul-Henning Kamp Cc: hackers@freebsd.org Subject: Re: so where is our press-release about MacOS X ? Message-ID: <20010324012954.A31961@xor.obsecurity.org> References: <14301.985419390@critter> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14301.985419390@critter>; from phk@freebsd.org on Sat, Mar 24, 2001 at 08:36:30AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 24, 2001 at 08:36:30AM +0100, Poul-Henning Kamp wrote: >=20 > Shouldn't the FreeBSD project issue a press release welcoming > Apple's MacOS X ? Good idea, write one :-) Kris --XsQoSWH+UP9D9v3l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6vGkSWry0BWjoQKURAu4OAJ9sF0/q6V8Nxoac7Nr80PnIUBqGlQCfTlck 5itjske+YGI05Yzv5tLrT04= =XY/C -----END PGP SIGNATURE----- --XsQoSWH+UP9D9v3l-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 3:40:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from samar.sasi.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 9B10137B71A for ; Sat, 24 Mar 2001 03:40:11 -0800 (PST) (envelope-from madhavis@sasken.com) Received: from samar (samar.sasi.com [164.164.56.2]) by samar.sasi.com (8.9.3/8.9.3) with SMTP id RAA09850 for ; Sat, 24 Mar 2001 17:10:05 +0530 (IST) Received: from pcs111.sasi.com ([10.0.36.111]) by samar.sasi.com; Sat, 24 Mar 2001 17:10:05 +0000 (IST) Received: from localhost (madhavis@localhost) by pcs111.sasi.com (8.9.3/8.9.3) with ESMTP id RAA15467 for ; Sat, 24 Mar 2001 17:10:05 +0530 X-Authentication-Warning: pcs111.sasi.com: madhavis owned process doing -bs Date: Sat, 24 Mar 2001 17:10:04 +0530 (IST) From: Madhavi Suram X-Sender: madhavis@pcs111.sasi.com To: freebsd-hackers@FreeBSD.ORG Subject: udp checksum problem.. In-Reply-To: <20010324012954.A31961@xor.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I am modifying FreeBSD 4.1 kernel. I am hacking all UDP packets in ip_input, changing some headers and finding the udp checksum using in_pseudo() and setting the packet header csum_flags to CSUM_UDP (I know this is a dirty way of doing it.. but, had to do it for efficiency reasons). When I try to see the checksum after the checksum calculation is complete in ip_output, I am getting the checksum 65535(0xffff). Is this a special checksum(error or something like that..)? I have seen INVERT doing something like this in the file /sys/alpha/alpha/in_cksum.c. sum == 0xffff ? 0xffff : ~sum & 0xffff. After modifying the packet in ip_input(), I call ip_forward() and the packet should go and reach the intended destination as usual. But, this destination address is the one that is changed in ip_input(). But, the destination host is not getting the packet. I think this is a checksum problem. Could anyone please tell me what checksum 0xffff means, or give me some pointers to where I can find this information? Also, could anyone tell me if there are any csum_flags other than CSUM_UDP and CSUM_DELAY_DATA in the mbuf packet header that can be set before a udp packet reaches ip_output()? thanks in advance. regards Madhavi. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 4:23:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id CF9AA37B718; Sat, 24 Mar 2001 04:23:40 -0800 (PST) (envelope-from ru@whale.sunbay.crimea.ua) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.2/8.11.2) id f2OCIRo41069; Sat, 24 Mar 2001 14:18:27 +0200 (EET) (envelope-from ru) Date: Sat, 24 Mar 2001 14:18:27 +0200 From: Ruslan Ermilov To: Madhavi Suram Cc: freebsd-hackers@FreeBSD.ORG, Jonathan Lemon Subject: Re: udp checksum problem.. Message-ID: <20010324141827.A38948@sunbay.com> Mail-Followup-To: Madhavi Suram , freebsd-hackers@FreeBSD.ORG, Jonathan Lemon References: <20010324012954.A31961@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from madhavis@sasken.com on Sat, Mar 24, 2001 at 05:10:04PM +0530 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 24, 2001 at 05:10:04PM +0530, Madhavi Suram wrote: > > Hi > > I am modifying FreeBSD 4.1 kernel. I am hacking all UDP packets in > ip_input, changing some headers and finding the udp checksum > using in_pseudo() and setting the packet header csum_flags to > CSUM_UDP (I know this is a dirty way of doing it.. but, had to do it > for efficiency reasons). When I try to see the checksum after the checksum > calculation is complete in ip_output, I am getting the checksum > 65535(0xffff). Is this a special checksum(error or something like > that..)? I have seen INVERT doing something like this in the file > /sys/alpha/alpha/in_cksum.c. > > sum == 0xffff ? 0xffff : ~sum & 0xffff. > > After modifying the packet in ip_input(), I call ip_forward() and the > packet should go and reach the intended destination as usual. But, this > destination address is the one that is changed in ip_input(). But, the > destination host is not getting the packet. I think this is a checksum > problem. > > Could anyone please tell me what checksum 0xffff means, or give me some > pointers to where I can find this information? > INVERT was a failed attempt to comply with RFC 768 requirement to transmit all zero computed checksum as all ones. For some unknown reason, the fix (sys/alpha/alpha/in_cksum.c, revision 1.5) was not yet MFC'ed. Cheers, -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 4:57:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from 192.76.134.35 (worker.thw-IP.NET [192.76.134.35]) by hub.freebsd.org (Postfix) with ESMTP id 0141E37B71A; Sat, 24 Mar 2001 04:57:40 -0800 (PST) (envelope-from kts.org!hm@worker.thw-IP.NET) Received: from localhost (1688 bytes) by worker.thw-IP.NET via rmail with P:stdio/R:inet_mx_hosts/T:inet_zone_smtp (sender: ) (ident using unix) id for ; Sat, 24 Mar 2001 13:57:32 +0100 (CET) (Smail-3.2.0.112 2001-Feb-5 #5 built 2001-Mar-21) Received: from bert.kts.org (bert.kts.org [194.55.156.2]) by ernie.kts.org (Postfix) with ESMTP id 15B0B52A8E; Sat, 24 Mar 2001 13:06:11 +0100 (CET) Received: by bert.kts.org (Postfix, from userid 100) id 18BCD9B22; Sat, 24 Mar 2001 13:06:10 +0100 (CET) Subject: Re: Intel driver doc's Take 2. In-Reply-To: <200103240805.f2O856h92540@mobile.wemm.org> from Peter Wemm at "Mar 24, 2001 0: 5: 6 am" To: peter@netplex.com.au (Peter Wemm) Date: Sat, 24 Mar 2001 13:06:10 +0100 (CET) Cc: msmith@FreeBSD.ORG, scanner@jurai.net, freebsd-hackers@FreeBSD.ORG Organization: Kitchen Table Systems Reply-To: hm@kts.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Message-Id: <20010324120610.18BCD9B22@bert.kts.org> From: hm@kts.org (Hellmuth Michaelis) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm wrote: > However, there are lots of things that would never go into a FreeBSD driver. > Things like the microcode interfaces for the wake-on-lan sequencer/filter, > etc. I´m trying for nearly a year now to get the docs from Intel for exactly this feature because i need it for a client who wishes to release the result back into FreeBSD. Although i have met and spoken to many helpful people from Intel, they all ran against a rubber wall sooner or later .... hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 5:42: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from heechee.tobez.org (254.adsl0.ryv.worldonline.dk [213.237.10.254]) by hub.freebsd.org (Postfix) with ESMTP id 2B4B037B71E; Sat, 24 Mar 2001 05:41:52 -0800 (PST) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id D9D95550E; Sat, 24 Mar 2001 14:41:50 +0100 (CET) Date: Sat, 24 Mar 2001 14:41:50 +0100 From: Anton Berezin To: Adrian Chadd Cc: Robert Watson , "Alexey V. Neyman" , "Michael C . Wu" , fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver Message-ID: <20010324144150.A59930@heechee.tobez.org> References: <20010323201103.A5828@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010323201103.A5828@roaming.cacheboy.net>; from adrian@FreeBSD.ORG on Fri, Mar 23, 2001 at 08:11:03PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Mar 23, 2001 at 08:11:03PM +0100, Adrian Chadd wrote: > A while back I started running through the undocumented sysctls and > documenting them. I didn't get through all of them, and the main reason > I stopped was because there wasn't a nifty way to extract the sysctls > short of writing a script to extract them from /usr/src. > > Someone did point out that you could stuff the sysctl's into an elf > segment and only load it when needed, but I don't know much about elf. > If someone would like to do this, I'm sure a small group of us > (Asmodai? :-P) could walk the sysctl tree again and figure out what > the undocumented sysctls are. :-) Some time ago I wrote such a script and even sent it to someone; never got any response, though. It is pretty minimal but does the job. I believe that the only sysctls it misses are those which use auxilliary defines to minimize the number of parameters (like #define P1B_SYSCTL in posix4/posix4_mib.c). FWIW, the script is attached. Cheers, &Anton. -- May the tuna salad be with you. --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=sysctl_find #! /usr/bin/perl -w use File::Find; use Text::ParseWords; sub check_file { return unless /\.c$/ && -r; local $/; open SRC, "< $_" or print( "can't open $File::Find::dir: $!"), return; my $src = ; # memory hog close SRC; my @found = ($src =~ /\nSYSCTL_(\w+\([^()]+\))/sg); return unless @found; print "$File::Find::dir/$_:\n"; for (@found) { tr/\n\t / /s; my ($type) = /^(\w+)\(/; next if $type eq "DECL"; s/^.*\(//; s/\)//; my @args = quotewords ',', 1, $_; #print "|@args|\n"; $args[0] =~ s/^\s*_//; $args[0] =~ s/\s+$//; $args[0] =~ tr/_/./; $args[2] =~ s/^\s+//; $args[2] =~ s/\s+$//; print "$type\t$args[0].$args[2]\t$args[-1]\n"; } } find( \&check_file, '/usr/src/sys'); --k+w/mQv8wyuph6w0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 6:21:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id CB5BC37B719; Sat, 24 Mar 2001 06:21:18 -0800 (PST) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id PAA09436; Sat, 24 Mar 2001 15:21:06 +0100 (CET) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Matt Dillon Cc: Alfred Perlstein , "Michael C . Wu" , Rik van Riel , Peter Wemm , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver References: <200103211114.f2LBE0h57371@mobile.wemm.org> <20010321120620.A932@peorth.iteration.net> <200103211817.f2LIHR416007@earth.backplane.com> <20010321102836.N12319@fw.wintelcom.net> <200103211907.f2LJ7cp17933@earth.backplane.com> From: Dag-Erling Smorgrav Date: 24 Mar 2001 15:21:05 +0100 In-Reply-To: Matt Dillon's message of "Wed, 21 Mar 2001 11:07:38 -0800 (PST)" Message-ID: Lines: 11 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Dillon writes: > So you would be able to create approximately four 17GB swap partitions. > If you reduce NSWAP to 2 you would be able to create approximately > two 34GB swap partitions. If you reduce NSWAP to 1 you would be able > to create approximately one 68GB swap partition. "approximately one"? :) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 6:49:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9EFCF37B71A; Sat, 24 Mar 2001 06:49:06 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f2OEmsh45675; Sat, 24 Mar 2001 09:48:54 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 24 Mar 2001 09:48:53 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Kris Kennaway Cc: Poul-Henning Kamp , hackers@freebsd.org Subject: Re: so where is our press-release about MacOS X ? In-Reply-To: <20010324012954.A31961@xor.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Mar 2001, Kris Kennaway wrote: > On Sat, Mar 24, 2001 at 08:36:30AM +0100, Poul-Henning Kamp wrote: > > > > Shouldn't the FreeBSD project issue a press release welcoming > > Apple's MacOS X ? > > Good idea, write one :-) To be a really effective press release, it should be joint released with Apple, or at the very least include quotes from Apple folk (and with their permission, mind you :-). They're probably pretty busy right now, but if you want to take it off-line, we can discuss that in detail. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 6:54: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id D4E0F37B718; Sat, 24 Mar 2001 06:53:59 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f2OEs0317534; Sat, 24 Mar 2001 15:54:00 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: Kris Kennaway , hackers@freebsd.org Subject: Re: so where is our press-release about MacOS X ? In-Reply-To: Your message of "Sat, 24 Mar 2001 09:48:53 EST." Date: Sat, 24 Mar 2001 15:54:00 +0100 Message-ID: <17532.985445640@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Robe rt Watson writes: > >On Sat, 24 Mar 2001, Kris Kennaway wrote: > >> On Sat, Mar 24, 2001 at 08:36:30AM +0100, Poul-Henning Kamp wrote: >> > >> > Shouldn't the FreeBSD project issue a press release welcoming >> > Apple's MacOS X ? >> >> Good idea, write one :-) > >To be a really effective press release, it should be joint released with >Apple, or at the very least include quotes from Apple folk (and with their >permission, mind you :-). They're probably pretty busy right now, but if >you want to take it off-line, we can discuss that in detail. I think you can assume that Jordan will veto me writing anything even remotely like a press-release for the project. I just thought it was a very good opportunity to beat the drum... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 8:48:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1B42137B71A; Sat, 24 Mar 2001 08:48:39 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA24646; Sat, 24 Mar 2001 08:48:40 -0800 Date: Sat, 24 Mar 2001 08:48:35 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Wemm Cc: Mike Smith , scanner@jurai.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: <200103240805.f2O856h92540@mobile.wemm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1 - Give a select group of people the docs under NDA > 2 - If there are any specific features Intel wants avoided, get them to > identify > them up front. > 3 - Let them write a driver that uses whatever features that are useful, with > header files that define the register bits etc that are reasonably related > to the features used. > 4 - Hand over the driver to intel for "final veto" with a pre-agreement in > place so that if they do not respond in 30 days we can release it as-is. > 5 - If they have specific features or register bit definitions that they want > removed, then do so as long as it isn't going to hopelessly cripple the > driver. If they want something removed that wasn't covered in the list at > the start and is going to cause severe performance problems (say a 10% > performance or efficiency drop), too bad. > 6 - Repeat the loop for 'final veto' but with a week timeout instead of 30 > days. > > Regarding step 5; if the information is already "out there" (other open > source drivers, leaked onto the internet, etc) then it is fair game and we > can use it. Step 4 is a lose. That will never fly because they don't have the interest or bandwidth to review. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 9:13:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 0C54E37B719; Sat, 24 Mar 2001 09:13:29 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id MAA04472; Sat, 24 Mar 2001 12:14:20 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010324122812.038f4eb0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 24 Mar 2001 12:31:05 -0500 To: "Kenneth D. Merry" From: Dennis Subject: Re: AW: Best Gigabit ethernet for 4.x Cc: "Schmalzbauer, Harald" , hackers@FreeBSD.ORG, isp@FreeBSD.ORG In-Reply-To: <20001118150437.A15956@panzer.kdm.org> References: <5.0.0.25.0.20001118113245.032d3130@mail.etinc.com> <5.0.0.25.0.20001118113245.032d3130@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:04 PM 11/18/2000, Kenneth D. Merry wrote: >On Sat, Nov 18, 2000 at 11:33:29 -0500, Dennis wrote: > > At 04:28 PM 11/17/2000, Schmalzbauer, Harald wrote: > > >I just heard that Intel doesn't supply documentation on ther chipset > and the > > >FreeBSD and Linux support is quiet bad. The Netgear GA620 is said to be > > >twice as fast. The same Chipset (Alteon Tigon/AceNIC) is on the 3com985. > > > > > > Are all of the cards supported that use this chipset? I read somewhere > that > > the netgear card has a smallish buffer, and that the alteon was a better > > choice. How does the 3com card compare in that respect? > >The Netgear boards have 512K SRAM, the 3Com boards have 1MB SRAM. > >You can get Alteon-branded boards (with either 512K or 1MB SRAM), but >generally only directly from Alteon, and you're going to pay more than you >would for either the 3Com or Netgear boards. > >The 3Com and Netgear boards are identical to the Alteon boards. The only >difference is they've got "Netgear" or "3Com" silk-screened on them, and >the Alteon boards don't have any logos on them. > >FWIW, 3Com is buying Alteon's NIC group. Apparantly (according to an >Alteon engineer who posted on the linux-acenic list) they're just buying >the technology, not hiring the engineers: When you say "identical", that implies that they are the same...or do you just mean that they use the same parts? It seems unlikely that alteon would allow netgear to license its product and them sell it for 1/2 the price. Price is not an issue at this level as performance is tantamount, but Im not sure you'd need more than 512M with unix unless you have several NICs in a box. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 9:32:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 55C5A37B719; Sat, 24 Mar 2001 09:32:11 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id SAA49447; Sat, 24 Mar 2001 18:31:44 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200103241731.SAA49447@info.iet.unipi.it> Subject: Re: Intel driver doc's Take 2. In-Reply-To: from Matthew Jacob at "Mar 24, 2001 08:48:35 am" To: mjacob@feral.com Date: Sat, 24 Mar 2001 18:31:44 +0100 (CET) Cc: Peter Wemm , Mike Smith , scanner@jurai.net, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have read the thread for a while, and i wonder: why in the world someone should go through the effort and responsibility of SIGNING THE NDA _and_ negotiating with Intel for getting permissions to redistribute the code ? I do not see how this is doing any good to the project, given that 1) there are alternatives (for 100Mbit quite a few of them), and some cards are even better and cheaper than the "fxp"; 2) even if you have hardware with an "fxp" on board, adding a second supported card is cheap and easy -- nothing like having to put in a second video card; Of course if you need support for this card in your own business, you do what you need (including NDA's etc), but that is a totally different story (and it appears to be a relatively straightforward and quick thing to do if you do not need to redistribute the source code). I think we all have better ways to use our time for FreeBSD than dealing with the legal department of some company. cheers luigi > > 1 - Give a select group of people the docs under NDA > > 2 - If there are any specific features Intel wants avoided, get them to > > identify > > them up front. > > 3 - Let them write a driver that uses whatever features that are useful, with > > header files that define the register bits etc that are reasonably related > > to the features used. > > 4 - Hand over the driver to intel for "final veto" with a pre-agreement in > > place so that if they do not respond in 30 days we can release it as-is. > > 5 - If they have specific features or register bit definitions that they want > > removed, then do so as long as it isn't going to hopelessly cripple the > > driver. If they want something removed that wasn't covered in the list at > > the start and is going to cause severe performance problems (say a 10% > > performance or efficiency drop), too bad. > > 6 - Repeat the loop for 'final veto' but with a week timeout instead of 30 > > days. > > > > Regarding step 5; if the information is already "out there" (other open > > source drivers, leaked onto the internet, etc) then it is fair game and we > > can use it. > > Step 4 is a lose. That will never fly because they don't have the interest > or bandwidth to review. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 10:20:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E43E37B718; Sat, 24 Mar 2001 10:20:38 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA24876; Sat, 24 Mar 2001 10:20:36 -0800 Date: Sat, 24 Mar 2001 10:20:31 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Luigi Rizzo Cc: Peter Wemm , Mike Smith , scanner@jurai.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: <200103241731.SAA49447@info.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Mar 2001, Luigi Rizzo wrote: > I have read the thread for a while, and i wonder: > > why in the world someone should go through the effort and > responsibility of SIGNING THE NDA _and_ negotiating with Intel > for getting permissions to redistribute the code ? Because NDAs come as a blanket cover, and you can then negotiate exceptions to them. > > I do not see how this is doing any good to the project, given that > 1) there are alternatives (for 100Mbit quite a few of them), and some > cards are even better and cheaper than the "fxp"; > 2) even if you have hardware with an "fxp" on board, adding a second > supported card is cheap and easy -- nothing like having to put > in a second video card; It's not about 100Mbit. Personally, I prefer the tulip chip. It's about Intel's 10/100/1000 Pro1000T. > > Of course if you need support for this card in your own business, > you do what you need (including NDA's etc), but that is a totally > different story (and it appears to be a relatively straightforward > and quick thing to do if you do not need to redistribute the source > code). > > I think we all have better ways to use our time for FreeBSD than > dealing with the legal department of some company. > Well- sure. some of us are required by various contractual obligations to our clients to attempt to support this stuff, against Intel's resistance I might add. Therefore, we're trying to encourage Intel to do the right thing. And this might also include encouraging the buyback into open source of the chipset because we happen to believe that this is in the mutual best interest of the FreeBSD project and the vendor. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 10:23:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id F249E37B71B for ; Sat, 24 Mar 2001 10:23:21 -0800 (PST) (envelope-from rh@matriplex.com) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id KAA13424; Sat, 24 Mar 2001 10:23:07 -0800 (PST) (envelope-from rh@matriplex.com) Date: Sat, 24 Mar 2001 10:23:07 -0800 (PST) From: Richard Hodges To: Luigi Rizzo Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: <200103241731.SAA49447@info.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Mar 2001, Luigi Rizzo wrote: > I have read the thread for a while, and i wonder: > > why in the world someone should go through the effort and > responsibility of SIGNING THE NDA _and_ negotiating with Intel > for getting permissions to redistribute the code ? > > I do not see how this is doing any good to the project, given that > 1) there are alternatives (for 100Mbit quite a few of them), and some > cards are even better and cheaper than the "fxp"; Cheaper is of little importance to me (although I would grumble if the price went much over $100). But "better"? Please continue! I am very interested in your insights on alternatives. > 2) even if you have hardware with an "fxp" on board, adding a second > supported card is cheap and easy -- nothing like having to put > in a second video card; For many (most?) people that may be practical. But what about those of us with a 1RU system using fxp on the motherboard and NEED the single PCI slot for something else? I suspect that there are more of us than you might think. All the best, -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. Product Manager | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 10:32:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id B6CC937B719; Sat, 24 Mar 2001 10:32:11 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2OIVNb05212; Sat, 24 Mar 2001 10:31:23 -0800 (PST) (envelope-from dillon) Date: Sat, 24 Mar 2001 10:31:23 -0800 (PST) From: Matt Dillon Message-Id: <200103241831.f2OIVNb05212@earth.backplane.com> To: Dag-Erling Smorgrav Cc: Alfred Perlstein , "Michael C . Wu" , Rik van Riel , Peter Wemm , izero@ms26.hinet.net, cross@math.psu.edu, grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded s cerver References: <200103211114.f2LBE0h57371@mobile.wemm.org> <20010321120620.A932@peorth.iteration.net> <200103211817.f2LIHR416007@earth.backplane.com> <20010321102836.N12319@fw.wintelcom.net> <200103211907.f2LJ7cp17933@earth.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matt Dillon writes: :> So you would be able to create approximately four 17GB swap partitions. :> If you reduce NSWAP to 2 you would be able to create approximately :> two 34GB swap partitions. If you reduce NSWAP to 1 you would be able :> to create approximately one 68GB swap partition. : :"approximately one"? :) : :DES :-- :Dag-Erling Smorgrav - des@ofug.org Well, before Tor's patch you could create more, but then the machine would get angry at you and crash. Now you can try to create more and the machine will only admonish you for being silly, and then ignore the request. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 10:33:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 0790537B719; Sat, 24 Mar 2001 10:33:24 -0800 (PST) (envelope-from scanner@jurai.net) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id NAA11303; Sat, 24 Mar 2001 13:33:15 -0500 (EST) Date: Sat, 24 Mar 2001 13:33:15 -0500 (EST) From: To: Luigi Rizzo Cc: mjacob@feral.com, Peter Wemm , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: <200103241731.SAA49447@info.iet.unipi.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Mar 2001, Luigi Rizzo wrote: > I have read the thread for a while, and i wonder: > > why in the world someone should go through the effort and > responsibility of SIGNING THE NDA _and_ negotiating with Intel > for getting permissions to redistribute the code ? I made the effort to try and work things out for users like dennis. Who constantly have problems with Intel changing their PHY's, and our driver not getting updated. Because Intel wont give doc's out without an NDA. Now that should tell people like dennis, that our developers are *not interested* in writing binary only drivers, and/or signing NDA's. And I agree if a company needs the support let them sign the NDA and have the thing done in-house. I made the effort as im usre many others here have to beat Intel with a clue bat. They simply are not interested in playing nice. And AFAIC we can drop Intel support right now and whack the driver from the tree. I could care less about Intel CPU's or NIC HW. I have choices. And there are far better choices then Intel. Not that dropping the driver will happen. But my guess is the driver will eventually just suffer from so much bit rot that it will get yanked. I can be just as fascist as Intel. I could say we should just make a statement and rip the driver now. Make a nice article on daemon news and/or slashdot co-authored by the Linux Intel nic maintainer and just publicaly say both OS's are dropping support for Intel until such time as Intel does away with NDA's on their HW. The people who develop for FreeBSD, and I'm sure Linux as well, as you noted do not have the time to screw around with legal dept's in companies. They have work to do, and code to write. I, among many im sure, made the effort to get Intel to get a friggin clue. And as others have said before it's a practice in futility. So I made the effort. Intel is aware of what crack heads their being. End of story. Sorry dennis but if I were you I would start using other brands of NIC's. ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tomorrow?" BSD: "Are you guys coming or what?" ============================================================================= irc.openprojects.net #FreeBSD -Join the revolution! ICQ: 20016186 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 10:44:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 8816B37B719 for ; Sat, 24 Mar 2001 10:44:50 -0800 (PST) (envelope-from scanner@jurai.net) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id NAA11494; Sat, 24 Mar 2001 13:44:42 -0500 (EST) Date: Sat, 24 Mar 2001 13:44:42 -0500 (EST) From: To: Richard Hodges Cc: Luigi Rizzo , freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Mar 2001, Richard Hodges wrote: > For many (most?) people that may be practical. But what about > those of us with a 1RU system using fxp on the motherboard and > NEED the single PCI slot for something else? I suspect that > there are more of us than you might think. Richard, Well then I suggest you ALL start writing Intel every single day to RELEASE DOCS WITH NO NDA. Then this problem will go away. Matt had the best Idea so far. To take an NDA manual and get Intel to release the basic functinoality parts of it openly. And that is what I sent to Linda Sanchez at Intel. She said she would take it to the metting with some people. And let me know of any updates. So I am pretty much not holding my breath. I don't even use Intel HW. So I made the effort on behalf of people like dennis. Said effort has been made, life moves on. AFAIK the XL driver for 3com card's performs just as well if not better then the intel cards. And gee funny enough the new dual AMD Athlon board from Tyan will sport onboard 3Com 10/100 FE. What an amazing coincedence. You now no longer need Intel CPU's, and now you no longer need the fxp driver. You have choices. If you choose not to use them... We can't FORCE Intel to do anything. And as long as they dont want us to write open source drivers for their hardware we won't. I'm just totally baffled at Intel's stance. And as usual I am quick to get angry over such petty stupid things. Which is why I don't work in PR :-) ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tomorrow?" BSD: "Are you guys coming or what?" ============================================================================= irc.openprojects.net #FreeBSD -Join the revolution! ICQ: 20016186 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 11:14: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 8EA6137B719; Sat, 24 Mar 2001 11:13:58 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f2OJDW008855; Sat, 24 Mar 2001 11:13:32 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: phk@critter.freebsd.dk Cc: rwatson@FreeBSD.ORG, kris@obsecurity.org, hackers@FreeBSD.ORG Subject: Re: so where is our press-release about MacOS X ? In-Reply-To: <17532.985445640@critter> References: <17532.985445640@critter> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010324111332F.jkh@osd.bsdi.com> Date: Sat, 24 Mar 2001 11:13:32 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 38 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think you can assume that Jordan will veto me writing anything even > remotely like a press-release for the project. I just thought it was > a very good opportunity to beat the drum... I don't think you can assume any such thing - I say go for it! :) One of the things that makes the Linux community as powerful as it is is the fact that so many people are involved in the advocacy side of things. They even have people reading their mailing lists and posting distillations of all the high points to various web sites. We like to talk about doing those sorts of things, but they have the manpower (personpower?) to actually do them. I may be the PR guy, but that just means that the buck generally stops with me when nobody else can be found to attend some press or technical round-table event and I'm always keen to have the PR baton taken up by others, when possible, since I obviously can't be in all places at once. I believe phk himself has done multiple european events now which I couldn't possibly have done, even if I had wanted to fly 12 hours over the atlantic to do a 2 hour presentation. :) To cite a very recent example, just last thursday there was a "Wells Fargo Linux Day" event which I sent Murray off to since I couldn't make it. By all accounts, he did a great job at presenting the FreeBSD side of the story and I'm just glad I could facilitate someone being there at all. That's really the essence of the PR hat, not just sitting at a desk and "vetoing" PR one doesn't like. Heck, I don't think I've ever done that, the most I generally get involved in other people's PR is to make suggestions or edit the drafts they send me. If you guys go near the Apple thing, however, I can at least note that it would be courteous to work with Ernie P. since he's the PR liason on that side and has worked with us in the past on things like this. Your message will be far more powerful with him on your side than without and he's also a pretty good wordsmith who can undoutedly help you polish the PR before sending it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 11:31:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 2A0FD37B718; Sat, 24 Mar 2001 11:31:40 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id OAA04967; Sat, 24 Mar 2001 14:32:31 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 24 Mar 2001 14:49:14 -0500 To: From: Dennis Subject: Re: Intel driver doc's Take 2. Cc: mjacob@feral.com, Peter Wemm , Mike Smith , freebsd-hackers@FreeBSD.ORG In-Reply-To: References: <200103241731.SAA49447@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:33 PM 03/24/2001, scanner@jurai.net wrote: >On Sat, 24 Mar 2001, Luigi Rizzo wrote: > > > I have read the thread for a while, and i wonder: > > > > why in the world someone should go through the effort and > > responsibility of SIGNING THE NDA _and_ negotiating with Intel > > for getting permissions to redistribute the code ? > > > > I made the effort to try and work things out for users like >dennis. Who constantly have problems with Intel changing their PHY's, and >our driver not getting updated. Because Intel wont give doc's out without >an NDA. Now that should tell people like dennis, that our developers are >*not interested* in writing binary only drivers, and/or signing NDA's. You use the term "our developers" as if you are some sort of closed cult. I have NEVER complained about Intel not releasing full information on their boards.That whining has come exclusively from hackers that didnt feel like doing the work. I complained about FreeBSD having a "maintainer" for a very important driver who didnt do any maintaining. I fixed the persistent PHY problem in an afternoon with info from the available linux driver supplied by intel. You dont need to get intel to change its policy to support the board. Its just an excuse to not do it. There are plenty of resources available. If the if_wx driver sucks, why not fix it rather than trying to coerce a mega-companies with a deep political structure to change is policies? But if youre not going to maintain it, dont do it at all. You cant stick it to users by deciding later that you dont want to support it anymore. I complained for days and then fixed the fxp driver in about 4 hours. Maybe its time to do work and complain less. dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 11:34:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.matriplex.com (ns1.matriplex.com [208.131.42.8]) by hub.freebsd.org (Postfix) with ESMTP id 729FD37B719 for ; Sat, 24 Mar 2001 11:34:34 -0800 (PST) (envelope-from rh@matriplex.com) Received: from mail.matriplex.com (mail.matriplex.com [208.131.42.9]) by mail.matriplex.com (8.9.2/8.9.2) with ESMTP id LAA13550; Sat, 24 Mar 2001 11:34:29 -0800 (PST) (envelope-from rh@matriplex.com) Date: Sat, 24 Mar 2001 11:34:29 -0800 (PST) From: Richard Hodges To: scanner@jurai.net Cc: Luigi Rizzo , freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Mar 2001 scanner@jurai.net wrote: > On Sat, 24 Mar 2001, Richard Hodges wrote: > > > For many (most?) people that may be practical. But what about > > those of us with a 1RU system using fxp on the motherboard and > > NEED the single PCI slot for something else? I suspect that > > there are more of us than you might think. > Richard, > > Well then I suggest you ALL start writing Intel every single day > to RELEASE DOCS WITH NO NDA. Then this problem will go away. That is probably the "right" thing to do, but like you, I'm not going to hold my breath. > AFAIK the XL driver for 3com card's performs just as well if not > better then the intel cards. And gee funny enough the new dual AMD > Athlon board from Tyan will sport onboard 3Com 10/100 FE. Thanks for the tip on the XL driver. Over the years, I have seen many questions about which driver/card was the best, and all the answers were pretty vague, or suggested that Intel had the edge. That's good news on the Tyan motherboard. The bad news is the price... About $950 :-( All the best, -Richard ------------------------------------------- Richard Hodges | Matriplex, inc. Product Manager | 769 Basque Way rh@matriplex.com | Carson City, NV 89706 775-886-6477 | www.matriplex.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 11:42:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nebula.cybercable.fr (d217.dhcp212-126.cybercable.fr [212.198.126.217]) by hub.freebsd.org (Postfix) with ESMTP id 10D8E37B719 for ; Sat, 24 Mar 2001 11:42:48 -0800 (PST) (envelope-from mux@qualys.com) Received: (from mux@localhost) by nebula.cybercable.fr (8.11.3/8.11.3) id f2OJgDw10761 for hackers@FreeBSD.org; Sat, 24 Mar 2001 20:42:13 +0100 (CET) (envelope-from mux) Date: Sat, 24 Mar 2001 20:42:12 +0100 From: Maxime Henrion To: hackers@FreeBSD.org Subject: Patch to disallow the build of modules Message-ID: <20010324204212.A777@nebula.cybercable.fr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, Here is a patch to select the modules you want and don't want. The patch is for /usr/src/sys/modules/Makefile from RELENG_4. Then you have to put variables in make.conf (i'm writing the patch for defaults/make.conf) like this : NO_KMOD_FPU=true NO_KMOD_GNUFPU=true ... Thanks for any review. Maxime -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code Key fingerprint = F9B6 1D5A 4963 331C 88FC CA6A AB50 1EF2 8CBE 99D6 Public Key : http://www.epita.fr/~henrio_m/ --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="Makefile.diff" --- /usr/src/sys/modules/Makefile Tue Mar 13 02:26:22 2001 +++ Makefile Sat Mar 24 20:35:54 2001 @@ -2,7 +2,7 @@ # XXX present but broken: ip_mroute_mod pcic -SUBDIR= accf_data accf_http agp aha amr an aue \ +_SUBDIR= accf_data accf_http agp aha amr an aue \ ccd cd9660 coda cue dc fdesc fxp if_disc if_ef if_ppp \ if_sl if_tap if_tun ip6fw ipfilter ipfw ispfw joy kernfs kue \ linux md mfs mii mlx msdos ncp pcn netgraph nfs ntfs nullfs \ @@ -12,16 +12,22 @@ # XXX some of these can move to the general case when de-i386'ed .if ${MACHINE_ARCH} == "i386" -SUBDIR+=aac asr bktr coff fpu gnufpu ibcs2 linprocfs mly ray splash streams \ +_SUBDIR+=aac asr bktr coff fpu gnufpu ibcs2 linprocfs mly ray splash streams \ svr4 vesa wi .endif .if ${MACHINE} == "pc98" -SUBDIR+=snc +_SUBDIR+=snc .endif .if ${MACHINE_ARCH} == "alpha" -SUBDIR+=osf1 +_SUBDIR+=osf1 .endif + +.for kmod in ${_SUBDIR} +.if !defined(NO_KMOD_${kmod:U}) +SUBDIR+=${kmod} +.endif +.endfor .include --Q68bSM7Ycu6FN28Q-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 11:43:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id C708F37B71A; Sat, 24 Mar 2001 11:43:28 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f2OJhQ320230; Sat, 24 Mar 2001 20:43:27 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Jordan Hubbard Cc: rwatson@FreeBSD.ORG, kris@obsecurity.org, hackers@FreeBSD.ORG Subject: Re: so where is our press-release about MacOS X ? In-Reply-To: Your message of "Sat, 24 Mar 2001 11:13:32 PST." <20010324111332F.jkh@osd.bsdi.com> Date: Sat, 24 Mar 2001 20:43:26 +0100 Message-ID: <20228.985463006@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010324111332F.jkh@osd.bsdi.com>, Jordan Hubbard writes: >> I think you can assume that Jordan will veto me writing anything even >> remotely like a press-release for the project. I just thought it was >> a very good opportunity to beat the drum... > >I don't think you can assume any such thing - I say go for it! :) Well, how soon we forget history :-) Anyway, I barely have time to read my email this weekend so I'm out of the loop... >One of the things that makes the Linux community as powerful as it is >is the fact that so many people are involved in the advocacy side of >things. Right, I fully agree. Chart me up in the "kernel architecture" category and lets find somebody else do the PR writing... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 11:44:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ohm.physics.purdue.edu (ohm.physics.purdue.edu [128.210.146.32]) by hub.freebsd.org (Postfix) with ESMTP id 0A35F37B719; Sat, 24 Mar 2001 11:44:32 -0800 (PST) (envelope-from will@physics.purdue.edu) Received: (from will@localhost) by ohm.physics.purdue.edu (8.11.2/8.9.3) id f2OJmj317257; Sat, 24 Mar 2001 14:48:45 -0500 (EST) (envelope-from will@physics.purdue.edu) X-Authentication-Warning: ohm.physics.purdue.edu: will set sender to will@physics.purdue.edu using -f Date: Sat, 24 Mar 2001 14:48:45 -0500 From: Will Andrews To: Dennis Cc: scanner@jurai.net, mjacob@feral.com, Peter Wemm , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. Message-ID: <20010324144844.K5821@ohm.physics.purdue.edu> Reply-To: Will Andrews References: <200103241731.SAA49447@info.iet.unipi.it> <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="3JWHCGIvlHPlU6rB" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com>; from dennis@etinc.com on Sat, Mar 24, 2001 at 02:49:14PM -0500 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --3JWHCGIvlHPlU6rB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 24, 2001 at 02:49:14PM -0500, Dennis wrote: > You use the term "our developers" as if you are some sort of closed cult. They have something in common, and it's not a cult. It's called being an "open source developer". > I have NEVER complained about Intel not releasing full information on=20 > their boards.That whining has come exclusively from hackers that didnt fe= el=20 > like doing the work. I complained about FreeBSD having a "maintainer" for= a=20 > very important driver who didnt do any maintaining. I fixed the persisten= t=20 > PHY problem in an afternoon with info from the available linux driver=20 > supplied by intel. You dont need to get intel to change its policy to=20 > support the board. Its just an excuse to not do it. There are plenty of= =20 > resources available. Not in terms of time. BSD developers prefer to spend their time on opensource code that's done the right way. Hence the quality of FreeBSD. I'm sure you knew that already, since you're supporting this in ETInc's products. > If the if_wx driver sucks, why not fix it rather than trying to coerce a= =20 > mega-companies with a deep political structure to change is policies? But= =20 > if youre not going to maintain it, dont do it at all. You cant stick it t= o=20 > users by deciding later that you dont want to support it anymore. You can't "fix" a device driver "correctly" when you don't have the right docs. > I complained for days and then fixed the fxp driver in about 4 hours. May= be=20 > its time to do work and complain less. Uh bro, if you have patches, submit them! That's what opensource is all about... of course you knew that too. :) --=20 wca --3JWHCGIvlHPlU6rB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6vPocF47idPgWcsURAowaAJ4+pmEWtgUjtUCxY62tKDdIIGFEQQCgkOwz lVsYXV7APMOgHaXVasmA7BQ= =sAgo -----END PGP SIGNATURE----- --3JWHCGIvlHPlU6rB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 11:45:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id E217337B718; Sat, 24 Mar 2001 11:45:28 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA18654; Sat, 24 Mar 2001 12:45:12 -0700 (MST) (envelope-from ken) Date: Sat, 24 Mar 2001 12:45:12 -0700 From: "Kenneth D. Merry" To: Dennis Cc: "Schmalzbauer, Harald" , hackers@FreeBSD.ORG, isp@FreeBSD.ORG Subject: Re: AW: Best Gigabit ethernet for 4.x Message-ID: <20010324124511.A18612@panzer.kdm.org> References: <5.0.0.25.0.20001118113245.032d3130@mail.etinc.com> <20001118150437.A15956@panzer.kdm.org> <5.0.0.25.0.20010324122812.038f4eb0@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <5.0.0.25.0.20010324122812.038f4eb0@mail.etinc.com>; from dennis@etinc.com on Sat, Mar 24, 2001 at 12:31:05PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 24, 2001 at 12:31:05 -0500, Dennis wrote: > At 05:04 PM 11/18/2000, Kenneth D. Merry wrote: > >On Sat, Nov 18, 2000 at 11:33:29 -0500, Dennis wrote: > > > At 04:28 PM 11/17/2000, Schmalzbauer, Harald wrote: > > > >I just heard that Intel doesn't supply documentation on ther chipset > > and the > > > >FreeBSD and Linux support is quiet bad. The Netgear GA620 is said to be > > > >twice as fast. The same Chipset (Alteon Tigon/AceNIC) is on the 3com985. > > > > > > > > > Are all of the cards supported that use this chipset? I read somewhere > > that > > > the netgear card has a smallish buffer, and that the alteon was a better > > > choice. How does the 3com card compare in that respect? > > > >The Netgear boards have 512K SRAM, the 3Com boards have 1MB SRAM. > > > >You can get Alteon-branded boards (with either 512K or 1MB SRAM), but > >generally only directly from Alteon, and you're going to pay more than you > >would for either the 3Com or Netgear boards. > > > >The 3Com and Netgear boards are identical to the Alteon boards. The only > >difference is they've got "Netgear" or "3Com" silk-screened on them, and > >the Alteon boards don't have any logos on them. > > > >FWIW, 3Com is buying Alteon's NIC group. Apparantly (according to an > >Alteon engineer who posted on the linux-acenic list) they're just buying > >the technology, not hiring the engineers: > > When you say "identical", that implies that they are the same...or do you > just mean that they use the same parts? It seems unlikely that alteon would > allow netgear to license its product and them sell it for 1/2 the price. Alteon evidently didn't want to undersell their OEMs. I think most of their NIC business was via sales from Netgear, 3Com, etc., and not via direct sales of their own NICs. (Which you could only buy direct from Alteon.) And the cards are pretty much the same, except that the Alteon boards generally have no identifying markings on them, whereas the Netgear and (I think) 3Com boards have the vendor's name silk-screened on the board. > Price is not an issue at this level as performance is tantamount, but Im > not sure you'd need more than 512M with unix unless you have several NICs > in a box. I'd like to see a Gigabit board with 512M. :) Assuming you mean 512K, you're probably right, that would be sufficient in many situations. The thing to remember is that you don't get the entire 512K for caching packets, since part of it (less than half) is used for the firmware and data structures. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 11:46: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 82BBC37B718 for ; Sat, 24 Mar 2001 11:45:59 -0800 (PST) (envelope-from scanner@jurai.net) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id OAA12451; Sat, 24 Mar 2001 14:45:54 -0500 (EST) Date: Sat, 24 Mar 2001 14:45:53 -0500 (EST) From: To: Richard Hodges Cc: Luigi Rizzo , freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Mar 2001, Richard Hodges wrote: > Thanks for the tip on the XL driver. Over the years, I have seen > many questions about which driver/card was the best, and all the > answers were pretty vague, or suggested that Intel had the edge. Yes. It's currently my understanding that the xl driver is indeed as reliable and as fast as the fxp. I know what your saying though. The fxp has been touted as the fastest. Years ago it was the de driver for DEC cards that was the screamer, then it became the fxp, but the xl driver is just as fast. > That's good news on the Tyan motherboard. The bad news is the price... > About $950 :-( Yeah when I saw that price I about had a stroke! My guess is it's going to be half that when it finally rolls out in april. AMD CPU's and AMD boards have *always* been cheaper then Intel parts. I really doubt Tyan is going to start breaking that now. Granted this is their first high end server board for K7's but Tyan always has faily decent prices on their MB's. I think that 950 is just an initial marketing price. But in relaity when it rolls out you will see it on pricewatch for half that. That's my guess. ============================================================================= -Chris Watson (316) 326-3862 | FreeBSD Consultant, FreeBSD Geek Work: scanner@jurai.net | Open Systems Inc., Wellington, Kansas Home: scanner@deceptively.shady.org | http://open-systems.net ============================================================================= WINDOWS: "Where do you want to go today?" LINUX: "Where do you want to go tomorrow?" BSD: "Are you guys coming or what?" ============================================================================= irc.openprojects.net #FreeBSD -Join the revolution! ICQ: 20016186 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 11:54:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id DA97E37B71B; Sat, 24 Mar 2001 11:54:23 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id OAA05100; Sat, 24 Mar 2001 14:55:12 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010324150424.03bc3900@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 24 Mar 2001 15:11:54 -0500 To: Will Andrews From: Dennis Subject: Re: Intel driver doc's Take 2. Cc: scanner@jurai.net, mjacob@feral.com, Peter Wemm , Mike Smith , freebsd-hackers@FreeBSD.ORG In-Reply-To: <20010324144844.K5821@ohm.physics.purdue.edu> References: <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> <200103241731.SAA49447@info.iet.unipi.it> <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If the if_wx driver sucks, why not fix it rather than trying to coerce a > > mega-companies with a deep political structure to change is policies? But > > if youre not going to maintain it, dont do it at all. You cant stick it to > > users by deciding later that you dont want to support it anymore. > >You can't "fix" a device driver "correctly" when you don't have the >right docs. Most drivers are written without full docs. Intel supplied drivers for linux are available for both eepro100 and gigabit cards. The info is out there. Cobbling together the info to produce a driver...THATS what open source is all about. > > I complained for days and then fixed the fxp driver in about 4 hours. > Maybe > > its time to do work and complain less. > >Uh bro, if you have patches, submit them! That's what opensource is all >about... of course you knew that too. Im not an "open-source" developer. but then again, you knew that. Plus I offered to help and J. Lemon bit off my head. Plus Im sure you wouldnt want Intels copyright in "your" driver. db To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 11:59:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 56A2A37B71B for ; Sat, 24 Mar 2001 11:59:24 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id PAA05136; Sat, 24 Mar 2001 15:00:21 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010324151516.03bc6d60@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 24 Mar 2001 15:17:03 -0500 To: , Richard Hodges From: Dennis Subject: Re: Intel driver doc's Take 2. Cc: Luigi Rizzo , freebsd-hackers@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:45 PM 03/24/2001, scanner@jurai.net wrote: >On Sat, 24 Mar 2001, Richard Hodges wrote: > > > Thanks for the tip on the XL driver. Over the years, I have seen > > many questions about which driver/card was the best, and all the > > answers were pretty vague, or suggested that Intel had the edge. > > Yes. It's currently my understanding that the xl driver is indeed >as reliable and as fast as the fxp. I know what your saying though. The >fxp has been touted as the fastest. Years ago it was the de driver for DEC >cards that was the screamer, then it became the fxp, but the xl driver is >just as fast. thats not true at all. We have traced many of our heavily loaded customers problems to the XL driver. Replacing them with intels solved the problems. But for general use you are probably correct. Db To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 12: 8:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ohm.physics.purdue.edu (ohm.physics.purdue.edu [128.210.146.32]) by hub.freebsd.org (Postfix) with ESMTP id EF1C137B718; Sat, 24 Mar 2001 12:08:18 -0800 (PST) (envelope-from will@physics.purdue.edu) Received: (from will@localhost) by ohm.physics.purdue.edu (8.11.2/8.9.3) id f2OKCbr17323; Sat, 24 Mar 2001 15:12:37 -0500 (EST) (envelope-from will@physics.purdue.edu) X-Authentication-Warning: ohm.physics.purdue.edu: will set sender to will@physics.purdue.edu using -f Date: Sat, 24 Mar 2001 15:12:37 -0500 From: Will Andrews To: Dennis Cc: Will Andrews , scanner@jurai.net, mjacob@feral.com, Peter Wemm , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. Message-ID: <20010324151237.L5821@ohm.physics.purdue.edu> Reply-To: Will Andrews References: <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> <200103241731.SAA49447@info.iet.unipi.it> <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> <20010324144844.K5821@ohm.physics.purdue.edu> <5.0.0.25.0.20010324150424.03bc3900@mail.etinc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="QQ3ZtGCb/+O9hLkL" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.0.25.0.20010324150424.03bc3900@mail.etinc.com>; from dennis@etinc.com on Sat, Mar 24, 2001 at 03:11:54PM -0500 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --QQ3ZtGCb/+O9hLkL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 24, 2001 at 03:11:54PM -0500, Dennis wrote: > Most drivers are written without full docs. Intel supplied drivers for=20 > linux are available for both eepro100 and gigabit cards. The info is out= =20 > there. Cobbling together the info to produce a driver...THATS what open= =20 > source is all about. [...] > Im not an "open-source" developer. but then again, you knew that. Plus I= =20 If you're not an opensource developer, then you don't know what yer talking about. Why do you even bother subscribing to any freebsd lists if you aren't going to adopt any sort of opensource behavior? --=20 wca --QQ3ZtGCb/+O9hLkL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6vP+1F47idPgWcsURAtQLAJ4y8GwCjNVb93USgtIsv+gDopH6IQCfRSn2 6QaqTU+hy1RgzkTNHsNCHxo= =qpEZ -----END PGP SIGNATURE----- --QQ3ZtGCb/+O9hLkL-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 12:55: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 6ADDF37B72D for ; Sat, 24 Mar 2001 12:54:59 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id PAA05277; Sat, 24 Mar 2001 15:56:01 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010324155127.03daa8a0@mail.etinc.com> X-Sender: dennis@mail.etinc.com X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 24 Mar 2001 16:12:34 -0500 To: Will Andrews From: Dennis Subject: Re: Intel driver doc's Take 2. Cc: hackers@freebsd.org In-Reply-To: <20010324151237.L5821@ohm.physics.purdue.edu> References: <5.0.0.25.0.20010324150424.03bc3900@mail.etinc.com> <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> <200103241731.SAA49447@info.iet.unipi.it> <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> <20010324144844.K5821@ohm.physics.purdue.edu> <5.0.0.25.0.20010324150424.03bc3900@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:12 PM 03/24/2001, Will Andrews wrote: >On Sat, Mar 24, 2001 at 03:11:54PM -0500, Dennis wrote: > > Most drivers are written without full docs. Intel supplied drivers for > > linux are available for both eepro100 and gigabit cards. The info is out > > there. Cobbling together the info to produce a driver...THATS what open > > source is all about. >[...] > > Im not an "open-source" developer. but then again, you knew that. Plus I > >If you're not an opensource developer, then you don't know what yer >talking about. Why do you even bother subscribing to any freebsd lists >if you aren't going to adopt any sort of opensource behavior? Is being an "open-source" developer now a necessary condition for being a "hacker" or "developer"? You academics crack me up. You have it completely backwards. Most open-source people dont know what they are talking about. This conversation about intel is like a bunch of women discussing what its like to be hit in the balls. its downright comical. They are in the business of making money. If you think they dont know the exact impact of releasing the information then you need to get out of your cubical a hell of a lot more. For your info, Bub, what makes the BSD license attractive is its usability by commercial vendors, so maybe you should go play in Linuxland because you are the one in the wrong camp, not me. the ability to take code, fix it and incorporate it into a product WITHOUT giving back source is the ENTIRE CONCEPT of the BSD license. And why does all of your email have that stupid attachment? Whats the matter, cant figure out how to use an open-source mailer? :-) DB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 13: 7:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 272D837B719 for ; Sat, 24 Mar 2001 13:07:53 -0800 (PST) (envelope-from dan@langille.org) Received: from wocker (dan@wocker.int.nz.freebsd.org [192.168.0.99]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f2OL7ff12730; Sun, 25 Mar 2001 09:07:42 +1200 (NZST) (envelope-from dan@langille.org) Message-Id: <200103242107.f2OL7ff12730@ns1.unixathome.org> From: "Dan Langille" Organization: novice in training To: Will Andrews , Dennis Date: Sun, 25 Mar 2001 09:07:41 +1200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Intel driver doc's Take 2. Reply-To: dan@langille.org Cc: hackers@FreeBSD.ORG In-reply-to: <5.0.0.25.0.20010324155127.03daa8a0@mail.etinc.com> References: <20010324151237.L5821@ohm.physics.purdue.edu> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24 Mar 2001, at 16:12, Dennis wrote: > And why does all of your email have that stupid attachment? Whats the > matter, cant figure out how to use an open-source mailer? :-) It's called a PGP signature. Could you two kids please take this pissing contest off -hackers? Thanks. -- Dan Langille pgpkey - finger dan@unixathome.org | http://unixathome.org/finger.php got any work? I'm looking for some. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 13:14:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ohm.physics.purdue.edu (ohm.physics.purdue.edu [128.210.146.32]) by hub.freebsd.org (Postfix) with ESMTP id C0C0B37B71B for ; Sat, 24 Mar 2001 13:14:43 -0800 (PST) (envelope-from will@physics.purdue.edu) Received: (from will@localhost) by ohm.physics.purdue.edu (8.11.2/8.9.3) id f2OLJ6S17443; Sat, 24 Mar 2001 16:19:06 -0500 (EST) (envelope-from will@physics.purdue.edu) X-Authentication-Warning: ohm.physics.purdue.edu: will set sender to will@physics.purdue.edu using -f Date: Sat, 24 Mar 2001 16:19:06 -0500 From: Will Andrews To: Dennis Cc: Will Andrews , hackers@freebsd.org Subject: Re: Intel driver doc's Take 2. Message-ID: <20010324161906.M5821@ohm.physics.purdue.edu> Reply-To: Will Andrews References: <5.0.0.25.0.20010324150424.03bc3900@mail.etinc.com> <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> <200103241731.SAA49447@info.iet.unipi.it> <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> <20010324144844.K5821@ohm.physics.purdue.edu> <5.0.0.25.0.20010324150424.03bc3900@mail.etinc.com> <20010324151237.L5821@ohm.physics.purdue.edu> <5.0.0.25.0.20010324155127.03daa8a0@mail.etinc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="hMSfLvDvQX5ATYp5" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.0.25.0.20010324155127.03daa8a0@mail.etinc.com>; from dennis@etinc.com on Sat, Mar 24, 2001 at 04:12:34PM -0500 X-Operating-System: FreeBSD 4.2-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --hMSfLvDvQX5ATYp5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Mar 24, 2001 at 04:12:34PM -0500, Dennis wrote: > For your info, Bub, what makes the BSD license attractive is its usabilit= y=20 > by commercial vendors, so maybe you should go play in Linuxland because= =20 > you are the one in the wrong camp, not me. the ability to take code, fix = it=20 > and incorporate it into a product WITHOUT giving back source is the ENTIR= E=20 > CONCEPT of the BSD license. Obviously so, but it serves no point to complain about an opensource driver's problem on an opensource list if you're going to fix it in your proprietary tree, say you did so, and not pass it on. Since nobody else gets to see your "fix", it won't solve a thing, for you or FreeBSD. > And why does all of your email have that stupid attachment? Whats the=20 > matter, cant figure out how to use an open-source mailer? :-) What's the matter, don't know how to use pgp? --=20 wca --hMSfLvDvQX5ATYp5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6vQ9KF47idPgWcsURApdiAJ49R3g7v4cPvKocXmkYVmFAOPFCZgCeIwzq 013ioDy4bFk7jV5dSwpgFLE= =D0WJ -----END PGP SIGNATURE----- --hMSfLvDvQX5ATYp5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 13:57:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 2265237B718 for ; Sat, 24 Mar 2001 13:57:08 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f2OLv2k06155; Sat, 24 Mar 2001 13:57:02 -0800 (PST) (envelope-from dillon) Date: Sat, 24 Mar 2001 13:57:02 -0800 (PST) From: Matt Dillon Message-Id: <200103242157.f2OLv2k06155@earth.backplane.com> To: freebsd-hackers@freebsd.org Subject: Patch to allow cvs diff to diff date ranges on a branch Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This patch allows cvs diff to diff a date range on a branch. e.g.: cvs -d /home/ncvs diff -j RELENG_4:2/15/01 -j RELENG_4:3/06/01 I'm not quite sure what to do with it yet... I suppose submit it to the cvs maintainers since its in contrib. The patch is fairly straightforward since cvs already has support for branch date ranges (for cvs update). -Matt Index: contrib/cvs/src/diff.c =================================================================== RCS file: /home/ncvs/src/contrib/cvs/src/diff.c,v retrieving revision 1.14 diff -u -r1.14 diff.c --- contrib/cvs/src/diff.c 1999/12/11 12:50:08 1.14 +++ contrib/cvs/src/diff.c 2001/03/24 21:51:13 @@ -50,6 +50,7 @@ static char *diff_rev1, *diff_rev2; /* Command line dates, from -D option. Malloc'd. */ static char *diff_date1, *diff_date2; +static char *diff_join1, *diff_join2; static char *use_rev1, *use_rev2; static int have_rev1_label, have_rev2_label; @@ -245,10 +246,12 @@ diff_rev2 = NULL; diff_date1 = NULL; diff_date2 = NULL; + diff_join1 = NULL; /* used for client/server only */ + diff_join2 = NULL; /* used for client/server only */ optind = 0; while ((c = getopt_long (argc, argv, - "+abcdefhilnpstuw0123456789BHNRC:D:F:I:L:U:V:W:k:r:", + "+abcdefhilnpstuw0123456789BHNRC:D:F:I:L:U:V:W:k:r:j:", longopts, &option_index)) != -1) { switch (c) @@ -308,6 +311,27 @@ free (options); options = RCS_check_kflag (optarg); break; + case 'j': + { + char *ptr; + char *cpy = strdup(optarg); + + if ((ptr = strchr(optarg, ':')) != NULL) + *ptr++ = 0; + if (diff_rev2 != NULL || diff_date2 != NULL) + error (1, 0, + "no more than two revisions/dates can be specified"); + if (diff_rev1 != NULL || diff_date1 != NULL) { + diff_join2 = cpy; + diff_rev2 = optarg; + diff_date2 = ptr ? Make_Date(ptr) : NULL; + } else { + diff_join1 = cpy; + diff_rev1 = optarg; + diff_date1 = ptr ? Make_Date(ptr) : NULL; + } + } + break; case 'r': if (diff_rev2 != NULL || diff_date2 != NULL) error (1, 0, @@ -356,13 +380,18 @@ send_option_string (opts); if (options[0] != '\0') send_arg (options); - if (diff_rev1) + if (diff_join1) + option_with_arg ("-j", diff_join1); + else if (diff_rev1) option_with_arg ("-r", diff_rev1); - if (diff_date1) + else if (diff_date1) client_senddate (diff_date1); - if (diff_rev2) + + if (diff_join2) + option_with_arg ("-j", diff_join2); + else if (diff_rev2) option_with_arg ("-r", diff_rev2); - if (diff_date2) + else if (diff_date2) client_senddate (diff_date2); /* Send the current files unless diffing two revs from the archive */ @@ -375,28 +404,26 @@ send_to_server ("diff\012", 0); err = get_responses_and_close (); - free (options); - options = NULL; - return (err); - } + } else #endif - - if (diff_rev1 != NULL) - tag_check_valid (diff_rev1, argc, argv, local, 0, ""); - if (diff_rev2 != NULL) - tag_check_valid (diff_rev2, argc, argv, local, 0, ""); - - which = W_LOCAL; - if (diff_rev1 != NULL || diff_date1 != NULL) - which |= W_REPOS | W_ATTIC; - - wrap_setup (); - - /* start the recursion processor */ - err = start_recursion (diff_fileproc, diff_filesdoneproc, diff_dirproc, - diff_dirleaveproc, NULL, argc, argv, local, - which, 0, 1, (char *) NULL, 1); + { + if (diff_rev1 != NULL) + tag_check_valid (diff_rev1, argc, argv, local, 0, ""); + if (diff_rev2 != NULL) + tag_check_valid (diff_rev2, argc, argv, local, 0, ""); + + which = W_LOCAL; + if (diff_rev1 != NULL || diff_date1 != NULL) + which |= W_REPOS | W_ATTIC; + + wrap_setup (); + + /* start the recursion processor */ + err = start_recursion (diff_fileproc, diff_filesdoneproc, diff_dirproc, + diff_dirleaveproc, NULL, argc, argv, local, + which, 0, 1, (char *) NULL, 1); + } /* clean up */ free (options); options = NULL; @@ -405,6 +432,10 @@ free (diff_date1); if (diff_date2 != NULL) free (diff_date2); + if (diff_join1 != NULL) + free (diff_join1); + if (diff_join2 != NULL) + free (diff_join2); return (err); } @@ -452,7 +483,7 @@ int exists; exists = 0; - /* special handling for TAG_HEAD */ + /* special handling for TAG_HEAD XXX */ if (diff_rev1 && strcmp (diff_rev1, TAG_HEAD) == 0) { char *head = @@ -842,7 +873,7 @@ if (diff_rev1 || diff_date1) { - /* special handling for TAG_HEAD */ + /* special handling for TAG_HEAD XXX */ if (diff_rev1 && strcmp (diff_rev1, TAG_HEAD) == 0) use_rev1 = ((vers->vn_rcs == NULL || vers->srcfile == NULL) ? NULL @@ -857,7 +888,7 @@ } if (diff_rev2 || diff_date2) { - /* special handling for TAG_HEAD */ + /* special handling for TAG_HEAD XXX */ if (diff_rev2 && strcmp (diff_rev2, TAG_HEAD) == 0) use_rev2 = ((vers->vn_rcs == NULL || vers->srcfile == NULL) ? NULL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 14:15:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id 38DB737B718; Sat, 24 Mar 2001 14:15:40 -0800 (PST) (envelope-from dima@unixfreak.org) Received: from spike.unixfreak.org (spike [63.198.170.139]) by bazooka.unixfreak.org (Postfix) with ESMTP id A025A3E09; Sat, 24 Mar 2001 14:15:39 -0800 (PST) To: Gerald Pfeifer Cc: freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org Subject: Re: Displaying options for current NFS mounts In-Reply-To: ; from pfeifer@dbai.tuwien.ac.at on "Sat, 24 Mar 2001 09:17:12 +0100 (CET)" Date: Sat, 24 Mar 2001 14:15:39 -0800 From: Dima Dorfman Message-Id: <20010324221539.A025A3E09@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerald Pfeifer writes: > What I'd like to see is `mount -v' printing > > vexpert:/files5 on /.amd_mnt/vexpert/files5 (nfs: v3, udp) > ^^^^^^^^^^^^ > instead of > > vexpert:/files5 on /.amd_mnt/vexpert/files5 (nfs) > ^^^ > This kind of information is incredibly useful for debugging, yet I > haven't found ANY way to obtain it, let alone such a natural one. IIRC tcpdump can detect NFS3 vs. NFS2, but that's suboptimal. Implementing the above functionality in mount(8) isn't actually that hard. We would need to export the filesystem-specific _args structures (e.g., nfs_args, ffs_args) to the userland. If we do that, mount(8) will be able to display all kinds of interesting, filesystem-specific stuff (e.g., NFS version and transport, whether a mounted CDROM is using Joilet, etc.). I tried to export this stuff in struct statfs, but ran into a problem: I'd need the complete definitions of _args in , but I can't include, e.g., because the latter includes the former ()! The patch below kind of implements this functionality. I only export nfs_args (not _args), and I only modified mount(8) to print the NFS version, but printing the transport and others is simple from there. To work around the above problem, I pasted the struct nfs_args definition into mount.h. It is *horribly* ugly, but it does work. If some other people display intrest in this, and someone can suggest a less ugly way of getting the definitions of _args into mount.h (the only other way I can think of is to just move all of them from /.h to mount.h permamently), I'll implement this stuff in the other filesystems. Regards Dima Dorfman dima@unixfreak.org P.S. If you want to try the patch, you'll need to rebuild at least the kernel, libc, mount, mountd, and amd, since the size of struct statfs changes. I only did those, and it seems to work on my system. Index: sys/sys/mount.h =================================================================== RCS file: /st/src/FreeBSD/src/sys/sys/mount.h,v retrieving revision 1.102 diff -u -r1.102 mount.h --- sys/sys/mount.h 2001/03/01 20:59:59 1.102 +++ sys/sys/mount.h 2001/03/24 22:03:13 @@ -69,6 +69,44 @@ #define MNAMELEN 72 /* length of buffer for returned name */ #endif +/* XXXDD: from src/sys/nfs/nfs.h! fixme! */ +/* + * Arguments to mount NFS + */ +#ifndef NFS_ARGS_DEFINED +#define NFS_ARGS_DEFINED +#define NFS_ARGSVERSION 3 /* change when nfs_args changes */ +struct nfs_args { + int version; /* args structure version number */ + struct sockaddr *addr; /* file server address */ + int addrlen; /* length of address */ + int sotype; /* Socket type */ + int proto; /* and Protocol */ + u_char *fh; /* File handle to be mounted */ + int fhsize; /* Size, in bytes, of fh */ + int flags; /* flags */ + int wsize; /* write size in bytes */ + int rsize; /* read size in bytes */ + int readdirsize; /* readdir size in bytes */ + int timeo; /* initial timeout in .1 secs */ + int retrans; /* times to retry send */ + int maxgrouplist; /* Max. size of group list */ + int readahead; /* # of blocks to readahead */ + int leaseterm; /* Term (sec) of lease */ + int deadthresh; /* Retrans threshold */ + char *hostname; /* server's name */ + int acregmin; /* cache attrs for reg files min time */ + int acregmax; /* cache attrs for reg files max time */ + int acdirmin; /* cache attrs for dirs min time */ + int acdirmax; /* cache attrs for dirs max time */ +}; +#endif /* !NFS_ARGS_DEFINED */ + +/* filesystem-specific mount options */ +union mount_info { + struct nfs_args nfs; +}; + struct statfs { long f_spare2; /* placeholder */ long f_bsize; /* fundamental file system block size */ @@ -92,6 +130,7 @@ char f_mntfromname[MNAMELEN];/* mounted filesystem */ short f_spares2; /* unused spare */ long f_spare[2]; /* unused spare */ + union mount_info f_mtinfo; /* filesystem-specific mount info */ }; #ifdef _KERNEL Index: sys/nfs/nfs.h =================================================================== RCS file: /st/src/FreeBSD/src/sys/nfs/nfs.h,v retrieving revision 1.57 diff -u -r1.57 nfs.h --- sys/nfs/nfs.h 2001/02/18 13:30:19 1.57 +++ sys/nfs/nfs.h 2001/03/24 22:03:13 @@ -116,6 +116,8 @@ /* * Arguments to mount NFS */ +#ifndef NFS_ARGS_DEFINED +#define NFS_ARGS_DEFINED #define NFS_ARGSVERSION 3 /* change when nfs_args changes */ struct nfs_args { int version; /* args structure version number */ @@ -141,6 +143,7 @@ int acdirmin; /* cache attrs for dirs min time */ int acdirmax; /* cache attrs for dirs max time */ }; +#endif /* !NFS_ARGS_DEFINED */ /* * NFS mount option flags Index: sys/nfs/nfs_vfsops.c =================================================================== RCS file: /st/src/FreeBSD/src/sys/nfs/nfs_vfsops.c,v retrieving revision 1.94 diff -u -r1.94 nfs_vfsops.c --- sys/nfs/nfs_vfsops.c 2001/03/01 20:59:19 1.94 +++ sys/nfs/nfs_vfsops.c 2001/03/24 22:03:14 @@ -307,6 +307,9 @@ sbp->f_type = mp->mnt_vfc->vfc_typenum; bcopy(mp->mnt_stat.f_mntonname, sbp->f_mntonname, MNAMELEN); bcopy(mp->mnt_stat.f_mntfromname, sbp->f_mntfromname, MNAMELEN); + bcopy((caddr_t)&mp->mnt_stat.f_mtinfo.nfs, + (caddr_t)&sbp->f_mtinfo.nfs, + sizeof(mp->mnt_stat.f_mtinfo.nfs)); } nfsm_reqdone; vput(vp); @@ -892,6 +895,7 @@ bcopy((caddr_t)argp->fh, (caddr_t)nmp->nm_fh, argp->fhsize); bcopy(hst, mp->mnt_stat.f_mntfromname, MNAMELEN); bcopy(pth, mp->mnt_stat.f_mntonname, MNAMELEN); + bcopy(argp, &mp->mnt_stat.f_mtinfo.nfs, sizeof(*argp)); nmp->nm_nam = nam; /* Set up the sockets and per-host congestion */ nmp->nm_sotype = argp->sotype; Index: sbin/mount/mount.c =================================================================== RCS file: /st/src/FreeBSD/src/sbin/mount/mount.c,v retrieving revision 1.41 diff -u -r1.41 mount.c --- sbin/mount/mount.c 2000/11/22 17:54:56 1.41 +++ sbin/mount/mount.c 2001/03/24 22:03:14 @@ -50,6 +50,9 @@ #include #include +#include +#include + #include #include #include @@ -530,6 +533,20 @@ (void)printf(", reads: sync %ld async %ld", sfp->f_syncreads, sfp->f_asyncreads); } + + /* + * File-system specific options. + */ + if (strcmp(sfp->f_fstypename, "nfs") == 0) { + struct nfs_args *nfsa = &sfp->f_mtinfo.nfs; + + if (nfsa->version != NFS_ARGSVERSION) { + (void)printf("\n"); + errx(1, "nfs_args version mismatch"); + } + (void)printf(", %s", + (nfsa->flags & NFSMNT_NFSV3) ? "v3" : "v2"); + } (void)printf(")\n"); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 14:42:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 3596837B718; Sat, 24 Mar 2001 14:42:43 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f2OMgB009471; Sat, 24 Mar 2001 14:42:12 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: phk@critter.freebsd.dk Cc: rwatson@FreeBSD.ORG, kris@obsecurity.org, hackers@FreeBSD.ORG Subject: Re: so where is our press-release about MacOS X ? In-Reply-To: <20228.985463006@critter> References: <20010324111332F.jkh@osd.bsdi.com> <20228.985463006@critter> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010324144211I.jkh@osd.bsdi.com> Date: Sat, 24 Mar 2001 14:42:11 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 12 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I don't think you can assume any such thing - I say go for it! :) > > Well, how soon we forget history :-) I have no idea what this means. > Right, I fully agree. Chart me up in the "kernel architecture" category > and lets find somebody else do the PR writing... Right. Can we see a show of hands? :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 15: 9:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ajax1.sovam.com (ajax1.sovam.com [194.67.1.172]) by hub.freebsd.org (Postfix) with ESMTP id CDA1E37B71A for ; Sat, 24 Mar 2001 15:09:48 -0800 (PST) (envelope-from avn@any.ru) Received: from ts9-a240.dial.sovam.com ([195.239.70.240]:1059 "EHLO ts9-a240.dial.sovam.com" ident: "avn" whoson: "-unregistered-" smtp-auth: TLS-CIPHER: TLS-PEER: ) by ajax1.sovam.com with ESMTP id ; Sun, 25 Mar 2001 03:09:36 +0400 Date: Sun, 25 Mar 2001 03:12:58 +0400 (MSD) From: "Alexey V. Neyman" X-X-Sender: To: Subject: make release Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello there! I just read FAQ on making release and have one question. FAQ says I must be having full CVS source tree (or be able to access it via CVSROOT), but I'm behind modem connection. So I'm curious why it is not enough to have a cvsupped src-all/doc-all/ports-all collections? And is there a way to avoid loading CVS tree for making release and generate it from these collections? # Alexey PS. The goal is to make a CD with a 5.0 snapshot to install it at home (where I have no internet access) and keep it up-to-date by later burning cvsuppable collections on a CD-RW at work. -------------------------------------+------------------------------ "May the Sun and Water gently | mailto: avn@any.ru fall upon you!" (Supox, from SC2) | -------------------------------------+------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 15:21:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 08A9D37B71E for ; Sat, 24 Mar 2001 15:21:26 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2ONL0E05739; Sat, 24 Mar 2001 15:21:00 -0800 (PST) (envelope-from obrien) Date: Sat, 24 Mar 2001 15:21:00 -0800 From: "David O'Brien" To: Luigi Rizzo Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. Message-ID: <20010324152100.A5571@dragon.nuxi.com> Reply-To: freebsd-hackers@FreeBSD.ORG References: <200103241731.SAA49447@info.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200103241731.SAA49447@info.iet.unipi.it>; from luigi@info.iet.unipi.it on Sat, Mar 24, 2001 at 06:31:44PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 24, 2001 at 06:31:44PM +0100, Luigi Rizzo wrote: > 2) even if you have hardware with an "fxp" on board, adding a second > supported card is cheap and easy -- nothing like having to put > in a second video card; Many, many U1-form-factor systems have two fxp on-board NICs. No room to add third (and fourth) supported NIC. K THNX. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 16: 3:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id F210837B719; Sat, 24 Mar 2001 16:03:14 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from mobile.wemm.org (mobile.wemm.org [10.0.0.5]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f2P03Ep11236; Sat, 24 Mar 2001 16:03:14 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f2P03Dh03713; Sat, 24 Mar 2001 16:03:13 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200103250003.f2P03Dh03713@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: mjacob@feral.com Cc: Mike Smith , scanner@jurai.net, freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: Date: Sat, 24 Mar 2001 16:03:12 -0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Jacob wrote: > > 1 - Give a select group of people the docs under NDA > > 2 - If there are any specific features Intel wants avoided, get them to > > identify > > them up front. > > 3 - Let them write a driver that uses whatever features that are useful, wi th > > header files that define the register bits etc that are reasonably rela ted > > to the features used. > > 4 - Hand over the driver to intel for "final veto" with a pre-agreement in > > place so that if they do not respond in 30 days we can release it as-is . > > 5 - If they have specific features or register bit definitions that they wa nt > > removed, then do so as long as it isn't going to hopelessly cripple the > > driver. If they want something removed that wasn't covered in the list at > > the start and is going to cause severe performance problems (say a 10% > > performance or efficiency drop), too bad. > > 6 - Repeat the loop for 'final veto' but with a week timeout instead of 30 > > days. > > > > Regarding step 5; if the information is already "out there" (other open > > source drivers, leaked onto the internet, etc) then it is fair game and we > > can use it. > > Step 4 is a lose. That will never fly because they don't have the interest > or bandwidth to review. I know. That is why I stressed that it is critical that there is a timeout. If there is no timeout, then you get stuck in the situation that Jonathan Lemon is in with his driver. *getting* the timeout clause is the trick. If somebody can manage that, then we are set. Finding somebody with the right marketing/legal connections who can get this in writing and who is naive enough to think that their internal departments will spend the time is what requires luck and/or persistance. There is no point beginning this process unless you can get the procedure *in writing*. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 16:40:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id B9A0D37B719 for ; Sat, 24 Mar 2001 16:40:19 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id TAA06132; Sat, 24 Mar 2001 19:41:23 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010324194115.02732960@mail.etinc.com> X-Sender: dennis@mail.etinc.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 24 Mar 2001 19:58:00 -0500 To: Will Andrews From: Dennis Subject: Re: Intel driver doc's Take 2. Cc: hackers@FreeBSD.ORG In-Reply-To: <20010324161906.M5821@ohm.physics.purdue.edu> References: <5.0.0.25.0.20010324155127.03daa8a0@mail.etinc.com> <5.0.0.25.0.20010324150424.03bc3900@mail.etinc.com> <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> <200103241731.SAA49447@info.iet.unipi.it> <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> <20010324144844.K5821@ohm.physics.purdue.edu> <5.0.0.25.0.20010324150424.03bc3900@mail.etinc.com> <20010324151237.L5821@ohm.physics.purdue.edu> <5.0.0.25.0.20010324155127.03daa8a0@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:19 PM 03/24/2001, Will Andrews wrote: >On Sat, Mar 24, 2001 at 04:12:34PM -0500, Dennis wrote: > > For your info, Bub, what makes the BSD license attractive is its usability > > by commercial vendors, so maybe you should go play in Linuxland because > > you are the one in the wrong camp, not me. the ability to take code, > fix it > > and incorporate it into a product WITHOUT giving back source is the ENTIRE > > CONCEPT of the BSD license. > >Obviously so, but it serves no point to complain about an opensource >driver's problem on an opensource list if you're going to fix it in your >proprietary tree, say you did so, and not pass it on. Since nobody else >gets to see your "fix", it won't solve a thing, for you or FreeBSD. Its not a "proprietary tree". I dont have time to clean it up and submit patches. "hackers" doesnt imply "open-souce". This is a "general technical discussion" list, according to freebsd.org. db To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 16:42:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from et-gw.etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 2C47137B719 for ; Sat, 24 Mar 2001 16:42:15 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys.etinc.com (dbsys.etinc.com [207.252.1.18]) by et-gw.etinc.com (8.9.3/8.9.3) with ESMTP id TAA06140; Sat, 24 Mar 2001 19:43:16 GMT (envelope-from dennis@etinc.com) Message-Id: <5.0.0.25.0.20010324195831.02737a50@mail.etinc.com> X-Sender: dennis@mail.etinc.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 24 Mar 2001 19:59:54 -0500 To: dan@langille.org From: Dennis Subject: Re: Intel driver doc's Take 2. Cc: hackers@FreeBSD.ORG In-Reply-To: <200103242107.f2OL7ff12730@ns1.unixathome.org> References: <5.0.0.25.0.20010324155127.03daa8a0@mail.etinc.com> <20010324151237.L5821@ohm.physics.purdue.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:07 PM 03/24/2001, Dan Langille wrote: >On 24 Mar 2001, at 16:12, Dennis wrote: > > > And why does all of your email have that stupid attachment? Whats the > > matter, cant figure out how to use an open-source mailer? :-) > >It's called a PGP signature. > >Could you two kids please take this pissing contest off -hackers? Thanks. the only thing more annoying the 2 people having a discussion is a third person telling them to stop. Feel free not to read any more messages in this thread. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 16:43:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CD7C237B71B for ; Sat, 24 Mar 2001 16:43:44 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA25786; Sat, 24 Mar 2001 16:43:42 -0800 Date: Sat, 24 Mar 2001 16:43:36 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Dennis Cc: dan@langille.org, hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. In-Reply-To: <5.0.0.25.0.20010324195831.02737a50@mail.etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I agree. We should delete the rest of this thread. On Sat, 24 Mar 2001, Dennis wrote: > At 04:07 PM 03/24/2001, Dan Langille wrote: > >On 24 Mar 2001, at 16:12, Dennis wrote: > > > > > And why does all of your email have that stupid attachment? Whats the > > > matter, cant figure out how to use an open-source mailer? :-) > > > >It's called a PGP signature. > > > >Could you two kids please take this pissing contest off -hackers? Thanks. > > the only thing more annoying the 2 people having a discussion is a third > person telling them to stop. Feel free not to read any more messages in > this thread. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 16:47:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 8C31A37B719 for ; Sat, 24 Mar 2001 16:47:33 -0800 (PST) (envelope-from dan@langille.org) Received: from wocker (dan@wocker.int.nz.freebsd.org [192.168.0.99]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f2P0lRf13867; Sun, 25 Mar 2001 12:47:28 +1200 (NZST) (envelope-from dan@langille.org) Message-Id: <200103250047.f2P0lRf13867@ns1.unixathome.org> From: "Dan Langille" Organization: novice in training To: Dennis Date: Sun, 25 Mar 2001 12:47:25 +1200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Intel driver doc's Take 2. Reply-To: dan@langille.org Cc: hackers@FreeBSD.ORG In-reply-to: <5.0.0.25.0.20010324195831.02737a50@mail.etinc.com> References: <200103242107.f2OL7ff12730@ns1.unixathome.org> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24 Mar 2001, at 19:59, Dennis wrote: > the only thing more annoying the 2 people having a discussion is a third > person telling them to stop. Feel free not to read any more messages in > this thread. Feel free to read the list charter. You two are in a pissing contest unreleated to this list. Please take it elsewhere. -- Dan Langille pgpkey - finger dan@unixathome.org | http://unixathome.org/finger.php got any work? I'm looking for some. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 17:43: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dell.dannyland.org (dell.dannyland.org [64.81.36.13]) by hub.freebsd.org (Postfix) with ESMTP id 3B52C37B718; Sat, 24 Mar 2001 17:43:05 -0800 (PST) (envelope-from dannyman@toldme.com) Received: by dell.dannyland.org (Postfix, from userid 1001) id 576BC5C3D; Sat, 24 Mar 2001 17:43:14 -0800 (PST) Date: Sat, 24 Mar 2001 17:43:14 -0800 From: dannyman To: Matt Dillon Cc: "Michael C . Wu" , Alfred Perlstein , grog@FreeBSD.ORG, fs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: tuning a VERY heavily (30.0) loaded server Message-ID: <20010324174314.B38361@dell.dannyland.org> References: <20010320111144.A51924@peorth.iteration.net> <20010320092717.R29888@fw.wintelcom.net> <20010320113818.B52586@peorth.iteration.net> <200103201750.f2KHopk94248@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200103201750.f2KHopk94248@earth.backplane.com>; from dillon@earth.backplane.com on Tue, Mar 20, 2001 at 09:50:51AM -0800 X-Loop: djhoward@uiuc.edu X-URL: http://www.dannyland.org/~dannyman/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Mar 20, 2001 at 09:50:51AM -0800, Matt Dillon wrote: > One thing that comes to mind is that you can smarthost your outgoing > email to another host so the queues don't build up. This should > greatly reduce mail load. In fact, I would recommend offloading email > entirely if possible... email always hits disks hard. > > Definitely get rid of MFS. MFS wastes 2x the memory allocated to it. > Use a softupdates-enabled filesystem in place of MFS, or use a > swap-backed VN-based partition with softupdates enabled. > > Alfred's vmiodirenable suggestion is a good one. [...] This might make a tiny help: mount things -noatime? If you are reading the same files over and over and over again you needn't bother WRITEing an atime ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 18:11:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id ED08637B718 for ; Sat, 24 Mar 2001 18:11:47 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.3/8.11.1) id f2P2BdI07901; Sat, 24 Mar 2001 18:11:39 -0800 (PST) (envelope-from obrien) Date: Sat, 24 Mar 2001 18:11:39 -0800 From: "David O'Brien" To: Dennis Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Intel driver doc's Take 2. Message-ID: <20010324181139.B5571@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> <200103241731.SAA49447@info.iet.unipi.it> <5.0.0.25.0.20010324142928.03a8b9d0@mail.etinc.com> <20010324144844.K5821@ohm.physics.purdue.edu> <5.0.0.25.0.20010324150424.03bc3900@mail.etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.0.25.0.20010324150424.03bc3900@mail.etinc.com>; from dennis@etinc.com on Sat, Mar 24, 2001 at 03:11:54PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Mar 24, 2001 at 03:11:54PM -0500, Dennis wrote: > Most drivers are written without full docs. Feh. *EVERY* wpaul written Ethernet driver was written _with_ having the full docs. wpaul will not write a driver otherwise. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 18:36:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 9947837B719; Sat, 24 Mar 2001 18:36:30 -0800 (PST) (envelope-from bp@butya.kz) Received: by relay.butya.kz (Postfix, from userid 1000) id 57E2928E25; Sun, 25 Mar 2001 09:36:21 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 447962866F; Sun, 25 Mar 2001 09:36:21 +0700 (ALMST) Date: Sun, 25 Mar 2001 09:36:21 +0700 (ALMST) From: Boris Popov To: Dima Dorfman Cc: Gerald Pfeifer , freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org Subject: Re: Displaying options for current NFS mounts In-Reply-To: <20010324221539.A025A3E09@bazooka.unixfreak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Mar 2001, Dima Dorfman wrote: > Implementing the above functionality in mount(8) isn't actually that > hard. We would need to export the filesystem-specific _args > structures (e.g., nfs_args, ffs_args) to the userland. If we do that, > mount(8) will be able to display all kinds of interesting, > filesystem-specific stuff (e.g., NFS version and transport, whether a > mounted CDROM is using Joilet, etc.). This probably a step in the wrong direction. In this way mount(8) should be aware about all types of filesystems and their flags/options/etc. May be fs (kernel part) can report these options as string to the given userland buffer ? It is not necessary to use existing statfs struct - now we have a very flexible VOP_GETEXTATTR() with corresponding syscall. > If some other people display intrest in this, and someone can suggest > a less ugly way of getting the definitions of _args into mount.h > (the only other way I can think of is to just move all of them from > /.h to mount.h permamently), I'll implement this stuff in the > other filesystems. Think about third party filesystems :) -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 19:50:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail-100baset.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 0660637B719; Sat, 24 Mar 2001 19:50:31 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id WAA23168; Sat, 24 Mar 2001 22:50:30 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <14301.985419390@critter> References: <14301.985419390@critter> Date: Sat, 24 Mar 2001 22:50:29 -0500 To: Poul-Henning Kamp , hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: so where is our press-release about MacOS X ? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:36 AM +0100 3/24/01, Poul-Henning Kamp wrote: >Shouldn't the FreeBSD project issue a press release welcoming >Apple's MacOS X ? For what it's worth, the Red Herring article on MacOS 10, at: http://www.redherring.com/index.asp?layout=story&channel=20000002&doc_id=1380018338 Mentions that: The core of the new OS is based on an open-source version of Unix called FreeBSD. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 20:19:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id EA35737B719; Sat, 24 Mar 2001 20:19:32 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id OAA14767; Sun, 25 Mar 2001 14:19:19 +1000 Date: Sun, 25 Mar 2001 14:18:43 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Dima Dorfman Cc: Gerald Pfeifer , freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: Displaying options for current NFS mounts In-Reply-To: <20010324221539.A025A3E09@bazooka.unixfreak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Mar 2001, Dima Dorfman wrote: > I tried to export this stuff in struct statfs, but ran into a problem: > I'd need the complete definitions of _args in , but I > can't include, e.g., because the latter includes the > former ()! mount.h used to know too much about all sorts of filesystems, but this was fixed in 4.4BSD. It is impossible for mount.h or mount(8) to know about all file systems, since filesystems can be dynamically loaded, and ugly for it to know about more than 1 (or 0 -- ffs is too special). > The patch below kind of implements this functionality. I only export > nfs_args (not _args), and I only modified mount(8) to print > the NFS version, but printing the transport and others is simple from > there. To work around the above problem, I pasted the struct nfs_args > definition into mount.h. It is *horribly* ugly, but it does work. Only mount_foofs can reasonably know about the options for foofs. perhaps mount(8) could fork-exec mount_foofs(8) to print options for foofs. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 21:17: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from idiom.com (idiom.com [216.240.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 57C8837B719 for ; Sat, 24 Mar 2001 21:16:56 -0800 (PST) (envelope-from rdm@cfcl.com) Received: from cfcl.com (cpe-24-221-169-54.ca.sprintbbd.net [24.221.169.54]) by idiom.com (8.9.3/8.9.3) with ESMTP id VAA85026 for ; Sat, 24 Mar 2001 21:16:55 -0800 (PST) Received: from [192.168.168.205] (cerberus [192.168.168.205]) by cfcl.com (8.11.1/8.11.1) with ESMTP id f2P5I6V41150 for ; Sat, 24 Mar 2001 21:18:06 -0800 (PST) (envelope-from rdm@cfcl.com) Mime-Version: 1.0 Message-Id: In-Reply-To: <20010324144211I.jkh@osd.bsdi.com> References: <20010324111332F.jkh@osd.bsdi.com> <20228.985463006@critter> <20010324144211I.jkh@osd.bsdi.com> Date: Sat, 24 Mar 2001 21:07:05 -0800 To: freebsd-hackers@freebsd.org From: Rich Morin Subject: Re: so where is our press-release about MacOS X ? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As a part-time journalist, I receive a fair number of press releases. Most get tossed, unopened, in an effort to simplify my life. When I do open a release, it all too frequently contains news of some VP of paper clips who has gotten promoted to Senior VP of office supplies. I have considered writing a form letter to send back to these folks, but it has never seemed to be worth the trouble. In short, I'm not too keen on press releases. I do think some kinds of PR materials are worthwhile, however. For instance, if I am trying to write a column on a topic, it's great to have a clearly-written white paper that tells me more than I can put into the article (but enough that I don't say silly things in trying to boil the topic down for the reader). I tend to find these gems by means of a web search and may follow them up by contacting the author(s) and/or PR contacts that are listed therein. All of which leads me to believe that FreeBSD might benefit from a web-based collection of white papers and other press resources. I don't know who is going to write these, but pulling a few documents (or links to documents) together onto a page might be a good start. Another useful PR technique involves writing articles and getting them published. The press needs a continuous stream of articles to keep the ads from slamming together. If you have the ability to do an authoritative and readable article on a topic of interest, you'll have no problem getting it published! MacTech, for instance, likes to get technical pieces on Macintosh- related topics; what about a critique of the Mac OS X kernel (including sections on the I/O Kit and the Mach subsystem) by someone who actually understands what's different from vanilla FreeBSD? Or, at a slightly higher level, an article could discuss how Apple used pieces of NetBSD and FreeBSD, including their reasons for using which pieces where. Ideally, an engineer from Apple should write this piece, but they're unlikely to have the time. OTOH, getting an Apple engineer to review something should be quite possible. Before anyone asks whether I'm volunteering to write pieces of this sort, I'll state that I fully intend to write some Mac OS X material, but I may not be in a position to write certain pieces, simply because I don't have the necessary background. In any case, we need LOTS of articles and I can only write so much on any topic without starting to repeat myself. Getting back to the press release notion, I do have a suggestion. The "FreeBSD in the Press" page (http://www.freebsd.org/news/press.html) is a great starting point for a "press contacts" list. If someone in the FreeBSD community (and/or BSDi) wants to start feeding material to the press, consider contacting these authors and asking them how the FreeBSD Project can help them write more pieces! -r -- http://www.cfcl.com/rdm - home page, resume, etc. http://www.cfcl.com/Meta/md_fb.html - The FreeBSD Browser email: rdm@cfcl.com; phone: +1 650-873-7841 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 22:18: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail15.sdc1.sfba.home.com (femail15.sdc1.sfba.home.com [24.0.95.142]) by hub.freebsd.org (Postfix) with ESMTP id CE42237B719; Sat, 24 Mar 2001 22:18:01 -0800 (PST) (envelope-from RonDzierwa@home.com) Received: from home.com ([24.3.55.231]) by femail15.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010325061801.SKTK29538.femail15.sdc1.sfba.home.com@home.com>; Sat, 24 Mar 2001 22:18:01 -0800 Message-ID: <3ABD8CD3.204BB823@home.com> Date: Sun, 25 Mar 2001 01:14:43 -0500 From: Ron Dzierwa Organization: Innovative Engineering, Inc. X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-bugs@freebsd.org, freebsd-hackers@freebsd.org Subject: ata driver problems with CTX laptop Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a CTX EzBook 800 series on which I have used FreeBSD version 2.2.8 since that version was current. At the time I had to use some of the PAO stuff to get the pcmcia enet to work, but everything else seemed to work fine. I just bought a new disk, and figured i'd install 4.2. The ata driver does not seem to live happily with the disk controller, however. and even the floppy driver seems to be having a problem (fdc0: cannot reserve I/O port range). The ata driver says: atapci0: port 0xfcf0-0xfcff,0x374-0x377,0x170-0x177 ,0x2f4-0x3f7,0x1f0-0x1f7 at device 18.1 on pci0 atapci0: Busmastering DMA not supported ata2: at 0x1f0 on atapci0 ata2: unable to allocate interrupt device_probe_and_attach: ata2 attach returned 6 ata3: at 0x170 on atapci0 ata3: unable to allocate interrupt device_probe_and_attach: ata3 attach returned 6 later on, when the sysinstall menu comes up and i try to allocate disk space it naturally tells me that there are no disks. the old kernel wd driver used to say: wdc0: at 0x1f0-0x1f7 irq 14 on isa wd0: 3102MB 96354432 sectors), 6304 cyls, 16 heads, 63 S/t, 512 B/s wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, ior I have tried enabling and disabling PNP in the bios, and using auto/user config for the disks. all combinations seem to yield the same results - it cant init the disk controllers. Why does it think it has ata2 and 3 instead of 0 and 1 like the old wd driver did? I have another FreeBSD system that I use as a workstation. I used it to build a kernel for the boot flop that would stop in the fd driver ( while(1) i++; makes an effective stopper) so that I could see the ata driver messages. If anybody has any fixes or suggestions, I could implement them and test them without any problem. If anyone has any answers or ideas, please email me directly, since I haven't subscribed to all the mailling lists. thanks, ron. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 22:20:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ghs.ssd.k12.wa.us (locutus.ghs.ssd.k12.wa.us [216.186.55.25]) by hub.freebsd.org (Postfix) with ESMTP id 2E58B37B71A for ; Sat, 24 Mar 2001 22:20:09 -0800 (PST) (envelope-from protozoa@ghs.ssd.k12.wa.us) Received: from localhost (protozoa@localhost) by ghs.ssd.k12.wa.us (8.9.3/8.9.3) with ESMTP id WAA01650; Sat, 24 Mar 2001 22:19:45 -0800 (PST) (envelope-from protozoa@ghs.ssd.k12.wa.us) Date: Sat, 24 Mar 2001 22:19:44 -0800 (PST) From: Dan Feldman To: Rich Morin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: so where is our press-release about MacOS X ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FOR IMMEDIATE RELEASE - 1 Apr 2000 SEATTLE - The FreeBSD Project, Inc. officially welcomed today the introduction of Apple Computer's Mac OS X. The next-generation operating system uses the TCP/IP stack of an obsolete version of FreeBSD's flagship product, and is otherwise completely unrelated. Apple's embracement of open-source software stretches far beyond its shameless duplication of the FreeBSD networking subystem. The Cupertino-based corporation recently released the core of OS X, Darwin, under the moniker "Public Source," after refusing to comply with Open Source Foundation rules for using the Open Source trademark. OS X ships with such industry-standard sofware as the Z shell and the Apache Web server, although the company recently announced to not contribute to either product. FreeBSD welcomes Apple's new OS release, touting the systems' completely different APIs, kernel architectures, platform support and target market. The new version of Mac OS is but one of several operating systems with hardly any relationship to FreeBSD whatsoever, including TOPS-20, WindRiver, VMS and AmigaOS. Apple plans to further the non-partnership as well. "We intend to further dissociate ourselves from FreeBSD, Inc." said a company representative. "We'll finish developing our in-house version of ps before the end of Q3 2002." Resoources: * www.apple.com * www.freebsd.org * www.getreal.net :) - dan feldman student, garfield high school, seattle On Sat, 24 Mar 2001, Rich Morin wrote: > As a part-time journalist, I receive a fair number of press releases. > Most get tossed, unopened, in an effort to simplify my life. When I > do open a release, it all too frequently contains news of some VP of > paper clips who has gotten promoted to Senior VP of office supplies. > I have considered writing a form letter to send back to these folks, > but it has never seemed to be worth the trouble. In short, I'm not > too keen on press releases. > > I do think some kinds of PR materials are worthwhile, however. For > instance, if I am trying to write a column on a topic, it's great to > have a clearly-written white paper that tells me more than I can put > into the article (but enough that I don't say silly things in trying > to boil the topic down for the reader). I tend to find these gems > by means of a web search and may follow them up by contacting the > author(s) and/or PR contacts that are listed therein. > > All of which leads me to believe that FreeBSD might benefit from a > web-based collection of white papers and other press resources. I > don't know who is going to write these, but pulling a few documents > (or links to documents) together onto a page might be a good start. > > Another useful PR technique involves writing articles and getting > them published. The press needs a continuous stream of articles to > keep the ads from slamming together. If you have the ability to do > an authoritative and readable article on a topic of interest, you'll > have no problem getting it published! > > MacTech, for instance, likes to get technical pieces on Macintosh- > related topics; what about a critique of the Mac OS X kernel (including > sections on the I/O Kit and the Mach subsystem) by someone who actually > understands what's different from vanilla FreeBSD? > > Or, at a slightly higher level, an article could discuss how Apple used > pieces of NetBSD and FreeBSD, including their reasons for using which > pieces where. Ideally, an engineer from Apple should write this piece, > but they're unlikely to have the time. OTOH, getting an Apple engineer > to review something should be quite possible. > > Before anyone asks whether I'm volunteering to write pieces of this sort, > I'll state that I fully intend to write some Mac OS X material, but I > may not be in a position to write certain pieces, simply because I don't > have the necessary background. In any case, we need LOTS of articles and > I can only write so much on any topic without starting to repeat myself. > > Getting back to the press release notion, I do have a suggestion. The > "FreeBSD in the Press" page (http://www.freebsd.org/news/press.html) is > a great starting point for a "press contacts" list. If someone in the > FreeBSD community (and/or BSDi) wants to start feeding material to the > press, consider contacting these authors and asking them how the FreeBSD > Project can help them write more pieces! > > -r > -- > http://www.cfcl.com/rdm - home page, resume, etc. > http://www.cfcl.com/Meta/md_fb.html - The FreeBSD Browser > email: rdm@cfcl.com; phone: +1 650-873-7841 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 22:26:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guild.plethora.net (guild.plethora.net [205.166.146.8]) by hub.freebsd.org (Postfix) with ESMTP id CBEEA37B71B for ; Sat, 24 Mar 2001 22:26:33 -0800 (PST) (envelope-from seebs@guild.plethora.net) Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1]) by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f2P6Q7O13135; Sun, 25 Mar 2001 00:26:07 -0600 (CST) Message-Id: <200103250626.f2P6Q7O13135@guild.plethora.net> From: seebs@plethora.net (Peter Seebach) Reply-To: seebs@plethora.net (Peter Seebach) To: Dan Feldman Cc: Rich Morin , freebsd-hackers@freebsd.org Subject: Re: so where is our press-release about MacOS X ? In-reply-to: Your message of "Sat, 24 Mar 2001 22:19:44 PST." Date: Sun, 25 Mar 2001 00:26:07 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dan Feldman wr ites: >under the moniker "Public Source," after refusing to comply with Open >Source Foundation rules for using the Open Source trademark. OS X ships >with such industry-standard sofware as the Z shell and the Apache Web >server, although the company recently announced to not contribute to >either product. "announced intentions", I assume. >hardly any relationship to FreeBSD whatsoever, including TOPS-20, >WindRiver, VMS and AmigaOS. WindRiver is a company, I believe the OS is called "vxWorks". Anyway, while this is hilarious, I'd be inclined to argue for trying to work *with* them, rather than against them. No matter how hard or futile it seems. -s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Mar 24 23:18:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ghs.ssd.k12.wa.us (locutus.ghs.ssd.k12.wa.us [216.186.55.25]) by hub.freebsd.org (Postfix) with ESMTP id 877BD37B71A for ; Sat, 24 Mar 2001 23:18:41 -0800 (PST) (envelope-from protozoa@ghs.ssd.k12.wa.us) Received: from localhost (protozoa@localhost) by ghs.ssd.k12.wa.us (8.9.3/8.9.3) with ESMTP id XAA07868; Sat, 24 Mar 2001 23:18:30 -0800 (PST) (envelope-from protozoa@ghs.ssd.k12.wa.us) Date: Sat, 24 Mar 2001 23:18:30 -0800 (PST) From: Dan Feldman To: Peter Seebach Cc: Dan Feldman , Rich Morin , freebsd-hackers@FreeBSD.ORG Subject: Re: so where is our press-release about MacOS X ? In-Reply-To: <200103250626.f2P6Q7O13135@guild.plethora.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You're right, there's no need to pick fights. But I'm just pointing out that there's no reason FreeBSD should work particularly hard to create the appearance of an alliance with Apple, when all they've done is use the source of some kernel components and a number of utilities for a commercial product. After all, Microsoft is rumored to have done exactly the same thing at times and I have yet to see any press releases about a relationship with _them_. On the other hand, a little evangelism could really help FreeBSD right now. There could be more users, for one, although I doubt millions of former Mac users will switch regardless of the press. The BSDs don't rely on big companies to support them as much as Linux does, so I don't think convincing corporate managers to switch will really help the project. What FreeBSD could use is some kind of magic way to attract developers from the other Unices, but I don't see that coming. What would help FreeBSD the most? An on-time, complete and stable release of 5.0. When I have a bit more free time, I'm planning to fix a few easy PRs.... - dan feldman student, garfield high school, seattle On Sun, 25 Mar 2001, Peter Seebach wrote: > In message , Dan Feldman wr > ites: > >under the moniker "Public Source," after refusing to comply with Open > >Source Foundation rules for using the Open Source trademark. OS X ships > >with such industry-standard sofware as the Z shell and the Apache Web > >server, although the company recently announced to not contribute to > >either product. > > "announced intentions", I assume. > > >hardly any relationship to FreeBSD whatsoever, including TOPS-20, > >WindRiver, VMS and AmigaOS. > > WindRiver is a company, I believe the OS is called "vxWorks". > > Anyway, while this is hilarious, I'd be inclined to argue for trying to > work *with* them, rather than against them. No matter how hard or futile > it seems. > > -s > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message