Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Alfred Perlstein
* Soren Schmidt <[EMAIL PROTECTED]> [010118 00:03] wrote: > It seems John Baldwin wrote: > > > Anyhow, I have asked before to have you guys supply me with > > > a kernel that has been compiled "the right way" and I'll test > > > it out here just to make sure I dont do anything stupid.. > > > > >

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Soren Schmidt
It seems John Baldwin wrote: > > Anyhow, I have asked before to have you guys supply me with > > a kernel that has been compiled "the right way" and I'll test > > it out here just to make sure I dont do anything stupid.. > > > > Just a bare bones kernel, fxp & ata drivers will do nicely for the >

Re: HEADS UP: I386_CPU

2001-01-17 Thread Warner Losh
In message <[EMAIL PROTECTED]> Greg Lehey writes: : > Of course. But of these people, which really need 5.x's features over : > 4.x? : : I thought about that, too. I came to the conclusion "probably not", : but 4.x won't be maintained for ever. Compiler technology maybe? But maintainence and

Re: HEADS UP: I386_CPU

2001-01-17 Thread Warner Losh
In message <[EMAIL PROTECTED]> Will Andrews writes: : Of course. But of these people, which really need 5.x's features over : 4.x? Plus they can still compile I386_CPU by itself, which I'm sure : they already do to keep the kernel size as small as possible. That's a red herring. The new featur

Re: HEADS UP: I386_CPU

2001-01-17 Thread Warner Losh
In message <[EMAIL PROTECTED]> Greg Lehey writes: : Don't forget that the i386 is still a popular CPU for embedded work. : Of course, embedded people will have less of an issue with sysinstall. We have basically an embedded environment and we don't use sysinstall at all for building our CF. And

Re: Debugging SMP instability (was Re: HEADS-UP: await/asleep removal imminent)

2001-01-17 Thread Tor . Egge
> Again I'll offer to run any and all code or patches to -current you > guys can come up with, but I simply dont have the time to sit down > and analyze into details what you have been doing... The enclosed patch implements a virtual NMI pushbutton by programming the IOAPIC to deliver an NMI when

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Boris Popov
On Wed, 17 Jan 2001, Alfred Perlstein wrote: > I have a patch here that removes await/asleep from the kernel API. > > http://people.freebsd.org/~alfred/noasleep.diff > > Matt Dillon implemented alseep/await quite some time ago and the > only thing that's using it is ata. In order to clean up s

Re: HEADS UP: I386_CPU

2001-01-17 Thread Greg Lehey
On Wednesday, 17 January 2001 at 19:16:18 -0500, Will Andrews wrote: > On Wed, Jan 17, 2001 at 04:21:15PM +1100, Greg Lehey wrote: >> Don't forget that the i386 is still a popular CPU for embedded work. >> Of course, embedded people will have less of an issue with sysinstall. > > Of course. But o

Re: Debugging SMP instability (was Re: HEADS-UP: await/asleep removal imminent)

2001-01-17 Thread Matt Dillon
:I did some research on this and am convinced that at least some video cards :would work as memory buffers for KTR logs. Specifically, someone mentioned :to me yesterday that their Matrox Millennium II flashes the X desktop :during startup from a previous invocation across warm boots. (I pursued

Re: HEADS UP: I386_CPU

2001-01-17 Thread Will Andrews
On Wed, Jan 17, 2001 at 04:21:15PM +1100, Greg Lehey wrote: > Don't forget that the i386 is still a popular CPU for embedded work. > Of course, embedded people will have less of an issue with sysinstall. Of course. But of these people, which really need 5.x's features over 4.x? Plus they can st

Re: HEADS UP: I386_CPU

2001-01-17 Thread Greg Lehey
On Tuesday, 16 January 2001 at 9:28:43 -0500, Will Andrews wrote: > On Tue, Jan 16, 2001 at 09:16:14AM -0500, Kenneth Wayne Culver wrote: >> Wont this make installing using sysinstall a bit hard? I know the generic >> kernel includes all the CPU lines, so that all cpu's are recognized... so >> ar

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Alfred Perlstein
* Bosko Milekic <[EMAIL PROTECTED]> [010117 14:35] wrote: > > Alfred Perlstein wrote: > > > Which means we don't have to drop the lock over the socket unless > > we'd block on allocation. > > No. You'd still have to drop it for now. Remember? (Last commit to > uipc_mbuf.c). You have to drop

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Bosko Milekic
Alfred Perlstein wrote: > * Alfred Perlstein <[EMAIL PROTECTED]> [010117 09:24] wrote: > > > > I'm not going to axe it for a few days, this is a really amazing > > API that Matt added, the problem is utility and useage over code > > complexity. > > > > It's just a proposal. > > I found several p

Re: number of processes forked since boot

2001-01-17 Thread Daniel Rock
Hajimu UMEMOTO schrieb: > > Hi, > > I wish to obtain number of processes forked since boot from userland. > So, I made a patch to intend to commit. > Any comment? I have done a similar approach. I was inspired by the "vmstat -s" output of Solaris. Therefor my solution was integrated into the vmm

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread John Baldwin
On 17-Jan-01 Dag-Erling Smorgrav wrote: > Poul-Henning Kamp <[EMAIL PROTECTED]> writes: >> It might be nice with a "How to provide useful info on SMPng >> problems." FAQ somewhere. > > I'd also like a "KTR for fun and profit" FAQ... ktr.9 is next on my todo list of manpages to write. I have se

Re: Zero-copy TCP patches - missing in action?

2001-01-17 Thread Kenneth D. Merry
On Wed, Jan 17, 2001 at 12:59:28 -0800, Jordan Hubbard wrote: > Weren't the zero-copy patches supposed to make it into -current some > time back? I recall a little grumbling over it since it made it > necessary for some other projects to sync up their own work, but > nobody seemed to object in pr

Zero-copy TCP patches - missing in action?

2001-01-17 Thread Jordan Hubbard
Weren't the zero-copy patches supposed to make it into -current some time back? I recall a little grumbling over it since it made it necessary for some other projects to sync up their own work, but nobody seemed to object in principal and zero-copy TCP is a real marketing point if we can actually

subscribe woody@woodwrecker.com

2001-01-17 Thread Mark Ohlund
subscribe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Atomic breakage?

2001-01-17 Thread Peter Jeremy
On 2001-Jan-17 10:28:03 -0800, John Baldwin <[EMAIL PROTECTED]> wrote: > So as long as we keep all >atomically-accessed 64-bit integers within a single page we should be fine for >CX8 on all pentiums should we even want 64-bit atomic ops. This comes free of charge (along with better performance)

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Dag-Erling Smorgrav
Poul-Henning Kamp <[EMAIL PROTECTED]> writes: > It might be nice with a "How to provide useful info on SMPng > problems." FAQ somewhere. I'd also like a "KTR for fun and profit" FAQ... > I have no idea which of all the WITNESS and other options > do what and when they are useful... WITNESS, at

Re: Atomic breakage?

2001-01-17 Thread Garrett Wollman
< said: > There are SMP machines using both 386 and 486 processors. There is > no support in FreeBSD for SMP on pre-Pentium processors. Yes, I well recall the Sequent. I wish for it to remain a memory. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-curr

Re: Atomic breakage?

2001-01-17 Thread Peter Jeremy
On 2001-Jan-17 10:43:10 -0500, Garrett Wollman <[EMAIL PROTECTED]> wrote: >< said: > >> To support multiple masters, you need proper locks. > >On older processors, yes. On processors with the CX8 feature bit set, >you can do it without any sort of locking (indeed, this is a primitive >that semaph

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread John Baldwin
On 17-Jan-01 Poul-Henning Kamp wrote: > > John, > > It might be nice with a "How to provide useful info on SMPng > problems." FAQ somewhere. > > I have no idea which of all the WITNESS and other options > do what and when they are useful... Fair enough. One thing on my todo list is a ktr.9 m

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Soren Schmidt
It seems John Baldwin wrote: > > Anyhow, I have asked before to have you guys supply me with > > a kernel that has been compiled "the right way" and I'll test > > it out here just to make sure I dont do anything stupid.. > > > > Just a bare bones kernel, fxp & ata drivers will do nicely for the >

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Poul-Henning Kamp
John, It might be nice with a "How to provide useful info on SMPng problems." FAQ somewhere. I have no idea which of all the WITNESS and other options do what and when they are useful... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 Fr

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Matt Dillon
:>:... :>: :>:The lock must be unwound becasue we're calling MGETHDR with M_TRYWAIT. :>:If wae used M_TRY'A'WAIT the code would probably look something like :>:this: :> :> The basic premis of using asleep()/await() is to allow you to :> propogate a 'blocking condition' back up to a highe

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, John Baldwin writes: > >On 17-Jan-01 Poul-Henning Kamp wrote: >> >>>Perhaps you can explain how you're able to trigger this instability >>>with a test script? Poul-Henning told me he just needed to do a >>>make -j256 world, I did 10 of them without a problem... >>

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Alfred Perlstein writes: >> > There has to be a way for you guys to get us some reasonable >> > tracebacks or diagnostics instead of just saying "it's broke". >> >> Its close to impossible, the two symptoms I see here are either >> spontanous reboots, or solid han

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread John Baldwin
On 17-Jan-01 Soren Schmidt wrote: > It seems John Baldwin wrote: >> >> On 17-Jan-01 Soren Schmidt wrote: >> > Nothing special, GENERIC kernel with SMP defined will do nicely, running >> > without SMP improves matters but on the fastet machine I'm still getting >> > lockups, but they are rare...

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Alfred Perlstein writes: >* Poul-Henning Kamp <[EMAIL PROTECTED]> [010117 10:25] wrote: >> >> >Perhaps you can explain how you're able to trigger this instability >> >with a test script? Poul-Henning told me he just needed to do a >> >make -j256 world, I did 10 of

Re: Debugging SMP instability (was Re: HEADS-UP: await/asleep removal imminent)

2001-01-17 Thread Soren Schmidt
It seems Jason Evans wrote: > On Wed, Jan 17, 2001 at 07:42:26PM +0100, Soren Schmidt wrote: > > > Basically if you're expecting me or the SMP team to figure out > > > what's going on without more info, you're pretty much out of luck. > > > > See above, not really possible, we have been trying to

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread John Baldwin
On 17-Jan-01 Soren Schmidt wrote: > It seems John Baldwin wrote: >> >> On 17-Jan-01 Soren Schmidt wrote: >> > Nothing special, GENERIC kernel with SMP defined will do nicely, running >> > without SMP improves matters but on the fastet machine I'm still getting >> > lockups, but they are rare...

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread John Baldwin
On 17-Jan-01 Matt Dillon wrote: >:* Alfred Perlstein <[EMAIL PROTECTED]> [010117 09:24] wrote: >:> >:> I'm not going to axe it for a few days, this is a really amazing >:> API that Matt added, the problem is utility and useage over code >:> complexity. >:> >:> It's just a proposal. >: >:I found

Debugging SMP instability (was Re: HEADS-UP: await/asleep removal imminent)

2001-01-17 Thread Jason Evans
On Wed, Jan 17, 2001 at 07:42:26PM +0100, Soren Schmidt wrote: > > Basically if you're expecting me or the SMP team to figure out > > what's going on without more info, you're pretty much out of luck. > > See above, not really possible, we have been trying to find some > (affordable) HW that coul

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Soren Schmidt
It seems John Baldwin wrote: > > On 17-Jan-01 Soren Schmidt wrote: > > Nothing special, GENERIC kernel with SMP defined will do nicely, running > > without SMP improves matters but on the fastet machine I'm still getting > > lockups, but they are rare... > > AHA! Useful info!! GENERIC is quite

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Matt Dillon
:* Alfred Perlstein <[EMAIL PROTECTED]> [010117 09:24] wrote: :> :> I'm not going to axe it for a few days, this is a really amazing :> API that Matt added, the problem is utility and useage over code :> complexity. :> :> It's just a proposal. : :I found several places where it may be useful, bu

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Soren Schmidt
It seems Alfred Perlstein wrote: > > > > > > You and Poul-Henning have to figure out what's going on, no one > > > else is able to reproduce this instability you're talking about. > > > > Oohh you dont read the mailing lists then, there has been plenty > > of reports of hanging -current boxen si

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread John Baldwin
On 17-Jan-01 Poul-Henning Kamp wrote: > >>Perhaps you can explain how you're able to trigger this instability >>with a test script? Poul-Henning told me he just needed to do a >>make -j256 world, I did 10 of them without a problem... > > Then you misunderstood me, I don't have anything in the

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread John Baldwin
On 17-Jan-01 Soren Schmidt wrote: > Nothing special, GENERIC kernel with SMP defined will do nicely, running > without SMP improves matters but on the fastet machine I'm still getting > lockups, but they are rare... AHA! Useful info!! GENERIC is quite close to bloated, so the fact that it is G

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Alfred Perlstein
* Soren Schmidt <[EMAIL PROTECTED]> [010117 10:43] wrote: > It seems Alfred Perlstein wrote: > > > > > > I suggest creative manpower is used to stabilize -current, instead > > > of fine trimming which API's should stay or not... > > > > I started a loop of make -j128 buildworld and buildkernel l

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Alfred Perlstein
* Poul-Henning Kamp <[EMAIL PROTECTED]> [010117 10:25] wrote: > > >Perhaps you can explain how you're able to trigger this instability > >with a test script? Poul-Henning told me he just needed to do a > >make -j256 world, I did 10 of them without a problem... > > Then you misunderstood me, I d

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Soren Schmidt
It seems Alfred Perlstein wrote: > > > > I suggest creative manpower is used to stabilize -current, instead > > of fine trimming which API's should stay or not... > > I started a loop of make -j128 buildworld and buildkernel last > night, I still haven't seen anything odd happen on my hardware.

Re: Atomic breakage?

2001-01-17 Thread Garrett Wollman
< said: > person was referring to: on Pentiums with stepping < 0xc, a cmpxchg8b that > crosses a page boundary triggers an illegel opcode fault rather than a page > fault if the second page is missing. This is (part of) the famous `F00F bug'. -GAWollman To Unsubscribe: send mail to [EMAIL P

Re: Atomic breakage?

2001-01-17 Thread John Baldwin
On 17-Jan-01 Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Robert Drehmel writes: >>In <[EMAIL PROTECTED]>, John Baldwin wrote: >>> Early Pentiums (<= P90) don't support CX8 or so I've heard, which make this >>> slightly more complicated, as for a pentium we would have to use a funct

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Poul-Henning Kamp
>Perhaps you can explain how you're able to trigger this instability >with a test script? Poul-Henning told me he just needed to do a >make -j256 world, I did 10 of them without a problem... Then you misunderstood me, I don't have anything in the dept of SMP hw which can trigger it. -- Poul-He

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Alfred Perlstein
* Soren Schmidt <[EMAIL PROTECTED]> [010117 10:02] wrote: > It seems Alfred Perlstein wrote: > > > >> Peter Wemm and I suspect that ata doesn't need it. Right now I'm > > > >> running several make -j128 buildworlds and buildkernels with this > > > >> patch to catch any ata problems. > > > > > >

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Alfred Perlstein
* Alfred Perlstein <[EMAIL PROTECTED]> [010117 09:24] wrote: > > I'm not going to axe it for a few days, this is a really amazing > API that Matt added, the problem is utility and useage over code > complexity. > > It's just a proposal. I found several places where it may be useful, but I'm not

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Soren Schmidt
It seems Alfred Perlstein wrote: > > >> Peter Wemm and I suspect that ata doesn't need it. Right now I'm > > >> running several make -j128 buildworlds and buildkernels with this > > >> patch to catch any ata problems. > > > > U... > > > > It seems to me from reading the man

Re: Atomic breakage?

2001-01-17 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, Robert Drehmel writes: >In <[EMAIL PROTECTED]>, John Baldwin wrote: >> Early Pentiums (<= P90) don't support CX8 or so I've heard, which make this >> slightly more complicated, as for a pentium we would have to use a function >> pointer that we setup during probe.

Re: Atomic breakage?

2001-01-17 Thread Robert Drehmel
In <[EMAIL PROTECTED]>, John Baldwin wrote: > Early Pentiums (<= P90) don't support CX8 or so I've heard, which make this > slightly more complicated, as for a pentium we would have to use a function > pointer that we setup during probe. Also, during a SMP boot we would have to > panic if CX8 was

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Alfred Perlstein
* Randell Jesup <[EMAIL PROTECTED]> [010117 08:14] wrote: > >It seems Alfred Perlstein wrote: > >> I have a patch here that removes await/asleep from the kernel API. > >> > >> http://people.freebsd.org/~alfred/noasleep.diff > >> > >> Matt Dillon implemented alseep/await quite some time ago and t

Re: HEADSUP! New netgraph code coming

2001-01-17 Thread Dag-Erling Smorgrav
Alfred Perlstein <[EMAIL PROTECTED]> writes: > Since I have no clue as to how they work, it'll have to wait until > someone who knows how it works does it or I have the time to UTSL. MODULE_VERSION(module, version); module is the name of your module. version is the integer version number of your

Re: HEADSUP! New netgraph code coming

2001-01-17 Thread Alfred Perlstein
* Dag-Erling Smorgrav <[EMAIL PROTECTED]> [010117 04:27] wrote: > Alfred Perlstein <[EMAIL PROTECTED]> writes: > > This ought to be documented. > > A good start would be to add example of MODULE_VERSION and > MODULE_DEPEND usage to one of the templates in > /usr/share/examples/kld/. Since I have

Re: Atomic breakage?

2001-01-17 Thread John Baldwin
On 17-Jan-01 Garrett Wollman wrote: > < <[EMAIL PROTECTED]> said: > >> To support multiple masters, you need proper locks. > > On older processors, yes. On processors with the CX8 feature bit set, > you can do it without any sort of locking (indeed, this is a primitive > that semaphores can be

Re: Atomic breakage?

2001-01-17 Thread Garrett Wollman
< said: > Just wondering, can't you use 'LOCK addl' and then use 'LOCK addc'? > add longword, add longword with carry? I know it would be pretty > ugly, but it should work, no? The two bus cycles are independent, so there is a race condition. OTOH, it's a fairly *unlikely* race condition, and

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Randell Jesup
>It seems Alfred Perlstein wrote: >> I have a patch here that removes await/asleep from the kernel API. >> >> http://people.freebsd.org/~alfred/noasleep.diff >> >> Matt Dillon implemented alseep/await quite some time ago and the >> only thing that's using it is ata. In order to clean up some of

Re: Atomic breakage?

2001-01-17 Thread Garrett Wollman
< said: > To support multiple masters, you need proper locks. On older processors, yes. On processors with the CX8 feature bit set, you can do it without any sort of locking (indeed, this is a primitive that semaphores can be built upon). Consider the following: atomic_increment: ; pr

Re: Fan speed control sony vaio lx800 slimtop

2001-01-17 Thread Peter Dufault
I'm giving up on turning down the slimtop fan for now, the only way I can think of to figure out how Sony is turning down the fan is to boot windows, single step through the installation of the device drivers until I know which one is doing it, and then disassemble it to see what they're up to. I

WANTED: testers with VIA 82C686B southbridges!!

2001-01-17 Thread Soren Schmidt
I've committed support for the VIA 82c686B southbridge, but I lack testing with an ATA100 drive to make sure it works as it should. Could somebody try the following if they have this HW setup: for i in 1 2 3 4 do dd if=/dev/adN of=/dev/null bs=512k count=1 # N is you drive number done and mail

Re: VXA tape drive

2001-01-17 Thread Jacques A. Vidrine
On Mon, Jan 15, 2001 at 12:49:29PM -0600, David W. Chapman Jr. wrote: > I checked in current with little luck. Does -current support VXA-1 tape > drives by Ecrix. The site claims that freebsd does, but the only response > by someone that has one says that it won't successfully backup. I've been

Re: HEADSUP! New netgraph code coming

2001-01-17 Thread Dag-Erling Smorgrav
Alfred Perlstein <[EMAIL PROTECTED]> writes: > This ought to be documented. A good start would be to add example of MODULE_VERSION and MODULE_DEPEND usage to one of the templates in /usr/share/examples/kld/. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PR

Re: HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Soren Schmidt
It seems Alfred Perlstein wrote: > Please trim cc's as appropriate. > > I have a patch here that removes await/asleep from the kernel API. > > http://people.freebsd.org/~alfred/noasleep.diff > > Matt Dillon implemented alseep/await quite some time ago and the > only thing that's using it is ata

HEADS-UP: await/asleep removal imminent

2001-01-17 Thread Alfred Perlstein
Please trim cc's as appropriate. I have a patch here that removes await/asleep from the kernel API. http://people.freebsd.org/~alfred/noasleep.diff Matt Dillon implemented alseep/await quite some time ago and the only thing that's using it is ata. In order to clean up some of the schduler and