NAV detected a virus in a document sent to you.
Rockwell Automation's installation of Norton Antivirus for Notes has detected a virus in a message sent to you by [EMAIL PROTECTED] with a subject of Re: Here is that sample. The author has been notified of the situation. If the message was quarantined, it is because our server's antivirus software was unable to repair the infected document, and the sender will need to repair it and resend. The scanned document was QUARANTINED. Virus Information: The attachment Movie_0074.mpeg.pif contained the virus W32.Sobig.A@mm and could NOT be repaired. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RE: FreeBSD firewall for high profile hosts - waste of time ?
What is the size of your pipe? If the pipe is big, then so should your BSD box be. The only time i've used something as small as 500ghz Celery it was for a puny 10mbit. What kind of network adapters are you using? I cant recommend using anything other than Intel. The drivers suck for the other cards. Have you applied POLLING (man polling)? If the computer in itself chokes, this will in almost every case prevent that. ( Requires cards such as Intel ) Do you filter outgoing packets so that your pipe wont be filled with ICMP's or RST's on exit? Dummynet is good for that. If the incoming attack isnt large enough to completely block your pipe one way, it often blocks on exit as the responses go back. Do you limit the amount of ICMP responses on each of the servers? May i suggest using creative routing for packets on exit going to unassigned or unroutable nets? How about getting a (perhaps smaller/cheaper) secondary pipe that also announce your network often the attacks go in on one pipe but let the other pipe go free. - This applies mainly when you are the one announcing the networks through BGP or in same provider cases - OSPF. But yes, in my opinion, a FreeBSD firewall is worth using your time with. --- Med vennlig hilsen / Best regards Sten Daniel Sørsdal --- -Original Message- From: Josh Brooks [mailto:[EMAIL PROTECTED]] Sent: 16. januar 2003 23:42 To: Matthew Dillon Cc: Nate Williams; [EMAIL PROTECTED] Subject: Re: FreeBSD firewall for high profile hosts - waste of time ? If attacks are a predominant problem for you, I recommend sticking a machine in between your internet connection and everything else whos Actually this is what I already do - my ISP does all the routing, and it feeds in one interface of my freebsd machine, and everything else is on the other side of the freebsd machine. My freebsd machine does _nothing_ but filter packets and run ssh. ONLY purpose is to deal with attacks. With an entire cpu dedicated to dealing with attacks you aren't likely to run out of CPU suds (at least not before your attackers fills your internet pipe). This allows you to use more reasonable rulesets on your other machines. You know, I keep hearing this ... the machine is a 500 mhz p3 celeron with 256 megs ram ... and normally `top` says it is at about 80% idle, and everything is wonderful - but when someone shoves 12,000-15,000 packets per second down its throat, it chokes _hard_. You think that optimizing my ruleset will change that ? Or does 15K p/s choke any freebsd+ipfw firewall with 1-200 rules running on it ? thanks. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: USB hub detach causing panic in 4.7p3
On Tue, Jan 14, 2003 at 12:05:37PM -0800, Darren Pilgrim wrote: I have a USB hub that's built into my Viewsonic PT775 monitor. The hub probes during boot and post-boot attach as follows: When the hub is disconnected, whether by unplugging it or turning off the monitor, I get a panic in 4.7p3 if there are no devices connected to the hub's downstream ports. mass snip Would this PR be related? http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/45579 I'm not sure? I didn't have anything running, that I could tell, that would have had the uhub device open. The machine was sitting idle at the login prompt. If someone would like to point me at a list of what I need to do to produce useful debugging information, I'll gladly do so. There are a number of brokenisms in the USB stack in -stable. As to whether they will get fixed or not is a matter of whether anyone has the time to MFC the USB stack from -current or not. It's much better over there, and I've already merged the framework to make it easier to MFC, but it is very unlikely that I will be attempting the work myself as I don't use USB on -stable myself. Joe -- Josef Karthauser ([EMAIL PROTECTED]) http://www.josef-k.net/ FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/ Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/ An eclectic mix of fact and theory. = msg39274/pgp0.pgp Description: PGP signature
Re: FreeBSD firewall for high profile hosts - waste of time ?
Terry Lambert wrote: FreeBSD is actually adding pointers and other complexity to its stack [...etc.] So you are referring to common features of stacks of both 4.* and 5.*, right? As far as I understand the matter, this all have to be (and I guess actually is) provable. Now, you were saying that 5.* is even worse, I quote: FreeBSD 5.x network performance is really poor, relative to 4.x; I do not recommend using FreeBSD 5.x in a production environment. Then I wonder *what* were the reasons for not working on matters pointed out??? You were also saying in same post that: The fixes are mostly simple, but for whatever reason, they never make it into FreeBSD proper (my theory is that the developement focus is heavily skewed to general purpose processing, rather than network processing). And throttling the FlagFeature??? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: 4.7 on 2 Xeons SMP?
Want to attract your attention once more. At my place double Xeons fails to start (with only SMP and APIC options added to GENERIC) with following diagnostics: I tried both 4.7-RELEASE srs/sys and that of January 14. That's what I get when booting with SMP enabled (copied from screen): Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 Programming 24 pins in IOAPIC #1 Programming 24 pins in IOAPIC #2 AP #1 (PHY# 6) failed panic y/n? mp_lock = 0001; cpuid = 0; lapic_id = I'm also attaching dmesg of successful boot of GENERIC. Now, when I looked into sources for apic initializing (where it seemingly fails), I've thought that with some qualified guidance (by e-mail or likewise) I could possibly try to address the problem myself. Bad news is that machine's going to be in my posession for two weeks only (in case FreeBSD+Oracle 9i combo fails to start) and that I'm practically unacquainted with kernel debugging so coaching should come really low-level, like in recent Dreyfus article about running IRIX binaries on NetBSD. Good news is I have some knowledge of electronics and recognize some concepts in source and understood almost everything in said article. :) So would anybody be willing to spare time and knowledge? Copyright (c) 1992-2002 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.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz CPU: Pentium 4 (1794.19-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf24 Stepping = 4 Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,b28,ACC real memory = 1073217536 (1048064K bytes) avail memory = 1039351808 (1014992K bytes) Preloaded elf kernel kernel at 0xc050f000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 17 entries at 0xc00fdeb0 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 pci0: unknown card (vendor=0x8086, dev=0x2541) at 0.1 pcib1: PCI to PCI bridge (vendor=8086 device=2543) at device 2.0 on pci0 pci1: PCI bus on pcib1 pci1: unknown card (vendor=0x8086, dev=0x1461) at 28.0 pcib2: PCI to PCI bridge (vendor=8086 device=1460) at device 29.0 on pci1 pci2: PCI bus on pcib2 pci1: unknown card (vendor=0x8086, dev=0x1461) at 30.0 pcib3: PCI to PCI bridge (vendor=8086 device=1460) at device 31.0 on pci1 pci3: PCI bus on pcib3 uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x7000-0x701f irq 10 at device 29.0 on pci0 usb0: Intel 82801CA/CAM (ICH3) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801CA/CAM (ICH3) USB controller USB-B port 0x7020-0x703f irq 5 at device 29.1 on pci0 usb1: Intel 82801CA/CAM (ICH3) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pcib4: Intel 82801BA/BAM (ICH2) Hub to PCI bridge at device 30.0 on pci0 pci4: PCI bus on pcib4 ahc0: Adaptec 29160N Ultra160 SCSI adapter port 0x8000-0x80ff mem 0xfc24-0xfc240fff irq 5 at device 2.0 on pci4 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs pci4: ATI Mach64-GR graphics accelerator at 3.0 irq 11 fxp0: Intel Pro 10/100B/100+ Ethernet port 0x8800-0x883f mem 0xfc20-0xfc21,0xfc242000-0xfc242fff irq 11 at device 4.0 on pci4 fxp0: Ethernet address 00:02:b3:b0:c5:06 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Intel Pro 10/100B/100+ Ethernet port 0x8840-0x887f mem 0xfc22-0xfc23,0xfc243000-0xfc243fff irq 11 at device 5.0 on pci4 fxp1: Ethernet address 00:02:b3:b0:c2:14 inphy1: i82555 10/100 media interface on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI to ISA bridge (vendor=8086 device=2480) at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH3 ATA100 controller port 0x7040-0x704f,0-0x3,0-0x7,0-0x3,0-0x7 irq 0 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: unknown card (vendor=0x8086, dev=0x2483) at 31.3 irq 11 orm0: Option ROMs at iomem 0xc-0xc7fff,0xe3800-0xe3fff on isa0 fdc0: NEC 72065B or clone 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: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags
Re: USB hub detach causing panic in 4.7p3
Josef Karthauser wrote: On Tue, Jan 14, 2003 at 12:05:37PM -0800, Darren Pilgrim wrote: I have a USB hub that's built into my Viewsonic PT775 monitor. The hub probes during boot and post-boot attach as follows: When the hub is disconnected, whether by unplugging it or turning off the monitor, I get a panic in 4.7p3 if there are no devices connected to the hub's downstream ports. mass snip Would this PR be related? http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/45579 I'm not sure? I didn't have anything running, that I could tell, that would have had the uhub device open. The machine was sitting idle at the login prompt. If someone would like to point me at a list of what I need to do to produce useful debugging information, I'll gladly do so. There are a number of brokenisms in the USB stack in -stable. As to whether they will get fixed or not is a matter of whether anyone has the time to MFC the USB stack from -current or not. It's much better over there, and I've already merged the framework to make it easier to MFC, but it is very unlikely that I will be attempting the work myself as I don't use USB on -stable myself. So the problem I'm having is a known issue when detaching a uhub device, then? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: USB hub detach causing panic in 4.7p3
On Fri, Jan 17, 2003 at 10:20:24AM -0800, Darren Pilgrim wrote: There are a number of brokenisms in the USB stack in -stable. As to whether they will get fixed or not is a matter of whether anyone has the time to MFC the USB stack from -current or not. It's much better over there, and I've already merged the framework to make it easier to MFC, but it is very unlikely that I will be attempting the work myself as I don't use USB on -stable myself. So the problem I'm having is a known issue when detaching a uhub device, then? I guess... there was a problem with hubs not working which was fixed about a year ago in -current. I don't know if the problem is with all uhubs, or just some uhubs. I work on the assumption that plug-and-play is broken in 4.x's usb stack. Try not to unplug things. If you do and it works, bonus! :). Joe msg39278/pgp0.pgp Description: PGP signature
Re: 4.7 on 2 Xeons SMP?
On 17-Jan-2003 Yury Tarasievich wrote: Want to attract your attention once more. At my place double Xeons fails to start (with only SMP and APIC options added to GENERIC) with following diagnostics: I tried both 4.7-RELEASE srs/sys and that of January 14. That's what I get when booting with SMP enabled (copied from screen): Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 Programming 24 pins in IOAPIC #1 Programming 24 pins in IOAPIC #2 AP #1 (PHY# 6) failed panic y/n? mp_lock = 0001; cpuid = 0; lapic_id = This is a known problem with the SE7500CW2 motherboards that doesn't have a solution atm. We are having difficulties sending IPI's to these machines for some reason and we don't know why yet. :-/ If your motherboard is not an Intel SE7500CW2 please let me know. Other Xeon SMP motherboards seem to work fine. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD 5-Current/RC en boot0cfg
In message [EMAIL PROTECTED], Dirk-Will em van Gulik writes: In short: A working procedure for making an ATA disk bootable does not work reliably with CF cards/with a Soekris. I use this script, and it worked reliably for me on -current when I last updated my GPS server a few weeks back. http://phk.freebsd.dk/misc/mk.sh -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | 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 [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD 5-Current/RC en boot0cfg
On Fri, 17 Jan 2003 [EMAIL PROTECTED] wrote:
http://phk.freebsd.dk/misc/mk.sh
There is no boot0cfg in there at all; was that already done (once) to the
CF card, or did it get a 'fdisk /mbr' under dos already ?
Or should I understand that:
fdisk -f file
(activate 1)
disklabel -R -B md${MD}s1 _.disklabel
is enough ? And boot0cfg etc is not needed in any way ?
Dw
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Promise ATA133 controller
Is anyone currently working on support for the Promise PDC20275 FastTrack TX EIDE Controller, which comes on the AOpen AX4B Pro-533 for ATA133? If so, is there an ETA for support? Thanks, -Travis To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD 5-Current/RC en boot0cfg
In message [EMAIL PROTECTED], Dirk-Will em van Gulik writes: On Fri, 17 Jan 2003 [EMAIL PROTECTED] wrote: http://phk.freebsd.dk/misc/mk.sh There is no boot0cfg in there at all; was that already done (once) to the CF card, or did it get a 'fdisk /mbr' under dos already ? This produces a image file which I write the he compact flash with the dd(1) command. There is nothing outside of this file that needs done. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | 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 [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD 5-Current/RC en boot0cfg
Here's the stuff I've been using. The dd in there that zeros stuff
seems to help a bit, but still certain cards don't work the first try
100% of the time. Sandisk seems to work 100% of the time for me
anyways. Don't forget to set disk to the right disk :) This stuff
gets followed by a newfs and tunefs.
#!/bin/sh -x
disk=ad8
disklabel -W ${disk}
dd if=/dev/zero of=/dev/${disk} bs=1k count=10
fdisk -BI ${disk}
disklabel -w -B ${disk}s1 auto
disklabel ${disk}s1 /tmp/label.$$
disklabel ${disk}s1 |
egrep unused |
sed s/c:/a:/ |
sed s/unused/4.2BSD/ /tmp/label.$$
disklabel -R -B ${disk}s1 /tmp/label.$$
rm -f /tmp/label.$$
boot0cfg ${disk}
On Friday, Jan 17, 2003, at 12:09 US/Pacific, Dirk-Willem van Gulik
wrote:
In short: A working procedure for making an ATA disk bootable does not
work reliably with CF cards/with a Soekris.
On FreeBSD with a normal IDE/ATA hard disk the following sequence:
fdisk -BI ad0
disklabel -w -B ad0s1 auto
disklabel -e ad0s1
... newfs what is needed
boot0cfg -v -B ad0
will reliably turn an IDE disk into something bootable (followed after
a
make install-world DESTDIR=..)
Is this the correct sequence ?
And though I can boot from CF cards; things are bit hitmiss; and it is
not clear to me exactly what the right procedure is.
The issue is that I seemingly get random results. And simply re-running
the script or rebooting changes behavour.
Issues seen are:
- Flashcards simply do not want to be 'seen' anymore with
/stand/sysinstall; it will bail out wit no disk detected.
- The flashcard show *different results* on successive run
with disklabel after an init iwth
fdisk -BI ad0:
c: 2498240unused0 0 # (Cyl.0 -
247*)
or
c: 2498240unsued 1024 819216 # (Cyl.0 -
247*)
quite random; with the same card and may change with a reboot.
Then after a disklabel edit once sees either one of the following
three:
a: 24982404.2BSD0 0 # (Cyl.0 -
247*)
c: 2498240unused0 0 # (Cyl.0 -
247*)
or
a: 24982404.2BSD 1024 819216 # (Cyl.0 -
247*)
c: 2498240unsued0 016 # (Cyl.0 -
247*)
or
a: 24982404.2BSD 1024 819216 # (Cyl.0 -
247*)
c: 2498240unsued 1024 819216 # (Cyl.0 -
247*)
Again; mixed across cycles and boots. Is there anything in the
new GEOM or BIOS which can be remembered across reboots, including
power cycles.
Right now the following commands :
boot soekris diskless
with GENERIC kernel using usual /var and /tmp on mfs.
setenv TERM vt100
fdisk -BI ad0
disklabel -w -B ad0s1 auto
disklabel -e ad0s1
- add 'a: 4.2BSD line'
- remove fsize/bsize
a: 249824 0 4.2BSD
a: 249824 0 untitled
disklabel ad0s1 will output 8 out of 11 times:
a: 249824 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 247*)
c: 249824 0 unsued 0 0 16 # (Cyl. 0 - 247*)
boot0cfg -v -B ad0
9-10 cases will give
GEOM: new disk ad0
ar: FreeBSD check1 failed
ad0: Hitachi CVM1.1.1/Rev 1.01 ATA-0 disk at ata0-master
ad0: 122MB (250368 sectors), 978 C, 8 H, 32 S, 512 B
ad0: 1 secs/int, 1 depth queue, BIOSPIO
ad0: piomode=1 dmamode=-1 udmamode=-1 cblid=0
GEOM: Configure ad0s1, start 16384 length 127909888 end 127926271
GEOM: Add ad0s1 hot[0] start 512 length 276 end 787
GEOM: Configure ad0s1a, start 0 length 127909888 end 127909887
GEOM: Configure ad0s1c, start 0 length 127909888 end 127909887
Manual root filesystem specification:
fstype:device Mount device using filesystem fstype
eg. ufs:da0s1a
? List valid disk boot devices
empty line Abort manual input
mountroot ufs:ad0s1a
panic: Root mount failed, startup aborted.
Debugger(panic)
Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
and sometimes:
mountroot ufs:ad0s1a
Mounting root from ufs:ad0s1a
start_init: trying /sbin/init
..hang...
and then again, 1 in 50 times it will boot just fine. What am I doing
wrong. How can I make this more reliable ?
Dw
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: Promise ATA133 controller
Hello, Travis L. Leuthauser! On Fri, Jan 17, 2003 at 04:12:34PM -0600, you wrote: Is anyone currently working on support for the Promise PDC20275 FastTrack TX EIDE Controller, which comes on the AOpen AX4B Pro-533 for ATA133? If so, is there an ETA for support? This one? atapci0: Promise TX2 ATA133 controller port 0xcc00-0xcc0f,0xd000-0xd003,0xd400-0xd407,0xd800-0xd803,0xdc00-0xdc07 mem 0xdfefc000-0xdfef irq 11 at device 14.0 on pci2 -- NEVE-RIPE, will build world for food Ukrainian FreeBSD User Group http://uafug.org.ua/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: nswap
Thus spake Mark Santcroos [EMAIL PROTECTED]: in sys/systm.h: extern int nswap; /* size of swap space */ in vm/vm_swap.c: static int nswap; /* first block after the interleaved devs */ Is the extern pointing to this variable? (It seems so, don't see any other such variable in the three) If so, is there any problem with making nswap non-static? It's a constant that is only relevant to the management of the swap allocation bitmap, so it is properly static. It shouldn't be declared in sys/systm.h. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD firewall for high profile hosts - waste of time ?
Yury Tarasievich wrote: Terry Lambert wrote: FreeBSD is actually adding pointers and other complexity to its stack [...etc.] So you are referring to common features of stacks of both 4.* and 5.*, right? Mostly 5.x for the mbuf metadata modifications; they haven't been back-ported to the 4.x branch, AFAIK. The IPv4 IPSEC problems for no-IPSEC-using connections are 4.x and 5.x both, and so are the timer and the livelock issues. As far as I understand the matter, this all have to be (and I guess actually is) provable. Yes. Duke University and Rice University have both done papers in this area (see Scala server or lazy receiver processing in a search engine; I recommend http://citeseer.nj.nec.com/cs for technical papers). Now, you were saying that 5.* is even worse, I quote: FreeBSD 5.x network performance is really poor, relative to 4.x; I do not recommend using FreeBSD 5.x in a production environment. Then I wonder *what* were the reasons for not working on matters pointed out??? The SMP-ification and the use of the interrupt threads model, etc., adds latency to packet processing. Additional latency translates into additional pool retention time, latency in response after the processing finally happens, and reduced reuse rate. The number that was posted by someone who had done benchmarking as -65% for flat network performance, going from 4.x to 5.x. The reality is that this is probably a little exaggerated, if you take into account common real-world operations, instead of benchmarking. One actual good benchmark is connections per second; using a combination of soft interrupt coelescing, hard interrupt coelescing, and lazy receiver processing, you get the following: Connections per second: Well tuned stock FreeBSDWell tuned modified FreeBSD --- 7,200 32,126 This is on a FreeBSD *without* a SYN cache. Most of the reasons this stuff is not in FreeBSD is NIH (not being the pet research project of a committer), license, the need to productize the code from research, etc.. For the complaints about scalability... Linux has a project that they are very proud of, in order to obtain 10,000 simultaneous TCP connections. With respect, I personally achieved 1,600,000 simultaneous TCP connections on a modified FreeBSD box with 4G of RAM. During this process, I found a credentials reference count overflow bug (since fixed in FreeBSD), which occurred on close, after opening more than 32,763 connections in one process. No one else reported this bug, so I have to assume that no one else ever ran FreeBSD up to that number of connections, before. So... the primary reason is that no one is using FreeBSD under the loads necessary to cause the problems to exhibit themselves. You have to have a need in order to be interested in a way of satifying a need. 8-). You were also saying in same post that: The fixes are mostly simple, but for whatever reason, they never make it into FreeBSD proper (my theory is that the developement focus is heavily skewed to general purpose processing, rather than network processing). And throttling the FlagFeature??? That sort of thing has to be there, for FreeBSD to be interesting as a reasearch OS, so that additional work occurs on the platform; that's pretty much a given. You wouldn't have someone as well-known as Sam Leffler donating code, if that code was unlikely to get in, since it would be a waste of his time and effort (the same reason some people have left the project, actually). So even if you don't like feature creep or bloat, when it impacts top end performance, top end performance really doesn't matter to most people who are doing the coding (i.e. how many OC3's do you have to your computer? How many would you need to have to saturate even a single gigabit ethernet?). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RE: Promise ATA133 controller
I don't believe it's the same one.. here's my pciconf -v -l output for the controller: none3@pci2:14:0:class=0x018085 card=0x1275105a chip=0x1275105a rev=0x01 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20275 FastTrack TX EIDE Controller' class= mass storage Running 4.7 Stable as of today around 2PM CST. -Travis -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alexandr Kovalenko Sent: Friday, January 17, 2003 5:01 PM To: Travis L. Leuthauser Cc: [EMAIL PROTECTED] Subject: Re: Promise ATA133 controller Hello, Travis L. Leuthauser! On Fri, Jan 17, 2003 at 04:12:34PM -0600, you wrote: Is anyone currently working on support for the Promise PDC20275 FastTrack TX EIDE Controller, which comes on the AOpen AX4B Pro-533 for ATA133? If so, is there an ETA for support? This one? atapci0: Promise TX2 ATA133 controller port 0xcc00-0xcc0f,0xd000-0xd003,0xd400-0xd407,0xd800-0xd803,0xdc00-0xdc07 mem 0xdfefc000-0xdfef irq 11 at device 14.0 on pci2 -- NEVE-RIPE, will build world for food Ukrainian FreeBSD User Group http://uafug.org.ua/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Promise ATA133 controller
Hello, Travis L. Leuthauser! On Fri, Jan 17, 2003 at 05:41:04PM -0600, you wrote: I don't believe it's the same one.. here's my pciconf -v -l output for the controller: none3@pci2:14:0:class=0x018085 card=0x1275105a chip=0x1275105a rev=0x01 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20275 FastTrack TX EIDE Controller' class= mass storage Running 4.7 Stable as of today around 2PM CST. atapci0@pci2:14:0: class=0x010485 card=0x704d1462 chip=0x5275105a rev=0x01 hdr=0x00 vendor = 'Promise Technology' device = 'PDC20276 Ultra133 TX2/FastTrak TX Lite EIDE Controller' class= mass storage subclass = RAID 4.7-RELEASE-p3 -- NEVE-RIPE, will build world for food Ukrainian FreeBSD User Group http://uafug.org.ua/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
5400RPM|7200RPM Cable bottleneck?
Greetings. Does anyone know if a NFS server with a 7200RPM IDE HD will perform significantly better than a 5400RPM IDE HD over a cable connection? I'm assuming that the performance will only be noticable iff the NFS client is close(geographically) to the NFS server, i.e. same LAN since the bottleneck would be at the network level. Also, if the 5400RPM IDE HD was RAIDed, would that match an unRAIDed 7200RPM IDE HD? Thanks in advance. __ Jay Sern Liew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RE: Promise ATA133 controller
Hmm... my ata-pci.c is revision 1.32.2.12, which should support it correct? -Travis -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alexandr Kovalenko Sent: Friday, January 17, 2003 5:48 PM To: Travis L. Leuthauser Cc: [EMAIL PROTECTED] Subject: Re: Promise ATA133 controller Hello, Travis L. Leuthauser! On Fri, Jan 17, 2003 at 05:41:04PM -0600, you wrote: I don't believe it's the same one.. here's my pciconf -v -l output for the controller: none3@pci2:14:0:class=0x018085 card=0x1275105a chip=0x1275105a rev=0x01 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20275 FastTrack TX EIDE Controller' class= mass storage Running 4.7 Stable as of today around 2PM CST. atapci0@pci2:14:0: class=0x010485 card=0x704d1462 chip=0x5275105a rev=0x01 hdr=0x00 vendor = 'Promise Technology' device = 'PDC20276 Ultra133 TX2/FastTrak TX Lite EIDE Controller' class= mass storage subclass = RAID 4.7-RELEASE-p3 -- NEVE-RIPE, will build world for food Ukrainian FreeBSD User Group http://uafug.org.ua/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
current 'make buildworld' record (non SMP)?
I was testing a new machine and it did a make buildworld in about 18:47. I was impressed.. 2.8GHz P4, 2G ram. src, obj on 2 x SCSI drives on separate controllers. (there are more but they were not involved) This is I might add for a 4.7++ world. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Promise ATA133 controller
Hello, Travis L. Leuthauser! On Fri, Jan 17, 2003 at 06:22:13PM -0600, you wrote: Hmm... my ata-pci.c is revision 1.32.2.12, which should support it correct? Yes. here's my pciconf -v -l output for the controller: none3@pci2:14:0:class=0x018085 card=0x1275105a chip=0x1275105a rev=0x01 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20275 FastTrack TX EIDE Controller' class= mass storage Running 4.7 Stable as of today around 2PM CST. atapci0@pci2:14:0: class=0x010485 card=0x704d1462 chip=0x5275105a rev=0x01 hdr=0x00 vendor = 'Promise Technology' device = 'PDC20276 Ultra133 TX2/FastTrak TX Lite EIDE Controller' class= mass storage subclass = RAID 4.7-RELEASE-p3 -- NEVE-RIPE, will build world for food Ukrainian FreeBSD User Group http://uafug.org.ua/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
replacing GNU grep with UNIX grep.
Hi guys; I replaced GNU grep with SCO's grep from http://unixtools.sourceforge.net . They are both covered by the same license (GPL) so there might not be any real advantage in the replacement. I haven't compared performance either. Compiling was trivial, I only had to cut and paste one function from stubs.c in their libregexp stuff and it seems to work fine. I just wanted to mention this in case there someone interested in an alternative. cheers, Pedro. __ Yahoo! Cellulari: loghi, suonerie, picture message per il tuo telefonino http://it.yahoo.com/mail_it/foot/?http://it.mobile.yahoo.com/index2002.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: replacing GNU grep with UNIX grep.
FWIW; The UNIX grep executable is like 3 times smaller than GNU grep but also like 3 times slower. Also .. JIC you wonder, I only built this for curiosity, I recommend keeping GNU grep unless Caldera changes the license :). Pedro. __ Yahoo! Cellulari: loghi, suonerie, picture message per il tuo telefonino http://it.yahoo.com/mail_it/foot/?http://it.mobile.yahoo.com/index2002.html To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Whoopsie! Hope I didn't jam everyone up...
My great plan of letting my mail spool file accumulate until I had all my new equipment like a new hard drive and Eudora and new browsers etc. uh, had a little uh...bug in it. My mail spool file got too big and my mail got bounced. I am pretty sure this affected only me. If it didn't I apologize. Anyway I used mail2web to clear it up and it seems to be working. Hopefully it didn't freak out postini or something. Anyway if anyone sent me mail and it bounced please retransmit. Sorry if anyone got clutter some bounce messages. Things should hopefully will now. Sorry to inflict people with my bad planning and please excuse the verbose apology. Have Fun, Sends Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
