A seriously interesting article about fab times. Post: 302998080

Sponsored Content

Special Forums News, Links, Events and Announcements A seriously interesting article about fab times. Post 302998080 by cb88 on Wednesday 24th of May 2017 10:58:36 PM

05-24-2017

Registered User

That really is a great article, I think one of the ways Intel is going to work around this is multi process chips... so things that aren't as performance intensive are going to be made on older faster cheaper processes, or more optimized processes. So they can make IO optimized drivers for high speed ram interfaces, logic optimized areas for the CPU, and low cost peripheral areas. It is certainly interesting to see companies trying to cope with the limits they are running up against. As well as they can conentrate on making only one sub unit faster per generation... rather than thier tick - tock tock they have been doing. They could do some iteration on aspects of the design without having to worry about parts that won't change getting broken by moving to a new process etc.. .

I've seen some ideas about die stacking of CPU and GPU components instead of chips ram as is done with HBM. So, perhaps they would make tiny very high yeild dies, but stack a bunch of them and run them rather slowly for a higher aggregate speed so they don't fry themselves with heat.

As an aside I've actually seen Daifuku (Wynright is the specific branch I've worked with) equipment installed in several locations where I have been out on an on site setup trip for the equipment my employer makes... very cool cranes (I've seen them shuffling shoe boxes and potato chips) though apparently they shuffle computer chips around as well!

Last edited by cb88; 05-25-2017 at 12:03 AM..

cb88

View Public Profile for cb88

Find all posts by cb88

4 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

An interesting problem

hi!, here is an interesting problem ..... I ftp a file named " my first file.doc" from windows to my HP workstation. Ftp is succesful. The file appears with the same name in my home directory.. But now how do I open this file?? while using Vi or More or other editor, they take only the...

2. Shell Programming and Scripting

interesting problem

Hi, I am new in this forum and I am glad to be a part of it. I have a problem that has two parts: 1/ extract just the timestamp from a filename: for example, I have a file called 'sales20080226144525.txt' and I want to extract just the '20080226144525' part out of it. 2/ Now, take that...

3. AIX

how would you know your server was rebooted 3 times or 5 times

Is there such location or command to know how many times did you reboot your server in that particular day?in AIX.

4. Programming

Problem with implementing the times() function in C (struct tms times return zero/negative values)

Hello, i'm trying to implement the times() function and i'm programming in C. I'm using the "struct tms" structure which consists of the fields: The tms_utime structure member is the CPU time charged for the execution of user instructions of the calling process. The tms_stime structure...

LEARN ABOUT SUSE

sensors-detect

SENSORS-DETECT(8)					      System Manager's Manual						 SENSORS-DETECT(8)

NAME

       sensors-detect - detect hardware monitoring chips

SYNOPSIS

       sensors-detect

DESCRIPTION

       sensors-detect  is  an  interactive  program that will walk you through the process of scanning your system for various hardware monitoring
       chips, or sensors, supported by libsensors(3), or more generally by the lm_sensors tool suite.

       sensors-detect will look for the following devices, in order:

       o      Sensors embedded in CPUs, south bridges and memory controllers.

       o      Sensors embedded in Super I/O chips.

       o      Hardware monitoring chips accessed through ISA I/O ports.

       o      Hardware monitoring chips reachable over the SMBus or more generally any I2C bus on your system.

       As the last two detection steps can cause trouble on some systems, they are normally not attempted if the second detection step led to  the
       discovery  of a Super I/O chip with complete hardware monitoring features.  However, the user is always free to ask for all detection steps
       if so is his/her wish. This can be useful if a given system has more than one hardware monitoring chip. Some vendors are known to do  this,
       most notably Asus and Tyan.

WARNING

       sensors-detect  needs  to access the hardware for most of the chip detections.  By definition, it doesn't know which chips are there before
       it manages to identify them. This means that it can access chips in a way these chips do not like,  causing  problems  ranging  from  SMBus
       lockup to permanent hardware damage (a rare case, thankfully.)

       The  authors  made  their  best	to make the detection as safe as possible, and it turns out to work just fine in most cases, however it is
       impossible to guarantee that sensors-detect will not lock or kill a specific system. So, as a rule of thumb, you should	not  run  sensors-
       detect  on  production  servers,  and you should not run sensors-detect if can't afford replacing a random part of your system. Also, it is
       recommended to not force a detection step which would have been skipped by default, unless you know what you are doing.

SEE ALSO

       sensors(1), libsensors(3)

AUTHOR

       Frodo Looijaard and Jean Delvare

lm-sensors 3							   December 2008						 SENSORS-DETECT(8)