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
EXPIRE.CTL(5)							File Formats Manual						     EXPIRE.CTL(5)

NAME
       expire.ctl - control file for Usenet article expiration

DESCRIPTION
       The  file  /etc/news/expire.ctl	is  the default control file for the expire(8) program, which reads it at start-up.  Blank lines and lines
       beginning with a number sign (``#'') are ignored.  All other lines should be in one of two formats.

       The first format specifies how long to keep a record of fully-expired articles.	This is useful when a newsfeed intermittently offers older
       news  that  is  not kept around very long.  (The case of very old news is handled by the ``-c'' flag of innd(8).)  There should only be one
       line in this format, which looks like this:
	      /remember/:days
       Where days is a floating-point number that specifies the upper limit to remember a Message-ID, even if the  article  has  already  expired.
       (It does not affect article expirations.)

       Most of the lines in the file will consist of five colon-separated fields, as follows:
	      pattern:modflag:keep:default:purge
       The  pattern  field  is a list of wildmat(3)-style patterns, separated by commas.  This field specifies the newsgroups to which the line is
       applied.  Note that the file is interpreted in order, so that the last line that matches will be used.  This means  that  general  patterns
       (like a single asterisk to set the defaults) should appear before specific group specifications.

       The modflag field can be used to further limit newsgroups to which the line applies, and should be chosen from the following set:
	      M    Only moderated groups
	      U    Only unmoderated groups
	      A    All groups

       The  next  three  fields are used to determine how long an article should be kept.  Each field should be either a number of days (fractions
       like ``8.5'' are allowed) or the word ``never.''  The most common use is to specify the default value for how long  an  article	should	be
       kept.   The  first  and	third fields -- keep and purge -- specify the boundaries within which an Expires header will be honored.  They are
       ignored if an article has no Expires header.  The fields are specified in the file as ``lower-bound default  upper-bound,''  and  they  are
       explained  in this order.  Since most articles do not have explicit expiration dates, however, the second field tends to be the most impor-
       tant one.

       The keep field specifies how many days an article should be kept before it will be removed.  No article in the newsgroup will be removed if
       it  has	been filed for less then keep days, regardless of any expiration date.	If this field is the word ``never'' then an article cannot
       have been kept for enough days so it will never be expired.

       The default field specifies how long to keep an article if no Expires header is present.  If this field is the word ``never'' then articles
       without explicit expiration dates will never be expired.

       The purge field specifies the upper bound on how long an article can be kept.  No article will be kept longer then the number of days spec-
       ified by this field.  All articles will be removed after then have been kept for purge days.  If purge is the word ``never'' then the arti-
       cle will never be deleted.

       It  is  often  useful  to  honor  the  expiration headers in articles, especially those in moderated groups.  To do this, set keep to zero,
       default to whatever value you wish, and purge to never.	To ignore any Expires header, set all three fields to the same value.

       There must be exactly one line with a pattern of ``*'' and a modflags of ``A'' -- this matches all groups and is used to set the expiration
       default.  It should be the first expiration line.

       For example,
	      ##  How long to keep expired history
	      /remember/:5
	      ##  Most things stay for two weeks
	      *:A:14:14:14
	      ##  Believe expiration dates in moderated groups, up to six weeks
	      *:M:1:30:42
	      ##  Keep local stuff for a long time
	      foo.*:A:30:30:30

HISTORY
       Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews.  This is revision 1.15, dated 1996/10/29.

SEE ALSO
       expire(8), wildmat(3).

																     EXPIRE.CTL(5)
All times are GMT -4. The time now is 04:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy