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

cvtbatch

CVTBATCH(8)						    InterNetNews Documentation						       CVTBATCH(8)

NAME

       cvtbatch - Convert Usenet batch files to INN format

SYNOPSIS

       cvtbatch [-w items]

DESCRIPTION

       cvtbatch reads standard input as a sequence of lines, converts each line, and writes it to standard output.  It is used to convert simple
       batch files that contain just the storage API token of an article to INN batch files that contain additional information about each
       article.

       Each line is taken as a storage API token indicating a Usenet article.  Only the first word of each line is parsed; anything following
       whitespace is ignored.  Lines not starting with a valid token are also silently ignored.

       If the input file consists of a series of message-IDs, then use grephistory with the -s flag piped into cvtbatch.

OPTIONS

       -w items
	   The -w flag specifies how each output line should be written.  The items for this flag should be chosen from the "W" flag items as
	   specified in newsfeeds(5).  They may be chosen from the following set:

	       b    Size of the article in bytes.
	       f    Storage API token of the article (same as "n").
	       m    Article message-ID.
	       n    Storage API token of the article.
	       t    Arrival time of the article as seconds since epoch.

	   The default is "nm", that is to say the storage API token followed by the message-ID of the article.

HISTORY

       Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews.  Converted to POD by Julien Elie.

       $Id: cvtbatch.pod 8776 2009-11-15 09:24:06Z iulius $

SEE ALSO

       grephistory(1), newsfeeds(5).

INN 2.5.2							    2009-11-15							       CVTBATCH(8)