Article: Escape From the Planet of x86
By: Bill Todd (billtodd.delete@this.metrocast.net), June 18, 2003 11:28 pm
Room: Moderated Discussions
Paul DeMone (pdemone@igs.net) on 6/18/03 wrote:
---------------------------
>Bill Todd (billtodd@metrocast.net) on 6/18/03 wrote:
>---------------------------
>[...]
>>And I never suggested in the least that it did. Though it is interesting to note
>>that it doesn't seem to clock all that much *faster* than 1.5 GHz even if you raise
>>the voltage all the way up to 1.5v (where they'd seem hard-pressed to get more than
>>about 1.6 GHz out of it with a decent margin of safety, if I understand the chart correctly).
>
>Intel is free to chose the sample it schmoo'd from anywhere in the process. Can
>you think of good strategic reasons for and against choosing parts in the slow vs
>typical vs fast processing range for public disclosure prior to product introduction?
>Is Intel more interested in exciting customers who rarely get excited about clock
>rates anyway or avoiding tipping its hand to its competitors?
So when you don't care for what *Intel* says about its own product you implicitly try to discredit it? One might almost think you're getting a bit defensive about some of your earlier statements that just don't seem to be supported by the emerging evidence.
>
>>
>>However, that interesting .pdf (thanks for the pointer) does support my understanding
>>that Madison indeed consumes 130 W at 1.3v (and 1.5 GHz).
>
>Explain how.
It's not all that hard to devine had you bothered to read the cited reference, Paul: it's right there in black and white on page 5. Is there anything else you'd like to have me read for you?
>
>> So how the power consumption
>>could be halved by reducing the voltage only 15% and the frequency only 13% (to
>>1.1v and 1.3 GHz, as you suggest below) remains unclear to me (though I don't have
>>any problem believing that a 1 GHz part - possibly at even lower voltage - might
>>halve the power requirement).
>
>If you start with faulty assumptions things only go down hill.
A statement you might want to take to heart yourself. Meanwhile, please identify any faulty assumptions I might have made.
A shmoo plot tells
>you absolutely nothing about power
Duh. Since my reference was to the .pdf rather than specifically to the schmoo plot, that observation seems rather pointless.
and is only a single sample anecdotal hint
>about the frequency yield. We don't know anything about which stepping this is
>compared to the production device. Similar faulty assumptions were the basis
>of apparent good sounding arguments in the past why Willamette would never
>scale above 1.7 GHz and why Northwood would never get above 2.5 GHz.
That's right. When it really comes right down to it, we just don't *know* anything (well, it appears that this was an ISSCC 2003 presentation, for what that may be worth). For all I know you could be Rob Young masquerading as someone more competent while talking up Itanic: you certainly sound that way right now.
- bill
---------------------------
>Bill Todd (billtodd@metrocast.net) on 6/18/03 wrote:
>---------------------------
>[...]
>>And I never suggested in the least that it did. Though it is interesting to note
>>that it doesn't seem to clock all that much *faster* than 1.5 GHz even if you raise
>>the voltage all the way up to 1.5v (where they'd seem hard-pressed to get more than
>>about 1.6 GHz out of it with a decent margin of safety, if I understand the chart correctly).
>
>Intel is free to chose the sample it schmoo'd from anywhere in the process. Can
>you think of good strategic reasons for and against choosing parts in the slow vs
>typical vs fast processing range for public disclosure prior to product introduction?
>Is Intel more interested in exciting customers who rarely get excited about clock
>rates anyway or avoiding tipping its hand to its competitors?
So when you don't care for what *Intel* says about its own product you implicitly try to discredit it? One might almost think you're getting a bit defensive about some of your earlier statements that just don't seem to be supported by the emerging evidence.
>
>>
>>However, that interesting .pdf (thanks for the pointer) does support my understanding
>>that Madison indeed consumes 130 W at 1.3v (and 1.5 GHz).
>
>Explain how.
It's not all that hard to devine had you bothered to read the cited reference, Paul: it's right there in black and white on page 5. Is there anything else you'd like to have me read for you?
>
>> So how the power consumption
>>could be halved by reducing the voltage only 15% and the frequency only 13% (to
>>1.1v and 1.3 GHz, as you suggest below) remains unclear to me (though I don't have
>>any problem believing that a 1 GHz part - possibly at even lower voltage - might
>>halve the power requirement).
>
>If you start with faulty assumptions things only go down hill.
A statement you might want to take to heart yourself. Meanwhile, please identify any faulty assumptions I might have made.
A shmoo plot tells
>you absolutely nothing about power
Duh. Since my reference was to the .pdf rather than specifically to the schmoo plot, that observation seems rather pointless.
and is only a single sample anecdotal hint
>about the frequency yield. We don't know anything about which stepping this is
>compared to the production device. Similar faulty assumptions were the basis
>of apparent good sounding arguments in the past why Willamette would never
>scale above 1.7 GHz and why Northwood would never get above 2.5 GHz.
That's right. When it really comes right down to it, we just don't *know* anything (well, it appears that this was an ISSCC 2003 presentation, for what that may be worth). For all I know you could be Rob Young masquerading as someone more competent while talking up Itanic: you certainly sound that way right now.
- bill
Topic | Posted By | Date |
---|---|---|
New Silicon Insider Article | David Kanter | 2003/06/17 03:39 PM |
Srockholm Syndrome | anonymous | 2003/06/17 03:50 PM |
Srockholm Syndrome | Nate Begeman | 2003/06/17 04:32 PM |
Srockholm Syndrome | anonymous | 2003/06/18 02:23 PM |
Srockholm Syndrome | Scott Robinson | 2003/06/20 08:25 AM |
New Silicon Insider Article | Bill Todd | 2003/06/17 09:51 PM |
New Silicon Insider Article | Alberto | 2003/06/18 07:29 AM |
New Silicon Insider Article | José Javier Zarate | 2003/06/18 10:16 AM |
New Silicon Insider Article | Bill Todd | 2003/06/18 03:10 PM |
New Silicon Insider Article | Nate Begeman | 2003/06/18 03:25 PM |
New Silicon Insider Article | Tvar' | 2003/06/18 03:41 PM |
New Silicon Insider Article | Alberto | 2003/06/18 03:58 PM |
New Silicon Insider Article | Tvar' | 2003/06/18 04:04 PM |
New Silicon Insider Article | Alberto | 2003/06/18 04:24 PM |
New Silicon Insider Article | Tvar' | 2003/06/18 04:32 PM |
New Silicon Insider Article | Paul DeMone | 2003/06/18 04:13 PM |
New Silicon Insider Article | Tvar' | 2003/06/18 04:23 PM |
New Silicon Insider Article | mas | 2003/06/18 04:11 PM |
New Silicon Insider Article | Alberto | 2003/06/18 03:45 PM |
New Silicon Insider Article | Bill Todd | 2003/06/18 11:46 PM |
New Silicon Insider Article | David Wang | 2003/06/19 12:13 AM |
New Silicon Insider Article | Bill Todd | 2003/06/19 01:14 AM |
New Silicon Insider Article | David Wang | 2003/06/19 10:52 AM |
New Silicon Insider Article | Paul DeMone | 2003/06/18 04:04 PM |
New Silicon Insider Article | Bill Todd | 2003/06/18 11:28 PM |
New Silicon Insider Article | Paul DeMone | 2003/06/19 12:43 AM |
New Silicon Insider Article | Rob Young | 2003/06/19 10:23 AM |
New Silicon Insider Article | Bill Todd | 2003/06/19 04:53 PM |
New Silicon Insider Article | David Wang | 2003/06/18 11:29 PM |
New Silicon Insider Article | Bill Todd | 2003/06/19 12:03 AM |
New Silicon Insider Article | José Javier Zarate | 2003/06/19 05:33 AM |
New Silicon Insider Article | mas | 2003/06/19 06:37 AM |
New Silicon Insider Article | Bill Todd | 2003/06/19 04:40 PM |
New Silicon Insider Article | David Wang | 2003/06/19 05:25 PM |
New Silicon Insider Article | Bill Todd | 2003/06/19 06:00 PM |
New Silicon Insider Article | Alberto | 2003/06/19 06:29 PM |
New Silicon Insider Article | Speedy | 2003/06/19 06:48 PM |
New Silicon Insider Article | Alberto | 2003/06/20 04:57 AM |
New Silicon Insider Article | David Wang | 2003/06/19 06:52 PM |
New Silicon Insider Article | Bill Todd | 2003/06/19 09:00 PM |
New Silicon Insider Article | Anonymous | 2003/06/20 02:20 AM |
New Silicon Insider Article | Paul DeMone | 2003/06/20 09:11 AM |
New Silicon Insider Article | Anonymous | 2003/06/22 04:48 PM |
New Silicon Insider Article | Paul DeMone | 2003/06/22 05:49 PM |
New Silicon Insider Article | Vincent Diepeveen | 2003/06/22 06:25 PM |
New Silicon Insider Article | José Javier Zarate | 2003/06/22 07:55 PM |
New Silicon Insider Article | Anonymous | 2003/06/23 09:59 AM |
New Silicon Insider Article | Paul DeMone | 2003/06/19 07:53 PM |
New Silicon Insider Article | Bill Todd | 2003/06/19 08:53 PM |
New Silicon Insider Article | David Wang | 2003/06/19 09:08 PM |
New Silicon Insider Article | Bill Todd | 2003/06/20 02:28 AM |
New Silicon Insider Article | David Wang | 2003/06/20 11:35 AM |
New Silicon Insider Article | Paul DeMone | 2003/06/20 12:29 PM |
New Silicon Insider Article | Bill Todd | 2003/06/20 07:10 PM |
New Silicon Insider Article | Marc M. | 2003/06/21 06:06 AM |
New Silicon Insider Article | Bill Todd | 2003/06/21 12:07 PM |
New Silicon Insider Article | Bill Todd | 2003/06/20 07:01 PM |
New Silicon Insider Article | David Wang | 2003/06/20 07:52 PM |
New Silicon Insider Article | Bill Todd | 2003/06/20 08:53 PM |
New Silicon Insider Article | David Wang | 2003/06/20 09:14 PM |
New Silicon Insider Article | Vincent Diepeveen | 2003/06/20 09:52 PM |
New Silicon Insider Article | Marc M. | 2003/06/21 08:16 AM |
New Silicon Insider Article | Vincent Diepeveen | 2003/06/22 05:24 PM |
New Silicon Insider Article | Singh, S.R. | 2003/06/21 04:39 AM |
New Silicon Insider Article | David Wang | 2003/06/21 09:10 AM |
IPF Compilers | Nate Begeman | 2003/06/21 10:10 AM |
IPF Compilers | Paul DeMone | 2003/06/21 10:45 AM |
Use ILP to extract more ILP | Paul DeMone | 2003/06/20 11:48 PM |
New Silicon Insider Article | Paul DeMone | 2003/06/20 09:06 AM |
New Silicon Insider Article | Singh, S.R. | 2003/06/20 10:41 AM |
New Silicon Insider Article | David Kanter | 2003/06/21 04:34 PM |
New Silicon Insider Article | Paul DeMone | 2003/06/22 03:22 PM |
New Silicon Insider Article | Bill Todd | 2003/06/20 06:52 PM |
New Silicon Insider Article | Marc M. | 2003/06/21 08:54 AM |
New Silicon Insider Article | Daniel Gustafsson | 2003/06/19 12:12 PM |
New Silicon Insider Article | Paul DeMone | 2003/06/20 03:20 PM |
New Silicon Insider Article | Bryan Gregory | 2003/06/20 02:14 PM |
New Silicon Insider Article | mas | 2003/06/20 02:43 PM |
New Silicon Insider Article | Paul DeMone | 2003/06/25 11:29 AM |
New Silicon Insider Article | José Javier Zarate | 2003/06/25 11:43 AM |
New Silicon Insider Article | Paul DeMone | 2003/06/25 11:52 AM |
lol, amazing coincidence :-) (NT) | mas | 2003/06/25 04:15 PM |
New Silicon Insider Article | Yoav | 2015/04/01 04:43 AM |