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

history

HISTORY(5)							File Formats Manual							HISTORY(5)

NAME

       history - record of current and recently expired Usenet articles

DESCRIPTION

       The  file  <pathdb in inn.conf>/history keeps a record of all articles currently stored in the news system, as well as those that have been
       received but since expired.  In a typical production environment, this file will be many megabytes.

       The file consists of text lines.  Each line corresponds to one article.	The file is normally kept sorted in the order  in  which  articles
       are  received,  although  this  is not a requirement.  Innd(8) appends a new line each time it files an article, and expire(8) builds a new
       version of the file by removing old articles and purging old entries.

       Each line consists of two or three fields separated by a tab, shown below as 	:
	      [Hash]	     	   date
	      [Hash]	     	   date	 	   token

       The Hash field is the ASCII representation of the hash of the Message-ID header.  This is directly used for the key of the dbz(3).

       The date field consists of three sub-fields separated by a tilde.  All sub-fields are the text representation  of  the  number  of  seconds
       since  the  epoch -- i.e., a time_t; see gettimeofday(2).  The first sub-field is the article's arrival date.  If copies of the article are
       still present then the second sub-field is either the value of the article's Expires header, or a hyphen if no expiration date  was  speci-
       fied.   If  an article has been expired then the second sub-field will be a hyphen.  The third sub-field is the value of the article's Date
       header, recording when the article was posted.

       The token field is a token of the article.  This field is empty if the article has been expired.

       For example, an article whose Message-ID was <7q2saq$sal$1@isrv4.pa.vix.com>, posted on 26 Aug 1999 08:02:34 GMT and  recieved  at  26  Aug
       1999 08:06:54 GMT, could have a history line (broken into three lines for display) like the following:
	      [E6184A5BC2898A35A3140B149DE91D5C]  	
		  935678987~-~935678821  	
		  @030154574F00000000000007CE3B000004BA@

       In  addition to the text file, there is a dbz(3) database associated with the file that uses the Message-ID field as a key to determine the
       offset in the text file where the associated line begins.  For historical reasons, the key includes the trailing    byte  (which  is  not
       stored in the text file).

HISTORY

       Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews.  This is revision 3782, dated 2000-08-17.

SEE ALSO

       dbz(3), expire(8), inn.conf(5), innd(8), makehistory(8).

																	HISTORY(5)