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
Old 05-24-2017
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..
 

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... (5 Replies)
Discussion started by: jyotipg
5 Replies

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... (5 Replies)
Discussion started by: ChicagoBlues
5 Replies

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. (3 Replies)
Discussion started by: kenshinhimura
3 Replies

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... (1 Reply)
Discussion started by: g_p
1 Replies
snsplit,v0.3.8(8)					      System Manager's Manual						 snsplit,v0.3.8(8)

NAME
snsplit - split an article stream into individual articles SYNOPSIS
snsplit [-r] [field... -] prog... DESCRIPTION
snsplit reads an article stream from descriptor 0 and splits it into separate articles, invoking prog... on each, with the article ava- iable on descriptor 0. This is useful as a quick-and-dirty way of filtering an article stream. The incoming article stream is expected to be in wire format, with lines ending in CRLF, leading dots doubled, and delimited by a dot on a line by itself. The article presented to prog... will have lines that end in a bare newline, will have all header lines unfolded, leading dots will be unstuffed, and the article will be terminated by end-of-file. ARGUMENTS
prog... is the program (with arguments) to run on each article. If prog... exits with any kind of failure, snsplit aborts. field...- are optional header field names. If these are specified, the value of the first header field of that name will be exported into the environment. This field... list must be terminated by the hyphen. See also ENVIRONMENT below. OPTIONS
-r Expect input articles in rnews batch format instead. ENVIRONMENT
snsplit sets some environment variables. If the environment already contains these variables, they will be overwritten. SEQUENCE If already set to a positive value, it is incremented for the first article. If it isn't set, is set to one for the first article. Thereafter it is incremented for each subsequent article. The value is always a 6-digit number with leading zeroes, and it can roll over. BYTES contains the size of the current article. HEAD_LINES The number of lines in the head of the article, excluding the blank separator line. BODY_LINES The number of lines in the body of the article, excluding the blank separator line. FLD_FIELD If any fields are specified on the command line, where field is the name of an article header field, then FLD_FIELD will be set to the value of field, where FIELD is the same as field but with lower case characters changed to upper case, and all hyphens changed to underscores. Confusing? If field is message-id, then FLD_MESSAGE_ID will be set to the value of the first Message-ID field in the current article, if there is one. EXIT CODES
snsplit exits 0 on success, 1 on usage error, 2 on system error, and 3 on article format error. If prog... exits with other than 0, snsplit will also exit that value. N.B. Harold Tay snsplit,v0.3.8(8)
All times are GMT -4. The time now is 12:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy