Re: New feutures...........
> First af all I would like to thank the FreeBSD developers for making > such a great system! Half a year ago, I had to choose an OS for my > server and the first decision was between Windows and Unix, ofcourse > it didn't take much research to determine that Unix were the better > choice. But now I had to choose from Linux, Solaris and one of the > BSD's, and one of the BSD's is was. After a little reseach I had > nerroed it down to OpenBSD and FreeBSD, and FreeBSD won me over :-) > But enough of this, on to the 2 requests: 1. Is there a way to hide a > user from other users? Fx programs like w, who, users, netstat, top, > ps all show what other users are doing. It would fx be a good idea to > hide root or the admin's activities from other users. If you are > trying to catch a cracker, then you know that he/she if not stupid > enough to login while other users (especial root) are online. But > perhaps this feuture to hide a user already exists? > > 2. After having read "Operating systems - Internals and Design > Principles" by William Stallings I have a few questions. He writes, > among other things, about VM, process and tread design, and compares > Unix SVR4, Solaris and Windows NT. Sometimes he more or less say, that > what fx Solaris have done is the way of the future and other times the > unix way was the bedst. I don't want to discuss why FreeBSD have > designed the kernel as they have, but I know that sometimes when you > work very closely with something, you forget to "look up". I mean, > does FreeBSD analyse the Linux and Solaris kernel, maybe adobt some of > the good thing they have made? I don't expect FreeBSD to rewrite the > kernel, but to learn from Solaris and Linux. If FreeBSD allready do > this, then I am sorry for having troubled you with this mail!!! I think you misunderstood somewhere along the lines. FreeBSD is just as good as solaris and linux in most things, and better in others. > > Best regards > Rafter > > ps: 1. I hope that in the future FreeBSD will remain a servers only > OS. Meaning that I hope the developers don't spend to much time making > games, grafical programs and stuff like gnome/kde/x11. I hope the opposite. I use FreeBSD all day every day as my desktop system, and I'd die if I didn't have the things that you mention above as hoping that they never happen. > 2. I hope that in the furture the FreeBSD developers will rewrite the > system in C++. This will most likely NEVER happen. One of the reasons FreeBSD and UNIX in general are so fast is because they don't have to deal with the overhead of C++. C is smaller and faster. > 3. I hope for even more focuse on security. As far as I know there is a whole project focusing on FreeBSD's security. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Junior Kernel hacker task: Floppy driver mode handling.
I was thinking about looking into it, but I won't have time to start until
the 18th. if you wanna do it, go for it, and I'll wait my turn for the
next thing I can do in the kernel. :-D
Ken
On Tue, 11 Dec 2001, Andrew R. Reiter wrote:
>
> Someone already doing this? If not, I'm down.
>
> On Tue, 11 Dec 2001, Poul-Henning Kamp wrote:
>
> :
> :There exists a patch for adding a mode to our floppy driver to
> :add DEC RX50 media handling.
> :
> :The crucial part of this is the addition of this line:
> :{ 10,2,0xFF,0x10,80, 800,1,FDC_300KBPS,1,0x2E,1 }, /* 400K DEC RX50 */
> :
> :But if one examines the fd.c driver, one cannot help but notice that the
> :handling of densities is a bit convoluted, to put it mildly.
> :
> :I'm looking for a volounteer to do this, it is a quite simple job and
> :I am quite sure that practically everybody has the hardware they need to
> :do this :-)
> :
> :Cleaning it up consists of the following steps:
> :
> :1. Define a new set of (bitmap) macros to distinguish the drive type:
> : #define FD_3S 0x0001 /* 3.5" single density */
> : #define FD_5S 0x0002 /* 5.25" single density */
> : ...
> :And use these instead of the FD_1200 and similar in
> :struct fd_data->type.
> :
> :2. Augment the struct fd_type with two new fields:
> : int minor; /* minor device encoding */
> : int drives; /* bitmap of compatible drives (FD_[35][SD]) */
> :And fill these fields out in the fd_types[NUMTYPES] array.
> :Add a termination entry at the end of the table so the
> :NUMTYPES, NUMDENS, and FD_%d[5_25] #defines can be eliminated.
> :
> :3. Change the _clone code to use the new "minor" field instead of
> :the private table it uses now. (Eliminate and avoid any
> :use of NUMTYPES, NUMDENS and FD_%d[5_25]).
> :
> :4. Change the code in Fdopen to examine the "drives" field in the
> :fd_types[] array instead of the hardcoded switch. (Eliminate
> :and avoid any use of NUMTYPES, NUMDENS and and FD_%d[5_25]);
> :
> :5. Remove any other use of NUMTYPES, NUMDENS and FD_%d[5_25]
> :
> :6. Add the "rx50" entry from above to the table to show how simple
> :that is now.
> :
> :7. Make it possible to define a new mode from userland with an ioctl.
> :(hint: instead of the index, put a pointer to the struct fd_type into
> :the fd_data structure.)
> :
> :Preferably, send one patch per step rather than one huge patch since that
> :will make reviewing easier.
> :
> :First volounteer to send me email gets the assignment.
> :
> :--
> :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
> :
>
> --
> Andrew R. Reiter
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
>
>
> 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: FreeBSD performing worse than Linux?
As a side note, I turned off delayed ack on both machines, and had the sendsize and recvsize set at 32768... I'm talking about wirespeed too, not measured incredibly accurately, but just measured using one of the windowmaker dockapps :-D Ken On Fri, 30 Nov 2001, Kenneth Wayne Culver wrote: > Wierd, on my Dual PII 300 I'm getting around 8MB/sec to an 800MHz > athlon. The athlon is using a 3com 905b I believe, and the PII is using an > intel fxp type card. Granted this is from my living room to my bedroom so > that may be part of what I see. Also, the Dual PII is running -STABLE as > of a week ago, and the Athlon is running -CURRENT as of about a week ago. > > Ken > > On Fri, 30 Nov 2001, James C. Durham wrote: > > > (snip...a large number of postings regarding slow performance by 4.x > > kernels with TCP/IP) > > > > A friend who works for a local university and I tried moving large > > files using variouis OS'es and hardware. These are FTP transfers > > with file sizes from 100 to 300 megabytes.. > > > > The conclusion we arrived at was that the TCP performance of FreeBSD > > 4.x and Linux is aproximately the same and that processor speed > > makes the most difference. In one case, a fast laptop with 16 bit > > pcmcia NIC did poorly. > > > > Moving large files on 100mb/s ethernet backbones gave the folowing > > results... > > > > Dual 800 mhz PIII processors with Linux 6.1: > > 10mB/s. > > > > Sunblade 100's: > > 10mB/s. > > > > Single 1.4ghz processors (noname box)with 3C905 NICS, > > FreeBSD-stable (June 2001).: > > 9.5 mB/s. > > > > In the case wehere we had only one machine of a type, we > > used the dual 800mhz machines as a "sink"...with the following > > results (this is probably questionable): > > > > Dual 333 Linux 5.1 5mB/s > > > > Pentium 350 III with 3C905 NIC, Linux 5.1: > > 2mB/sec > > > > K6-2 400 with smc NIC, Linux 5.1: > > 2.8mB/sec > > > > Dell 500mhz PowerEdge with 4.3 with 3C905 NIC to HP Netserver PII 266, > > both running 4.3-RELEASE: > > 3.0 mB/sec. > > > > Dell 500mhz PowerEdge with 4.3 to Dell 850mhz laptop running > > 4.4 with Dlink PCMCIA ethernet card: > > 1.0 mB/sec. (caused by pcmcia NIC?) > > > > PIIMMX 200mhz box running 4.4-Relese with 3C905 to same Dell Laptop: > > 500kB/sec. > > > > Unfortunately, we didn't have any 7.x Linux available or 3.X FreeBSD. > > > > FWIW... > > > > Jim Durham > > > > 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 > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: TCP Performance Graphs
> > The question that immediately comes to mind is, why not simply use > > as big a value as possible? The problem comes down to buffering > > the data, and busy servers may have to buffer a lot of data. Having > > a 1 meg window size may have you buffer 1 meg per connection. Note > > that FreeBSD's current buffer management is particularly stupid in > > that it will _always_ buffer 1 Meg, need it or not. Until we fix > > this we need an interim solution. > > > > I thought that I heard a few months ago that Matt Dillon was looking > at ways to dynamically size tcp windows from within the kernel. Maybe > I'm on crack. You're not on crack, I don't know if it was Matt Dillon, but someone was doing this, I was using the patches for about a month to test them out. Ken > > Maybe we should look at the Dynamic Righsizing work being done at > LANL. See "Dynamic Adjustment of TCP Window Sizes" and > "Dynamic Right-Sizing: A Simulation Study" at > http://public.lanl.gov/radiant/publications.html > > Cheers, > > Drew > > 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: FreeBSD performing worse than Linux?
Wierd, on my Dual PII 300 I'm getting around 8MB/sec to an 800MHz athlon. The athlon is using a 3com 905b I believe, and the PII is using an intel fxp type card. Granted this is from my living room to my bedroom so that may be part of what I see. Also, the Dual PII is running -STABLE as of a week ago, and the Athlon is running -CURRENT as of about a week ago. Ken On Fri, 30 Nov 2001, James C. Durham wrote: > (snip...a large number of postings regarding slow performance by 4.x > kernels with TCP/IP) > > A friend who works for a local university and I tried moving large > files using variouis OS'es and hardware. These are FTP transfers > with file sizes from 100 to 300 megabytes.. > > The conclusion we arrived at was that the TCP performance of FreeBSD > 4.x and Linux is aproximately the same and that processor speed > makes the most difference. In one case, a fast laptop with 16 bit > pcmcia NIC did poorly. > > Moving large files on 100mb/s ethernet backbones gave the folowing > results... > > Dual 800 mhz PIII processors with Linux 6.1: > 10mB/s. > > Sunblade 100's: >10mB/s. > > Single 1.4ghz processors (noname box)with 3C905 NICS, > FreeBSD-stable (June 2001).: >9.5 mB/s. > > In the case wehere we had only one machine of a type, we > used the dual 800mhz machines as a "sink"...with the following > results (this is probably questionable): > > Dual 333 Linux 5.1 5mB/s > > Pentium 350 III with 3C905 NIC, Linux 5.1: >2mB/sec > > K6-2 400 with smc NIC, Linux 5.1: > 2.8mB/sec > > Dell 500mhz PowerEdge with 4.3 with 3C905 NIC to HP Netserver PII 266, > both running 4.3-RELEASE: > 3.0 mB/sec. > > Dell 500mhz PowerEdge with 4.3 to Dell 850mhz laptop running > 4.4 with Dlink PCMCIA ethernet card: > 1.0 mB/sec. (caused by pcmcia NIC?) > > PIIMMX 200mhz box running 4.4-Relese with 3C905 to same Dell Laptop: > 500kB/sec. > > Unfortunately, we didn't have any 7.x Linux available or 3.X FreeBSD. > > FWIW... > > Jim Durham > > 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
domain sockets question (don't laugh)
While I've been coding for a long time, and am fairly decent at coding in the kernel, I've never really had a chance to get into sockets programming. So I thought I'd write a simple set of programs to see how things work. From what I understand, when you read on a socket, you have to do it in a loop because it won't block and wait for the total amount of data specified, while write will not return until all specified data has been written. My problem is that I've set up a read loop to read in chunks that are the size of the recv/send buffers (16384 bytes) from the socket (until the end of course, when it reads only what's left), then when I write from one program to the socket for the other program to read, the program that's writing exits with the message "broken pipe" while the program that's reading doesn't think there was any error, reads the amount of data it should have read (although I'm not sure if there's any data there). Can anyone tell me what's going on? Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: altq question.
> either you have set the bandwidth wrong (does "ipfw pipe show" > list the speed you want for the pipes ? can you post its > output ?) or you are doing the measurement on a saturated link, > in which case when you use dummynet with dynamic queues you have > a lot more buffering going on, and this would explain why you > see higher ping times (but perhaps without it you see some > large amount of losses) ? > ipfw pipe show shows the correct amounts. I did the measurements on a non-saturated link, I'm sure of this because when I ipfw flush, ipfw queue flush, the ping goes back to normal. I have no packet loss either way, whether dummynet is configured or not. An added note, this is running on an 533 MHz alpha with a de type card hooked to the dsl modem running at 10Mbit/sec full duplex (dsl connection is rated at 608Kbit/s down and 128 Kbit/s up), and an xl type card connected to the internal net running at 100Mbit/sec Full duplex. My configuration looks like this: ipfw add queue 1 ip from any to x.x.x.x/24 in via de0 ipfw add queue 2 ip from x.x.x.x/24 to any out via de0 ipfw pipe 1 config bw 570Kbit/s queue 47 ipfw pipe 2 config bw 118Kbit/s queue 10 ipfw queue 1 config pipe 1 weight 40 mask dst-ip 0x00ff ipfw queue 2 config pipe 2 weight 40 mask src-ip 0x00ff I set it to 570Kbit/s download because this is the top download speed I measured (I get this speed to pretty much every site I download from, to arrive at this number I downloaded a file 2 times from a site that gave me around 62Kbytes/sec (my max speed), then I turned on queueing with successively larger bw values for pipe 1 until I could attain my top speed, then I added 10 Kbit/s just to be sure that I was getting the full wirespeed my connection would support. I did this for the upstream as well) Thanks for your help. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
altq question.
I was wondering if anyone had ever used altq to throttle people on an adsl connection. Basically what I want to do make each user share bandwidth evenly, but in such a way that they can use all the available bandwidth individually if nobody else is using it. However, I also want to be able to set aside some of that bandwidth for ssh. The problem is on my machine, with dummynet, I can do all this, but when I set it up to limit both incoming (608Kbit/s) and outgoing (128Kbit/sec) connections, the ping time through the machine goes up by 5 seconds, if I turn off the queuing options on the outgoing connections/packets, the ping returns to normal. Also, I can't figure out with altq how to set up different incoming and outgoing bandwidths. Does anyone have any experience doing anything like this with altq? if not, can someone tell me how to fix my ping problem with dummynet? Thanks. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD and Athlon Processors
> > > > Yeah. As long as you avoid motherboards with the VIA KT133A/KT133 > > chipset and the VIA 686B Southbridge, you're probably fine (not all such > > motherboards supposedly have problems, but how do you tell the > > difference?). For more info, check out: Well, I've been using an abit kt7 (via kt133/686a chipset) with FreeBSD and I havn't had the slightest problem. I'm running this with an 800 MHz Thunderbird. > > I'm using both of those (iwill kk266) with a thunderbird 850, and haven't had > problems in fbsd. Linux flakes out a bit when I tell it I have a k7 processor, > so I told it I have a k6 and it works fine. > Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How to visit physical memory above 4G?
Also, the PIII CAN'T natively support more than 4GB of ram. If a particular PIII motherboard supports this, then it's using some kind of wierd chipset that allows this to happen. 4GB is the limit with a 32 bit chip I believe; and the PIII is a 32-bit chip. Ken On Thu, 2 Aug 2001, Rik van Riel wrote: > On Wed, 1 Aug 2001, Terry Lambert wrote: > > > craig wrote: > > > > > > > > > I know PIII can support 64G physical memory. In FreeBSD how can I visit such > > > range memory(4G-64G) ? > > > > The short answer is "you can't". > > > > The longer answer is that you end up having to window it using > > segmentation; > > Only if you want to use it all within one process. > > You can have multiple 2 GB (that's the maximum > process size in FreeBSD, right?) programs at the > same time, happily using all physical memory. > > Only the FreeBSD memory management subsystem doesn't > support it (yet?). > > > This basically means that the memory is useless as a DMA target > > or source for disk controllers or gigabit ethernet cards, and is > > pretty useless for swap, ... > > > So for limited uses in data intensive applications, it might be > > usable, > > And for those data intensive applications, it is very > useful indeed... > > > But to directly answer your question: by rewriting much of the > > low core virtual memory and page mapping handling code to know > > about segmentation. > > Not just that. There is a more insidious problem with > the FreeBSD VM code and support of huge machines. > > The part of handling the PAE extended page table format > and mapping high memory pages in and out of KVA (kernel > virtual address) memory to copy stuff is easy. > > Problem is that you'll have to fit all of FreeBSD's VM > data structures in the 2GB of KVA. This just isn't going > to fit with the size the data structures have today ... > > So in order to support huge memory machines "right", > you'd have to put a number of FreeBSD's VM data structures > on a rather strict diet. > > regards, > > Rik > -- > Executive summary of a recent Microsoft press release: >"we are concerned about the GNU General Public License (GPL)" > > > http://www.surriel.com/ > http://www.conectiva.com/ http://distro.conectiva.com/ > > > 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: How to visit physical memory above 4G?
Oh ok, I knew that regular PIII's only had 32 bits... but it's still obviously a pain in the butt to use above 4GB. Ken On Thu, 2 Aug 2001, Rik van Riel wrote: > On Thu, 2 Aug 2001, Kenneth Wayne Culver wrote: > > > Also, the PIII CAN'T natively support more than 4GB of ram. If a > > particular PIII motherboard supports this, then it's using some > > kind of wierd chipset that allows this to happen. 4GB is the > > limit with a 32 bit chip I believe; and the PIII is a 32-bit > > chip. > > The Xeon series have 32 bits of virtual address space > and 36 bits of physical address space. > > Rik > -- > Executive summary of a recent Microsoft press release: >"we are concerned about the GNU General Public License (GPL)" > > > http://www.surriel.com/ > http://www.conectiva.com/ http://distro.conectiva.com/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: How to visit physical memory above 4G?
BUT, don't the motherboards also have to support this? And isn't it only supported through some wierd segmentation thing? KEn On Thu, 2 Aug 2001, John Baldwin wrote: > > On 02-Aug-01 Kenneth Wayne Culver wrote: > > Also, the PIII CAN'T natively support more than 4GB of ram. If a > > particular PIII motherboard supports this, then it's using some kind of > > wierd chipset that allows this to happen. 4GB is the limit with a 32 bit > > chip I believe; and the PIII is a 32-bit chip. > > > > Ken > > Go look at some Intel docs. P6 chips since the Pentium Pro (yes, before > Pentium II) have supported PAE which allows for a 36-bit physical address. > > -- > > John Baldwin <[EMAIL PROTECTED]> -- 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 [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CardBus support...
Cardbus is only supported in FreeBSD-CURRENT. It may never be ported to 4.x Ken On Mon, 30 Jul 2001, Rich Neswold wrote: > Hello, > > We have a few Dell laptops that came with the 3C-575BT ethernet cards. I > was curious about the status of cardbus support under FreeBSD. I couldn't > find a CardBus project page from the Home Page. > > There are CardBus-related files in our 4.3 source tree, but they don't seem > to be included in our kernel builds. > > Is CardBus supported? Or close to supported? Is there a web page that shows > the status of the progress? > > Any information would be appreciated. > > -- > Rich > > > Richard Neswold, Beams Division / Controls Dept | [EMAIL PROTECTED] > Fermilab, PO Box 500, MS 360, Batavia, IL 60510 | voice 1.630.840.3454 > | fax 1.630.840.3093 > > 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: pci device driver writing newbie
> On Wed, Jul 18, 2001 at 09:08:31PM -0400, Kenneth Wayne Culver wrote: > > get my module (which right now does mostly nothing except probing and > > attaching) to detect the ACPI function of this chip, but right now pciconf > > -l shows it as "chip0". I found the devid in > > /usr/src/sys/pci/pcisupport.c, (0x30571106) and commented that case out, > > recompiled my kernel, and rebooted, but no luck, it still detects as > > chip0. What can I do to keep this from happening. This is the only way I > > The first thing that comes to mind is that you will probably find > using a KLD much easier during development for this sort of thing. > There is some basic information in the Developer's Handbook about this > but it is incomplete : > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ > Yep, I already looked at that :-) I'm using a kld for development for the very reason that I don't have to keep rebooting to test. The print of the pci_get_devid in my probe function returns 2 values, and they correspond to the device that say "none0" and "none1" beside them. chip0 reports chip=0x30571106. According to the documentation I have for the via chipset, this is what is supposed be reported for this chip. It's the ACPI device on my via686a chipset. What I did was comment out the case for that devid number from pcisupport.c in /usr/src/sys/pci (I'm working on stable right now) and recompiled my kernel, but that doesn't seem to have made any difference. I'm at work now so I can't try anything else until this evening. One thing I'll try is doing a config -r KERNEL to get rid of all the obj files and recompile everything; I have the feeling that pcisupport.c never compiled over again. Anyway, thanks for your help. > Can you print the return value of pci_get_vendor() in your probe() > function to verify that you are getting the same listing that pciconf > -l reports? Remember that if pciconf -l returns something like > chip=0x2a601093 then 1093 is the vendor ID and 2a60 is the device ID. > I guess the vendor ID for this chip would be 0x1106 then Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
pci device driver writing newbie
I'm currently trying to write a driver for the hardware monitoring function of the Via 686a/b chipset, but I have a problem. I'm trying to get my module (which right now does mostly nothing except probing and attaching) to detect the ACPI function of this chip, but right now pciconf -l shows it as "chip0". I found the devid in /usr/src/sys/pci/pcisupport.c, (0x30571106) and commented that case out, recompiled my kernel, and rebooted, but no luck, it still detects as chip0. What can I do to keep this from happening. This is the only way I can accurately probe and attach this device and find it's base i/o address. Once I have this chip probing and attaching, and have the base io address, I can do the rest of the hardware monitoring functions of this driver on my own. (as a note, to avoid doing floating point calculations in the kernel, and to avoid doing some really nasty hacks that I found in the linux version of this driver, I'll be making the driver return the raw values from the registers, and I'll be writing a library that takes care of making the values that come from the registers useful.) Thanks ahead of time :-) Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: eXperimental bandwidth delay product code (was Re: Networkperformance tuning.)
I have been testing this over a very slow (barely ever over 24000 bps due to a crappy phone line) dial-up link, and as expected, over an idle line there is no difference (typing in an interactive ssh session seems a little quicker, but that could just be me). The gain comes when someone is downloading over the link and I try to type in an interactive ssh session. (I'm sharing the link with 1 other computer). Without the sysctl turned on typing in the "interactive" session results in a 10-15 second wait before anything appears on the screen; but with the sysctl turned on the wait is 2-3 seconds. I'd say that's pretty good work :-) Ken On Mon, 16 Jul 2001, Luigi Rizzo wrote: > > Cool! We were just commenting that it's too bad dummynet/ALTQ really > > couldn't help the interactive response for us dial-up users. Anyway, I > > i haven't seen the beginning of the thread but surely both altq > and dummynet can help, with the CBQ/WFQ support. > > In the case of dummynet, you can pace incoming traffic as well, > at your endpoint. This means you act after the bottleneck, > but the effect is that this way > you will delay acks, and so slow down the connection eating a lot of > bandwidth, and in the steady state this keeps the queue very > short even before the bottleneck. > Much like what products like packeteer do. > > cheers > luigi > > > just tried this on my dial-up connection on a fresh -STABLE but don't > > really notice any appreciable difference. > > > > net.inet.tcp.tcp_send_dynamic_enable: 1 > > net.inet.tcp.tcp_send_dynamic_min: 1024 (tried it with default 4096 too) > > > > My ssh response is still about 3 or 4 seconds behind my typing. What > > should a dial-up user expect? > > > > Thanks! > > > > Tim > > > > 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 > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Block Device I/O
> I saw an old message in 1999 freebsd-hackers archive that said that block > devices were being replaced from freebsd. I tried to follow the trail of > the message but could not find anything more...Also I could not find > any bdevsw[] in the code. I shall be thankful if anyone could give any > further references about how Block I/O is being implemented now... > As far as I know, there is no block IO anymore. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: TCP Window Size
You made it way to big... On 10 Jul 2001, Joseph Lekostaj wrote: > > I've been trying to up my TCP window size from the default 16K and it's caused >nothing but problems. From the info I've found so far, these are the sysctl i've >changed: > > kern.ipc.maxsockbuffer=2097152 > net.inet.tcp.rfc1323=1 > net.inet.tcp.sendspace=524288 > net.inet.tcp.recvspace=524288 > > But if I do that, on boot I get all sorts of error messages about buffer space. >i.e.: > > Jul 9 11:53:20 ccn64 portmap[180]: cannot create tcp socket: No buffer space >available > Jul 9 11:53:21 ccn64 inetd[199]: shell/tcp: socket: No buffer space available > Jul 9 11:53:21 ccn64 inetd[199]: login/tcp: socket: No buffer space available > Jul 9 11:58:55 ccn64 RPC::PlClient[243]: Cannot connect: No buffer space available > Jul 9 11:58:55 ccn64 RPC::PlClient[246]: Cannot connect: No buffer space available > > Is there anything I'm missing? > > -- > Joe LeKostaj > - > Just don't create a file called -rf. > > 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: Athlon MP / AMD 760MP Chipset (Athlon SMP question)
SMP works on athlons... while internally AMD uses the Alpha EV6 bus to give each CPU a full 200MHz point-to-point bus between it and it's RAM, to the OS, it just looks like any other intel based SMP machine. (It just runs faster) Ken On Mon, 9 Jul 2001, Nathan Vidican wrote: > I seem to recall a few discussions about the Dual Athlon buzz some > while back which had stated that the Athlon would essentially require a > completely different SMP spec than that currently utilized by the Intel > procesors. Assuming that this was true, one would assume that the O/S > too would require a different kind of SMP support in order to function > with these CPUs. > Unfortuneately, a recent thread has me at a bit of a loss here; in > that people seem to be speaking about the processor/smp chipset as > though they function just like Intel's do. Assuming that this > conflicting information is indeed correct, then would it not be > feasible to assume that the code currently implemented for using SMP > implementations under FreeBSD would be portable to the new Athlon MP > processor line? > The threads I'm speaking of, were to freebsd-questions most > recently wherein someone had been asking if the new Tyan ThunderK7 > motherboard would work with FreeBSD. The general concencus was 'why > not', from the responses I had read... but no one who answered really > seemed to know for sure. > Just for the record, is it or is it not possible to run SMP with > the new Athlon MP Processors; or has no-one even tried yet? Currently > the only O/S I know of which is promoting the usage of such systems is > Novell Netware, and I am just curious if FreeBSD will (if it is not > currently) be capable of running on such a system? > > > -- > Nathan Vidican > [EMAIL PROTECTED] > http://Nathan.Vidican.com/ > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
more on latency
I think I found the reason that my FreeBSD box is performing so poorly as a NATing router. When I do an ipnat -l to see what "active connections" are there on the router, a list about 3 pages long (using ipnat -l | more) appears. I think maybe it's having trouble because for every packet coming in and out of the router, it's got to look at that list of active connections for the right one to send to and from. Is there any way to make connections that aren't being used go away from the NAT faster? Thanks a lot. Kenneth Culver To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
NAT (ipf/ipnat) latency problems
Recently over the weekend my friends and I had a lanparty, and we wanted to use FreeBSD as his gateway machine (to replace Win2k) to his cable modem. When I got there, he and 3 other people had been playing a game online (over the internet through the Win2k NAT, the game was counterstrike for those who care) and they were seeing really good pings and no packet loss (pings of 15-39ms). I set up the FreeBSD server (which I had already preconfigured for the task) using ipf and ipnat with very simple rules (ipf passes all traffic in and out, and map 192.168.0.0/28 -> 0/32 portmap 2:4 as the ipnat rule. The portmap is so that multiple people from our lan can connect to the same counterstrike server). I pinged the counterstrike server online from our NAT machine and the NAT machine got 15-30ms pings, but when I went online in counterstrike and went to that server, the ping was about 200 ms, and if more than 2 people connected to any counterstrike server at a time, the ping went up to 1500-2000 ms. I read about some settings to the kernel's timecounters that might fix the problem, so I rebuilt a kernel with the HZ=1000 option and rebooted the router. We still had the same problem, so I tried using natd and ipfw. This was even slower. My question is: why could 4 people total connect through a win2k NAT server (using 2 3com 90x 10/100 cards, and a 933MHz PIII) through the same server, and maintain a 15 - 30 ms ping and no packet loss, when with FreeBSD using an 800 MHz athlon with 2 DEC 21140A ethernet cards, or with 2 intel (fxp) cards (we tried both) we maxed out at 2 people connected to that same server we got a lot of packet loss and really high (200-2000ms depending on how many people are connected )??? Thanks a lot ... Kenneth Culver To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Article: Network performance by OS
It's a lot faster on writes with softupdates enabled. FreeBSD will also have journaling filesystems soon. Either way, this was not a very good benchmark. On Sun, 17 Jun 2001, Rayson Ho wrote: > But how much tuning is needed? You can download a kernel patch for VM, > another kernel patch for FS... > > I am sure Linux can be even faster on an SMP machine with a Journaling > FS (XFS, RFS, JFS, ext3, etc). > > Rayson > > --- Kenneth Wayne Culver <[EMAIL PROTECTED]> wrote: > > This is not really a "hardcore networking app" but a custom app > > written by > > the person who did the benchmark. The main reason that FreeBSD came > > in > > last was mostly because the guy didn't mount his filesystem > > correctly. > > > > On Sat, 16 Jun 2001, Matthew Hagerty wrote: > > > > > Greetings, > > > > > > Here is a surprisingly unbiased article comparing OSes running hard > > core > > > network apps. The results are kind of disturbing, with FreeBSD > > (4.2) > > > coming in last against Linux (RH), Win2k, and Solaris (Intel). > > > > > > http://www.sysadminmag.com/articles/2001/0107/0107a/0107a.htm > > > > > > The tests were performed against the TCP/IP implementation on these > > > > > platforms with different system calls. File systems tests (EXT2 > > for Linux, > > > UFS for FreeBSD and Solaris, and NTFS for Windows 2000) were > > performed by > > > creating writing, and reading 10,000 files in the same directory, > > > increasing the file size from 4K to 128K. Tests of various network > > > > > applications based on number of simultaneous connections, > > process-based vs. > > > thread-based, and sync vs. async connection handling were also > > performed. > > > > > > Hope it might be helpful to you... > > > > > > Matthew > > > > > > > > > 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 > > > __ > Do You Yahoo!? > Spot the hottest trends in music, movies, and more. > http://buzz.yahoo.com/ > > 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: Article: Network performance by OS
This is not really a "hardcore networking app" but a custom app written by the person who did the benchmark. The main reason that FreeBSD came in last was mostly because the guy didn't mount his filesystem correctly. On Sat, 16 Jun 2001, Matthew Hagerty wrote: > Greetings, > > Here is a surprisingly unbiased article comparing OSes running hard core > network apps. The results are kind of disturbing, with FreeBSD (4.2) > coming in last against Linux (RH), Win2k, and Solaris (Intel). > > http://www.sysadminmag.com/articles/2001/0107/0107a/0107a.htm > > The tests were performed against the TCP/IP implementation on these > platforms with different system calls. File systems tests (EXT2 for Linux, > UFS for FreeBSD and Solaris, and NTFS for Windows 2000) were performed by > creating writing, and reading 10,000 files in the same directory, > increasing the file size from 4K to 128K. Tests of various network > applications based on number of simultaneous connections, process-based vs. > thread-based, and sync vs. async connection handling were also performed. > > Hope it might be helpful to you... > > Matthew > > > 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: Compaq e500, 3com cardbus card help
What I was saying is that cardbus only works on current. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On 25 Feb 2001, Dag-Erling Smorgrav wrote: > Kenneth Wayne Culver <[EMAIL PROTECTED]> writes: > > On 24 Feb 2001, Dag-Erling Smorgrav wrote: > > > Kenneth Wayne Culver <[EMAIL PROTECTED]> writes: > > > > FreeBSD supports cardbus in -CURRENT, but I wouldn't expect it to ever > > > > support cardbus in 4.x. If you are daring you can get -CURRENT, but from > > > > what I hear right now, it's not working very well. > > > It works just fine, thank you very much, but it takes some > > > hand-holding. > > Must not be cardbus then. > > I beg your pardon? Were you trying to say that -CURRENT does not work > very well, or that Cardbus does not work very well? I assumed the > former, which is partly true (-CURRENT works fine if you keep close > enough track of things to know when it's safe to upgrade and how to > fix or work around whatever bugs you hit). If you meant the latter, I > beg to differ - Cardbus itself works fine and dandy for me. > > DES > -- > Dag-Erling Smorgrav - [EMAIL PROTECTED] > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Compaq e500, 3com cardbus card help
Must not be cardbus then. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On 24 Feb 2001, Dag-Erling Smorgrav wrote: > Kenneth Wayne Culver <[EMAIL PROTECTED]> writes: > > FreeBSD supports cardbus in -CURRENT, but I wouldn't expect it to ever > > support cardbus in 4.x. If you are daring you can get -CURRENT, but from > > what I hear right now, it's not working very well. > > It works just fine, thank you very much, but it takes some > hand-holding. > > DES > -- > Dag-Erling Smorgrav - [EMAIL PROTECTED] > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Compaq e500, 3com cardbus card help
FreeBSD supports cardbus in -CURRENT, but I wouldn't expect it to ever support cardbus in 4.x. If you are daring you can get -CURRENT, but from what I hear right now, it's not working very well. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Thu, 22 Feb 2001 [EMAIL PROTECTED] wrote: > On Thu, Feb 22, 2001 at 10:32:13AM -0500, Justin McKnight wrote: > > I cant figure out to get freebsd 4.2 to recognize > > and enable my 3com cardbus card? > > FreeBSD currently doesn't support cardbus cards. > > -- > Simon Dick[EMAIL PROTECTED] > "Why do I get this urge to go bowling everytime I see Tux?" > > 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: kernel threads
> Are threads on FreeBSD 4.x implemented at the > kernel level? No, as far as I know, those are coming in FreeBSD 5.0 (which won't be out for a while) > > If so, since when (I remember 2.x used MIT-threads, > so I'm guessing at least since 3.x)? > > How can I see for myself that threads are really > implemented at the kernel level? I looked around > in /usr/src/sys/kern, but couldn't find anything > relating to threads there. > They aren't really implemented at the kernel level yet, but something like kernel threads will be in 5.x when it comes out. If you really need kernel threads in FreeBSD take a look at /usr/ports/devel/linuxthreads. Those do kernel threads through a call to rfork I believe. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What's the best PCMCIA Ethernet card?
I've seen cardbus cards do almost a full 100 mbit, but regular pcmcia cards can't do much at all. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sat, 9 Sep 2000, Adam wrote: > Hi, I'd just like to say that I dont think non cardbus cards are capable > of doing more than 10bt speeds even if it talks 100bt. I have not met one > that did and I assume it is a limit of the pcmcia design. Just warning > you not to waste your money on one if you get near 10bt speeds already. > > On Thu, 7 Sep 2000, Stephen Hocking wrote: > > >Preferably 10/100. This old Megahertz CC10BT doesn't seem to be terribly quick. > > > > > > Stephen > >-- > > The views expressed above are not those of PGS Tensor. > > > >"We've heard that a million monkeys at a million keyboards could produce > > the Complete Works of Shakespeare; now, thanks to the Internet, we know > > this is not true."Robert Wilensky, University of California > > > > > > > > > >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 > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD,Posix,Linux Threading - Are they really useable?
Currently as far as I know, there isn't really a way to do this, although much work is being done in -CURRENT to fix this. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Fri, 28 Jul 2000, Bjorn Tornqvist wrote: > Howdy all, > > I must have missed something very importand w.r.t threads under FreeBSD, > here's what I've come up with during the last week: > > PosixThreads are userland threads - if one thread blocks on i/o the > whole process is blocked. Which makes PosixThreads rather useless. > > FreeBSD Kernel-threads (dunno what they are called actually) can't be > used natively!? (Searched the archives and found an explanation that the > only way to access normal kernel SMP-thread functionality is to use > LinuxThreads) > > LinuxThreads: While they are kernel-threads, if one thread receives an > uncought signal, all threads are killed (as they should be), but the > resulting coredump is useless since it only captures the state of the > last-killed-thread (or process or whatever you want to call it. > LinuxThreads seems like just a big hack...). > > How do I use normal kernel-threads that will allow all nonblocked > threads in a process to work concurrently, *and* will generate useful > coredumps? > > There must be a way - I've just haven't found any documentation on the > subject. And yes, I must use threads - fork()ing will only give me the > same trouble as LinuxThreads (a process sharing memory with another > won't give a corefile). > > Please help me with this one. > > //Bjorn Tornqvist, West Entertainment Solutions & Technologies AB > > > 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: cvs-crypto missing from 4.0-stable via cvsup?
Yep, there was a message a few days about this on -current I think. = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sun, 9 Jul 2000, Jim Mercer wrote: > > maybe i just noticed, or maybe something happened recently, but when i cvsup > now, i get a message saying cvs-cryto is non-existent. > > has it been integrated into the standard tree? > > -- > [ Jim Mercer [EMAIL PROTECTED] +1 416 410-5633 ] > [ Reptilian Research -- Longer Life through Colder Blood ] > [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] > > > 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: VM coloring description in NOTES
Alright, well that makes sense.. I guess it speeds things up some too? (I had it enabled for a while, but didn't notice a difference). = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Mon, 26 Jun 2000, Arun Sharma wrote: > On Mon, Jun 26, 2000 at 12:50:41PM -0400, Kenneth Wayne Culver wrote: > > Just curious because I have no experience in this area... but what exactly > > does cache coloring get us... I've never actually gotten a really straight > > answer on this... Thanks > > Read Curt Schimmel's book UNIX systems for modern architectures for an > answer. > > Basically, it ensures that if P1 and P2 are two pages that are allocated > successively (temporal locality), then the first cache line in P1 and > the first cache line in P2 do not compete with each other for the L2 cache. > > -Arun > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: VM coloring description in NOTES
Just curious because I have no experience in this area... but what exactly does cache coloring get us... I've never actually gotten a really straight answer on this... Thanks = | Kenneth Culver | FreeBSD: The best NT upgrade| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Mon, 26 Jun 2000, Arun Sharma wrote: > [This message has also been posted.] > On Mon, 26 Jun 2000 10:42:35 +0100, Koster, K.J. <[EMAIL PROTECTED]> wrote: > > > > > > > > currently -> candidate > > > > > PQ_HUGECACHE PQ_CACHE1024 > > > > > PQ_LARGECACHE PQ_CACHE512 > > > > > PQ_MEDIUMCACHEPQ_CACHE256 > > > > > PQ_NORMALCACHEPQ_CACHE64 > > > > > Hmm. At boot time, the BIOS displayes this square box with a lot of grub in > > it that FreeBSD then proceeds to rediscover. Is there no way to whack the > > BIOS into submission and have it cough up the cache size? > > > > It's probably going to be BIOS-vendor specific *sigh*. Then again, perhaps > > it would be nice to have an interface to some of the more widely used > > bioses. I image you could pry all sorts of tuning information about the > > machine from its clammy little hands. Cache size, cache scheme, memory type. > > For Intel processors, CPUID instruction spits out both L1 and L2 cache > sizes. Perhaps, these things should be made a runtime option than a > compile time option ? > > -Arun > > > 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: subscribe
> subscribe [EMAIL PROTECTED] send this to [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: bktr, unknown PCI device?
It's just another part of the card that doesn't need to have a driver for it to function, take a look at my dmesg: bktr0: mem 0xe9002000-0xe9002fff irq 5 at device 17.0 on pci0 bktr0: Hauppauge Model 61291 D110 Hauppauge WinCast/TV, Philips NTSC tuner. pci0: (vendor=0x109e, dev=0x0878) at 17.1 irq 5 = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sun, 21 May 2000, Wilko Bulte wrote: > I just upgraded one of my boxes to 4.0-stable. Now I seem to have > a 'unknown card' on the PCI, seems related to the bktr. I remember > there was a posting once with a WWW pointer to a PCI-ID database. Alas > I cannot find that pointer :-( > > Any clue what I'm looking at? Fxtv works like a charm BTW > > bktr0: mem 0xe700-0xe7000fff irq 7 at device 10.0 on > pci0 > iicbb0: on bti2c0 > iicbus0: on iicbb0 master-only > smbus0: on bti2c0 > bktr0: Hauppauge Model 61204 AMA > Hauppauge WinCast/TV, Philips PAL I tuner. > pci0: (vendor=0x109e, dev=0x0878) at 10.1 irq 7 > > > -- > Wilko Bulte FreeBSD, 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 > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What are the best gcc optimization options for Pentium 200 MMX
Thanks :-) = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What are the best gcc optimization options for Pentium 200 MMX
Why exactly whould you not touch the -march options? I have had no problems using them, and my system (5.0-CURRENT) seems a little faster with -march=i686. I could be wrong though as I havn't done any exact tests... it just seems a bit more responsive.. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Sat, 8 Apr 2000, Matthew Dillon wrote: > :On Sat, 8 Apr 2000, Alexey N. Dokuchaev wrote: > : > :> AFAIK, Linux Mandrake has it's kernel and userland highly optimized for > :> Pentium architecture. However, they have additional gcc optimization > :> flags turned on by default, including -O3 and -mfast_math. > : > :Can you say "gimmick"? :-) gcc often produces demonstrably broken code for > :optimisation levels higher than -O. > : > :Probably the only useful and safe option apart from -O is the > :-march=pentium/pentiumpro/pentiumii/etc option for using > :processor-specific opcodes and instruction scheduling. > :Kris > > I use -Os for everything. I wouldn't bother with anything else. Someone > ran a bunch of benchmarks with various gcc/egcs options a while back > and, frankly, the top half dozen combinations were so close to each > other performance-wise that it just didn't matter. -Os was in that > group, but also produced significantly smaller binaries. > > I wouldn't touch the -march stuff at all, nor would I use -O3 (which > tries to inline standard static functions verses -O2) - that's useless > on IA32 because call/returns are very fast (I had an argument with John > Dyson about call/return overhead verses an L1 cache miss and > we ran a bunch of timings. I lost the argument :-) call/return won the > race handily). > > > -Matt > Matthew Dillon > <[EMAIL PROTECTED]> > > > 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: Is traditional unixes kernel really stable ?
I don't think that's quite true. I've seen microkernels crash because of bad drivers. I think no matter what, even in a microkernel the drivers have to interface directly to the kernel. I could be wrong but I thought that in a microkernel, drivers were loaded as kernel modules. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Fri, 7 Apr 2000, Gustavo V G C Rios wrote: > Alfred Perlstein wrote: > > > > Some archs (such as i386) allow the OS to set page protections and > > io permission bitmaps that effectively can pretect against problems > > with drivers touching incorrect IO ranges, however... > > > > > > > > Worse yet: What about hardware buggy devices? > > > This could case the entiry system to crash, isn't it ? > > > > Yes, incorrectly programmed hardware either by firmware (on > > chip/board) or by drivers can cause crashes and hardware damage. > > > > That's the point! > Why not a different approach ? > Why not starting a microkernel arch? The microkernel would basically do > just feel tasks, like: > > IPC: managing and routing messages. > Process scheduling. > First level interrupt handling. > > > All other tasks would run in like any other user process, like a fyle > system daemon, process daemon , internet daemon (not inetd), and, of > course, device drivers programs. > > This design, would not let a system crash due to device drivers problems > or even bad hardware desgin. > > What all you think about that ? > > > -- > If you're happy, you're successful. > > > 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: Linux ioctl not implemented error
Oops... not a member of that one... I'll go look then... :-) sorry to have cross posted... = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Tue, 30 Nov 1999, Jordan K. Hubbard wrote: > > Wait... vmware for linux works under FreeBSD now??? or it just runs > > freebsd??? > > You really need to go search the mailing list archives for the > discussion which has just occurred on this topic. Everything from > what it does to how to grab the port and apply the appropriate patches > to your kernel have been discussed in the freebsd-emulation mailing > list and it would be kind of silly to reprise the whole thing all over > again in -hackers. > > - Jordan > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux ioctl not implemented error
Well, I personally was gonna try to get my already installed windows working... :-) = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Wed, 1 Dec 1999, Wilko Bulte wrote: > As Chris Costello wrote ... > > On Tue, Nov 30, 1999, Kenneth Wayne Culver wrote: > > > Wait... vmware for linux works under FreeBSD now??? or it just runs > > > freebsd??? > > > >It runs on FreeBSD. > > More precisely: on -current. > > In the meantime I also gave it a shot on my dual-P100 SMP box. > > This gave me a "VMWare internal monitor error, NullGate on IRQ. gate=0x52" > Along with a suggestion to report a bug to the VMware development team ;-) > > For obvious reasons I'll refrain from the latter > > Question: how do you people get a guest O/S installed without a CD > drive working? > > Wilko > -- > | / o / / _Arnhem, The Netherlands - Powered by FreeBSD - > |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux ioctl not implemented error
Any wierd things I should do to get it running? = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Tue, 30 Nov 1999, Chris Costello wrote: > On Tue, Nov 30, 1999, Kenneth Wayne Culver wrote: > > Wait... vmware for linux works under FreeBSD now??? or it just runs > > freebsd??? > >It runs on FreeBSD. > > -- > |Chris Costello <[EMAIL PROTECTED]> > |What do computer engineers use for birth control? Their personalities. > `--- > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux ioctl not implemented error
Wait... vmware for linux works under FreeBSD now??? or it just runs freebsd??? = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = On Tue, 30 Nov 1999, Wilko Bulte wrote: > I get " LINUX: 'ioctl' fd=0, typ=0x53(S), num=0x13 not implemented " > when attempting to configure a IDE cdrom under VMware (really coold BTW!! > thanks for the port development). > > Somebody close to a Linux box have an idea what this ioctl is supposed > to do? > > Wilko > -- > | / o / / _Arnhem, The Netherlands - Powered by FreeBSD - > |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org > > > 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
