Yes I am, which is why the bulbs in my garage door opener are not CFL - the one in the one bathroom vent fan is the only one with vibration, and that isn't *too* bad (not like a ceiling fan or door opener, anyway).
They do generally recommend nothing below -5F, but I certainly haven't had trouble, and these are OK to use in enclosed outdoor fixtures (no direct weather). YBMV.
I've had shorter life on the 4 CFLs I have in my outdoor lights by the front door and garage (replaced each of them once in the last couple years), but, being in Minnesota, I'm pretty happy that they work as long as they do out there, and I haven't had trouble with them even when it is -10 outside.
I've had a CFL in my bathroom fan/light for a couple of years already, and I expected that one to die sooner due to stress from the fan vibration. I'm quite happy that it hasn't. The other nice thing is that I put a 23W CFL (100W equivalent) where the fixture could only handle a 75W incandescent. More brightness with 1/3 the wattage is a really nice thing
I've had one that died in about 4 months, but that seems the exception rather than the rule. I have ~25 others that have been in service for 1-3 years that haven't been replaced yet, including the three bulbs in the overhead kitchen light, which is on quite a bit, especially in the darker months.
Now all we need is reasonably priced dimmable CFLs, and CFLs that have the same spectrum as the GE Reveal bulbs, and I'd never need anything else*.
> but there's only one division (STD, I kid you not, unless they've renamed it again...) Actually, it is STG (Systems & Technology Group), not STD... I suppose someone noticed the problem with that other acronym...
Wow - it has been a while since I got flamed by the parent posted for posting a small bit of information that is roughly in agreement with said post. There was no intent to discredit your post, just to provide the contrast to what you already stated in case anyone wondered "What would non-SMP multiprocessing be". Clearly the "identical" label in Wikipedia could be interpreted differently, and certainly you took that as a slight against your post. Chill out. If I wanted to discredit anything someone writes, I will use my own words and cite the references, not just paste in some related information... I was providing a little bit of reference for others so they could read and make up their own minds is a totally different thing. Way to take the one word that didn't agree with your post and fly off of the handle.
I think someone needs a little less/more coffee today... or according to your.sig... maybe you just didn't have enough Tequila for breakfast.
To summarize.... Pharmboy: "I think the Symmetrical in SMP means the chips are more or less the same, not that they are in equal numbers"
Tower: (I agree with that statement - why don't I throw some info regarding that in there in support... how about a quick def of ASMP and NUMA too) [info regarding SMP, using the unforgivable 'identical' word inside, but otherwise providing a valid oversimplification for the masses...]
Symmetric Multiprocessing, or SMP, is a multiprocessor computer architecture where two or more identical processors are connected to a single shared main memory. Most common multiprocessor systems today use an SMP architecture. SMP systems allow any processor to work on any task no matter where the data for that task is located in memory; with proper operating system support, SMP systems can easily move tasks between processors to balance the workload efficiently.
Another style is NUMA which dedicates different memory banks to different processors. This allows processors to access memory in parallel, which can dramatically improve memory throughput if the data is localized to specific processes (and thus processors).
Other systems include asymmetric or asymmetrical multiprocessing (ASMP), in which separate specialized processors are used for specific tasks.
Device driver writers should already be comfortable with a multi-core type of environment... when it comes down to it, a single core system behaves like a multi-core for any bus hardware, since the processor and the bus HW can be accessing the same memory at the same time - throw in the ever-present interrupt or non-blocking requests from multiple threads/processes/tasks (your choice) and you already have more than enough elements to create all of the interesting situations... especially if your processor is weakly consistent, so that you don't necessarily see the latest data DMA'd by your adapter.
Oddly enough, among the 5 laptops I've had, none of them has had a pot. All have had the up/down/mute buttons above the keyboard, but never anything near the jacks. Of course, 4 of the 5 were Thinkpads, and the other was an ancient Compaq that may have been before sound was invented.
This helps if you have a company culture where this is more the norm. At work, people bring in donuts, baked goods, fruit, etc to celebrate birthdays, service anniversaries, promotions, children born, etc... This results in people meeting and talking in a relaxed environment with very little room for wrong ideas. Nice way to meet shy people, since many people who wouldn't talk to you otherwise are more comfortable making conversation when they have taken food from you (even if it just being polite, it is better than nothing).
It is all a question of tradeoffs, and for most situations, the tradeoff of a little extra CPU against extra money on an adapter (particularly if it can increase latency) is a no-brainer. This is the same way with crypto offload.
That being said, if you are trying to scale (think a dozen gigabit cards running at high utilization) or a significant number of high-throughput IPSec/VPN clients, then the offload hardware can really show up as a big gain. Even the OTS gigabit ethernet cards these days support offload of some type - usually TCP checksum offload and some support large send offload which save quite a bit on the CPU, since these checksums are cheaper to do in HW than in software.
If you are running a layer on top with its own checksum or CRC (think iSCSI), this can use a very significant amount of CPU, or it can be handled in offload hardware and really save. Again, a multi-proc Xeon can certainly handle a full gig wire with iSCSI with all of the CRCs enabled, but it can't really handle 4 of them without some serious help.
Another issue is that the bulk of older TCP offload engines were firmware based - good path TCP/IP can be handled in ASIC logic instead. Expensive to deisgn and test, but much faster and more capable than a small processor trying to handle those kind of speeds. Great for scaling to many adapters under a single OS image - generally too expensive for a simple home / SOHO type of setup where the demands aren't that great.
As always, everything depends upon what kind of traffic you want to send, how much, and over how many interfaces.
I was so confused by your post, since the only Ninja Gaiden I've ever played was for the NES... X? Y? You got too many darn buttons there:-)
A quick search turns up this list indicating that there were in fact quite a few versions and releases... Of course, the Sega Genesis is still the newest console I've owned, so I'm a little behind.
Well, I think there is a lot to be taken into account. What kind of environment and what language/compiler are you using?
Is this in Java, where the library does contain this function? In C++ is STL or another appropriate library available? Is this an embedded application where there isn't a library available or the compiler can't handle templates? Does the search have to worry about locking (reentrant use by other threads adding/removing nodes while you are searching)? Does the routine need to be stackless or close to it because it may be running in a limited context (interrupt level, on a system timer, etc)?
There are many wheels that all roll forward... some are good for the racetrack, some are good for the country roads, some are good for bicycles, and some are good for earthmovers. They all have differing requirements - no size fits all.
Determining what the requirements are and which wheel to use (or if a reinvent is needed) is something a smart company wants the developers doing. Sometimes the answer is obvious... the rest is why you get paid.
Unless the warm source is a source of water vapor (i.e. the chicken, a human, combustion heater where one of the combustion products is water, etc). An electric heater wouldn't do anything.
>They can't sue them because PODS (Portable On-Demand Storage) isn't in the same realm of consumer goods as the iPod.
I wouldn't be so sure of that - I can store my music collection in either one, though I'm having trouble getting the rest of my furniture into the iPod... maybe PODS should sue Apple claiming that the iPod is hurting the perception of how much can be stored in a pod...
>no one I know have a stand alown DVD, since they breaks so fast.
You know, a few of us at work were talking about this recently, and the funny thing is that my DVD player from 1999, which has since moved from an apartment to two other houses is still almost fully functional (some of the newer discs give it fits, and it willfully does not read CD-R audio discs). Several other people have had more than one DVD player quit on them in one or more ways, the most common being a posessed tray that requires manual intervention (one output or another stopping working was also common). Of course, most of them didn't pay even $35 for the DVD player, and they just replace it with another $30 player. The well built ones actually do last longer (shocking!), and as long as they aren't as old as mine, they actually support all of the reasonable things (MP3, CD-R audio, etc).
That being said, I built a PVR box myself using a hauppauge PVR-500 for capture and GB-PVR and Myth-TV for the interface and such. That is where we play our DVDs in the family room now, so the old DVD player has moved to the TV in our room.
The other, less ambiguous option is something along the lines of 02 August 2006. I know of a couple of friends who always dated things that way... come to think of it, they both had experience in the US Navy. In any case, using the month name and four digit year clears up some of that trouble.
You left out the Pentium M, the predecessor of the Core - 3 parts P!!!, 1 part P4... I'd use that where you have Centrino, since that isn't a CPU... just a chipset.
That's just it - if you are using it to haul things (plywood/drywall/jobsite stuff) and/or as a tow vehicle, they are great. If you don't have a hitch, have only one kid and no dogs, and use it to commute to your desk job every day... that's a little excessive.
My grandfather owned a 1983 Suburban (later on a Chevy Express van), using it to pull his 31' and 35' travel trailers, but when he was at home, he primarily drove the smaller car (currently a Ford Focus) unless he was getting something that wouldn't fit.
There's no reason the sleeves couldn't have small sections of non-treated fabric around the elbow that is bunched under the protective part with a little elastic, allowing some movement even when the rest of the sleeve is solidified. There could be sufficient overlap to prevent open areas. Apply this same idea to the other joints. This would be kind of live the removable skateboarding/rollerblading elbow pads - there are cases in sports and other games where fixed(shell-style) pads/blockers are used on both sides of an elbow or knee, and there is still flexibility.
This shouldn't be an insurmountable problem, really.
Slashdot Mirror
Yes I am, which is why the bulbs in my garage door opener are not CFL - the one in the one bathroom vent fan is the only one with vibration, and that isn't *too* bad (not like a ceiling fan or door opener, anyway).
They do generally recommend nothing below -5F, but I certainly haven't had trouble, and these are OK to use in enclosed outdoor fixtures (no direct weather). YBMV.
>Windows DVRs: Uh... Go go gadget DRM! Aw, crap!
GB-PVR isn't half bad, and can use comskip just as effectively as mythtv. Quite a nice program without needing MCE.
I've had shorter life on the 4 CFLs I have in my outdoor lights by the front door and garage (replaced each of them once in the last couple years), but, being in Minnesota, I'm pretty happy that they work as long as they do out there, and I haven't had trouble with them even when it is -10 outside.
I've had a CFL in my bathroom fan/light for a couple of years already, and I expected that one to die sooner due to stress from the fan vibration. I'm quite happy that it hasn't. The other nice thing is that I put a 23W CFL (100W equivalent) where the fixture could only handle a 75W incandescent. More brightness with 1/3 the wattage is a really nice thing
I've had one that died in about 4 months, but that seems the exception rather than the rule. I have ~25 others that have been in service for 1-3 years that haven't been replaced yet, including the three bulbs in the overhead kitchen light, which is on quite a bit, especially in the darker months.
Now all we need is reasonably priced dimmable CFLs, and CFLs that have the same spectrum as the GE Reveal bulbs, and I'd never need anything else*.
* - and 640K ought to be enough for anybody.
> but there's only one division (STD, I kid you not, unless they've renamed it again...)
Actually, it is STG (Systems & Technology Group), not STD... I suppose someone noticed the problem with that other acronym...
Wow - it has been a while since I got flamed by the parent posted for posting a small bit of information that is roughly in agreement with said post. There was no intent to discredit your post, just to provide the contrast to what you already stated in case anyone wondered "What would non-SMP multiprocessing be". Clearly the "identical" label in Wikipedia could be interpreted differently, and certainly you took that as a slight against your post. Chill out. If I wanted to discredit anything someone writes, I will use my own words and cite the references, not just paste in some related information... I was providing a little bit of reference for others so they could read and make up their own minds is a totally different thing. Way to take the one word that didn't agree with your post and fly off of the handle.
.sig... maybe you just didn't have enough Tequila for breakfast.
I think someone needs a little less/more coffee today... or according to your
To summarize....
Pharmboy: "I think the Symmetrical in SMP means the chips are more or less the same, not that they are in equal numbers"
Tower: (I agree with that statement - why don't I throw some info regarding that in there in support... how about a quick def of ASMP and NUMA too) [info regarding SMP, using the unforgivable 'identical' word inside, but otherwise providing a valid oversimplification for the masses...]
Pharmboy: [rant]
From Wikipedia's SMP entry
Symmetric Multiprocessing, or SMP, is a multiprocessor computer architecture where two or more identical processors are connected to a single shared main memory. Most common multiprocessor systems today use an SMP architecture. SMP systems allow any processor to work on any task no matter where the data for that task is located in memory; with proper operating system support, SMP systems can easily move tasks between processors to balance the workload efficiently.
Another style is NUMA which dedicates different memory banks to different processors. This allows processors to access memory in parallel, which can dramatically improve memory throughput if the data is localized to specific processes (and thus processors).
Other systems include asymmetric or asymmetrical multiprocessing (ASMP), in which separate specialized processors are used for specific tasks.
Device driver writers should already be comfortable with a multi-core type of environment... when it comes down to it, a single core system behaves like a multi-core for any bus hardware, since the processor and the bus HW can be accessing the same memory at the same time - throw in the ever-present interrupt or non-blocking requests from multiple threads/processes/tasks (your choice) and you already have more than enough elements to create all of the interesting situations... especially if your processor is weakly consistent, so that you don't necessarily see the latest data DMA'd by your adapter.
Oddly enough, among the 5 laptops I've had, none of them has had a pot. All have had the up/down/mute buttons above the keyboard, but never anything near the jacks. Of course, 4 of the 5 were Thinkpads, and the other was an ancient Compaq that may have been before sound was invented.
Indeed, since there is no such thing as half duplex gigabit...
This helps if you have a company culture where this is more the norm. At work, people bring in donuts, baked goods, fruit, etc to celebrate birthdays, service anniversaries, promotions, children born, etc... This results in people meeting and talking in a relaxed environment with very little room for wrong ideas. Nice way to meet shy people, since many people who wouldn't talk to you otherwise are more comfortable making conversation when they have taken food from you (even if it just being polite, it is better than nothing).
It is all a question of tradeoffs, and for most situations, the tradeoff of a little extra CPU against extra money on an adapter (particularly if it can increase latency) is a no-brainer. This is the same way with crypto offload.
That being said, if you are trying to scale (think a dozen gigabit cards running at high utilization) or a significant number of high-throughput IPSec/VPN clients, then the offload hardware can really show up as a big gain. Even the OTS gigabit ethernet cards these days support offload of some type - usually TCP checksum offload and some support large send offload which save quite a bit on the CPU, since these checksums are cheaper to do in HW than in software.
If you are running a layer on top with its own checksum or CRC (think iSCSI), this can use a very significant amount of CPU, or it can be handled in offload hardware and really save. Again, a multi-proc Xeon can certainly handle a full gig wire with iSCSI with all of the CRCs enabled, but it can't really handle 4 of them without some serious help.
Another issue is that the bulk of older TCP offload engines were firmware based - good path TCP/IP can be handled in ASIC logic instead. Expensive to deisgn and test, but much faster and more capable than a small processor trying to handle those kind of speeds. Great for scaling to many adapters under a single OS image - generally too expensive for a simple home / SOHO type of setup where the demands aren't that great.
As always, everything depends upon what kind of traffic you want to send, how much, and over how many interfaces.
I was so confused by your post, since the only Ninja Gaiden I've ever played was for the NES... X? Y? You got too many darn buttons there :-)
A quick search turns up this list indicating that there were in fact quite a few versions and releases... Of course, the Sega Genesis is still the newest console I've owned, so I'm a little behind.
Heck, there are often sales where you can get cordless phones (used to be 900 MHz, but now even 2.4GHz) phones for free (especially on black friday).
Well, I think there is a lot to be taken into account. What kind of environment and what language/compiler are you using?
Is this in Java, where the library does contain this function?
In C++ is STL or another appropriate library available?
Is this an embedded application where there isn't a library available or the compiler can't handle templates?
Does the search have to worry about locking (reentrant use by other threads adding/removing nodes while you are searching)?
Does the routine need to be stackless or close to it because it may be running in a limited context (interrupt level, on a system timer, etc)?
There are many wheels that all roll forward... some are good for the racetrack, some are good for the country roads, some are good for bicycles, and some are good for earthmovers. They all have differing requirements - no size fits all.
Determining what the requirements are and which wheel to use (or if a reinvent is needed) is something a smart company wants the developers doing. Sometimes the answer is obvious... the rest is why you get paid.
Something like the Firefly or the Migo, then?
Unless the warm source is a source of water vapor (i.e. the chicken, a human, combustion heater where one of the combustion products is water, etc). An electric heater wouldn't do anything.
>They can't sue them because PODS (Portable On-Demand Storage) isn't in the same realm of consumer goods as the iPod.
I wouldn't be so sure of that - I can store my music collection in either one, though I'm having trouble getting the rest of my furniture into the iPod... maybe PODS should sue Apple claiming that the iPod is hurting the perception of how much can be stored in a pod...
>no one I know have a stand alown DVD, since they breaks so fast.
You know, a few of us at work were talking about this recently, and the funny thing is that my DVD player from 1999, which has since moved from an apartment to two other houses is still almost fully functional (some of the newer discs give it fits, and it willfully does not read CD-R audio discs). Several other people have had more than one DVD player quit on them in one or more ways, the most common being a posessed tray that requires manual intervention (one output or another stopping working was also common). Of course, most of them didn't pay even $35 for the DVD player, and they just replace it with another $30 player. The well built ones actually do last longer (shocking!), and as long as they aren't as old as mine, they actually support all of the reasonable things (MP3, CD-R audio, etc).
That being said, I built a PVR box myself using a hauppauge PVR-500 for capture and GB-PVR and Myth-TV for the interface and such. That is where we play our DVDs in the family room now, so the old DVD player has moved to the TV in our room.
Of course - with three times as many elephants, they are practically everywhere now!
>I am a native English speaker and have said "It's the 2nd of August, 2006" all my life.
Well, then... congratulations - For the first time in your life, you are correct!
The other, less ambiguous option is something along the lines of 02 August 2006. I know of a couple of friends who always dated things that way... come to think of it, they both had experience in the US Navy. In any case, using the month name and four digit year clears up some of that trouble.
You left out the Pentium M, the predecessor of the Core - 3 parts P!!!, 1 part P4... I'd use that where you have Centrino, since that isn't a CPU... just a chipset.
Indeed - the 1973 GTO would have been a better choice (>4000 lbs), or perhaps any of the large sedans from the era.
That's just it - if you are using it to haul things (plywood/drywall/jobsite stuff) and/or as a tow vehicle, they are great. If you don't have a hitch, have only one kid and no dogs, and use it to commute to your desk job every day... that's a little excessive.
My grandfather owned a 1983 Suburban (later on a Chevy Express van), using it to pull his 31' and 35' travel trailers, but when he was at home, he primarily drove the smaller car (currently a Ford Focus) unless he was getting something that wouldn't fit.
Seems like a decent usage model to me.
There's no reason the sleeves couldn't have small sections of non-treated fabric around the elbow that is bunched under the protective part with a little elastic, allowing some movement even when the rest of the sleeve is solidified. There could be sufficient overlap to prevent open areas. Apply this same idea to the other joints. This would be kind of live the removable skateboarding/rollerblading elbow pads - there are cases in sports and other games where fixed(shell-style) pads/blockers are used on both sides of an elbow or knee, and there is still flexibility.
This shouldn't be an insurmountable problem, really.