Interesting read about upcoming K9 processors

  • Thread starter Thread starter Yousuf Khan
  • Start date Start date
George Macdonald said:
George Macdonald wrote:

True but those people are among the most arrogant on the planet. They
think they can get away with it and maybe they can. There are signs that
AMD64 supply is tightening up and prices are staying relatively high. It's
probable that the bottom line is that M$ figures AMD64 volume can never
reach what they call "volume".

Interesting, because I was just reading an article from yesterday saying AMD
just dropped the price of the A64 by up to 30% (depending on the model).

http://www.theregister.co.uk/2004/07/26/amd_prices/

That readjustment, which also included raised prices for a cpuple of
models, was on Monday and I'm going by prices paid for recent "shopping".
The price *has* been holding quite well for AMD64 CPUs compared with their
historical curves and even Intel's - even at the old higher prices, they
were definitely in quite tight supply.

Rgds, George Macdonald

"Just because they're paranoid doesn't mean you're not psychotic" - Who, me??
 
Kinda curious where you found the reports on SP2 RC2. Have three systems
running it, with zero problems.

I think he meant the problems MS have making it work - wider issues than
most people will come across. If there weren't any problems it would've
been released many months ago.

Cheers
Anton
 
Tony Hill said:
Sun currently has 64-bit Solaris for Opteron scheduled for Dec. of
this year. Word so far is that they are pretty much right on schedule
and that the OS is up and running in their labs.

I'd never heard of that until now. Doing a Yahoo search only revealed a few
articles from 2003 (too old now to be really useful), and some Sun articles
being suitably vague ("real soon now"). You got something to link to?
FWIW I don't think the MS delay is simply an issue of drivers.
They've also delayed Win2003 SP1 for apparently the same reason as
their delay of WinXP 64-bit. All of this actually seems to tie back
in to WinXP (32-bit) SP2, which is continuously being pushed back.
All the future OSes are going to be built off the SP2 code-base and
Microsoft seems to be having no end of problems getting this update
out.

For those that aren't familiar with WinXP SP2, it is a pretty
significant change to WinXP (many have referred to it more as "WinXP
Second Edition" rather than just a service pack). Lots of positive
changes with regards to the basic security concept of the system, but
MS seems to be having HUGE problems making it work. Reports from the
recently released "Release Candidate 2" suggest that this is still
definitely beta software (certainly not an actual candidate to be
released). I suspect that until MS gets these sorted out they aren't
going to try to push the other new OSes and service packs out.

It's possible that the NX protected pages are breaking more apps than
initially thought.

Yousuf Khan
 
Sander said:
Well... I would imaghine it depends a lot on how throughout work they want
to make of it. With teh IL32P64 model they are using, almost no extra work
might be needed for an initial api and lilbrary conversion.

That model is surely going to make the famous trick of using xor
to build doubly-linked lists more interesting. (Unless they used
a typedef to mean "an integer that can hold a pointer". They
certainly wouldn't have been using "long long" for that purpose in
the 16- or 32-bit days.)

Weren't we just discussing "issues with C and pointers" :-)
 
I don't think so. More likely Windows is a nightmare to code/modify. Some
people like conspiracy theories, however. :-).

Moi? Come on. Either M$ is incompetent or they're holding back. You
choose!
Linux isn't Windows,

No (micro)$hit! Linux doesn't have the corporate skulldugery impeeding
its progress. There is a market, it will fill it. ...kinda like AMD
these days.
and therefore is a completely different argument.
Sun found religion for the same reason most others do... impending
death! <g>.

Perhaps not impending.
Unlike Power, which will dominate everywhere, right?

Well, there is no longer a "Power" architecture (you really should
know by now that that is a silly marketeer's term). If you're
alluding to "PowerPC", well it seems to be invading from top to bottom;
IBM's Power(TM) and blades, Apple G5 and XServe, Nintendo,
PlayStation3, X-Box2, and a ton of embedded stuff.


Yeah, it seems to be doing a tad better than Itanic! ;-)

No politics here!!! ;-).

Who me? o;-)

BTW, Dean a decent newsreader is in order. Lookout sucks.
 
Keith said:
Moi? Come on. Either M$ is incompetent or they're holding back. You
choose!

How many Windows programmers does it take to change a lightbulb? ;-).
No (micro)$hit! Linux doesn't have the corporate skulldugery impeeding
its progress. There is a market, it will fill it. ...kinda like AMD
these days.

Far too early to tell for AMD, unfortunately. 15% marketshare is a bit less
than their best. Server segment share is not too shabby, but still a long
way to go to be compared to Linux.
Perhaps not impending.

Hell, they're not only porting Solaris to x86-64, but are considering
PowerWhatever/IPF as well. Sun sees the light, and it is coming from
somewhere else. ;-).
Well, there is no longer a "Power" architecture (you really should
know by now that that is a silly marketeer's term). If you're
alluding to "PowerPC", well it seems to be invading from top to bottom;
IBM's Power(TM) and blades, Apple G5 and XServe, Nintendo,
PlayStation3, X-Box2, and a ton of embedded stuff.


Yeah, it seems to be doing a tad better than Itanic! ;-)

It has impressive numbers, for sure. What happened to SPEC int, though?
Who me? o;-)

BTW, Dean a decent newsreader is in order. Lookout sucks.

So I've heard. I haven't made the investment (timewise) to put Linux on,
and don't have the funds to upgrade my K7 box to a K8 yet. I figure to do
that all at the same time - will you stop your whining then? :-) Besides,
I keep hoping IBM will let me play with a Thinkpad with FLEX-ES and z/OS on
it (or they approve z/OS to run on Hercules along with an affordable
single-user license) so I can pretend I am on a *real* computer while at
home... <g>.

Regards,
Dean
 
Pleasant said:
Sure it is a nasty problem and I do understand that. But, I'm talking
about the total amount of work for Microsoft here.

I think this is a serial problem, time to solution is at least the time
to solution for the most dificult problem, or more depending on how many
things can be done in parallel.
How many people do you think would need to be working on the kernel
development for this particular problem as opposed to migrating the
entire Win32 API and attendant APIs such as DirectX to 64-bit? That was
my point. The real world is more than some academic abstraction that
"NUMA is hard" and so on. The real world is about delivering a complete
shrink-wrapped 64-bit Windows XP I can buy.

People are still doing graduate thesis on NUMA, it's not clear that more
people will mean shorter time to solution. The first cut may settle for
being stable and running well where Ntask <= Ncpu. Getting it wrong
means bigtime bad throughput, which is probably an issue, since there
are more mature Linux and Solaris (I'm told) models as competition.

I think the rest of the steps are pretty well understood and can be
solved in reasonable time. Or course things like keeping the CPU number
in a byte will need work ;-)
 
How many Windows programmers does it take to change a lightbulb? ;-).

That's easy; none. But that certainly doesn't answer the question
(quite the opposite, in fact). ;-)
Far too early to tell for AMD, unfortunately. 15% marketshare is a bit less
than their best. Server segment share is not too shabby, but still a long
way to go to be compared to Linux.

Linux has 15%? The server segment is not too shabby, but...
Hell, they're not only porting Solaris to x86-64, but are considering
PowerWhatever/IPF as well. Sun sees the light, and it is coming from
somewhere else. ;-).

When one has so many lamps to choose from, why would one keep lamp-
designers on payroll?
It has impressive numbers, for sure. What happened to SPEC int, though?

Don't look at me! I didn't take it! ...which SPEC Int were you
referring to?
So I've heard. I haven't made the investment (timewise) to put Linux on,
and don't have the funds to upgrade my K7 box to a K8 yet. I figure to do
that all at the same time - will you stop your whining then? :-)

Linux isn't needed to get a decent reader. Agent works fine under Win,
though I prefer Gravity. There are many choices, most *free*, and all
better than outhouse. It doesn't take a lot of time to switch. It took
me an hour or so to switch from Win/Gravity to Linux/PAN.
Besides,
I keep hoping IBM will let me play with a Thinkpad with FLEX-ES and z/OS on
it (or they approve z/OS to run on Hercules along with an affordable
single-user license) so I can pretend I am on a *real* computer while at
home... <g>.

I can't remember the last time I logged onto a 'Z' system. Must be
close to five years for VM (I've long forgotten my password) and
fifteen for MVS.
 
Dean Kent's last words before the Sword of Azrial plunged through his body
were:
So I've heard. I haven't made the investment (timewise) to put Linux on,
and don't have the funds to upgrade my K7 box to a K8 yet. I figure to do
that all at the same time - will you stop your whining then? :-) Besides,
I keep hoping IBM will let me play with a Thinkpad with FLEX-ES and z/OS on
it (or they approve z/OS to run on Hercules along with an affordable
single-user license) so I can pretend I am on a *real* computer while at
home... <g>.

You can get different email and news readers for windows too, ya know
 
I though Solaris 9 something was an option on the Opterons?

The 32-bit version of Solaris 9 is indeed an option on the Opterons,
but that's not really what we're interested in here. It's the 64-bit
version of Solaris 10 that people are waiting for.
 
Kinda curious where you found the reports on SP2 RC2.
Have three systems running it, with zero problems.

I'd like to read the reports so I can tell what problems
to look for and test.

The biggest issue I've been hearing about (admittedly mostly
second-hand) seems to be with actually getting the service pack
installed. A lot of people seem to have had all sorts of problems,
ranging from changing settings and breaking things right up to making
the machines blue-screen and not boot.

Once installed I have heard of a few application compatibilities,
particularly with software that does kind of funky things with
hardware (some CD burning applications, virtual drives, etc.). Some
of these problems are probably almost by design, ie they tie in to the
new security features of SP2, but in the process break compatibility
with some odd-ball software. This isn't entirely a bad thing, MS
really NEEDED to break compatibility with some software in order to
improve their security, but there do still seem to be a few rough
edges to be worked out.

Of course, that being said, "release candidates" are never really
actual candidates for release, so I shouldn't really be directing too
much blame at MS for this one. They're really just late-beta releases
that are going through their final testing and bug-fixing before an
actual release candidate can be created. In this regards RC2 seems
fine. Hopefully MS will get the rough edges smoothed out and get SP2
out by the end of the year (only about a year late) so that all the
other new operating systems can get here.
 
Bill Davidsen said:
People are still doing graduate thesis on NUMA, it's not clear that
more people will mean shorter time to solution. The first cut may
settle for being stable and running well where Ntask <= Ncpu. Getting
it wrong means bigtime bad throughput, which is probably an issue,
since there are more mature Linux and Solaris (I'm told) models as
competition.

I think the rest of the steps are pretty well understood and can be
solved in reasonable time. Or course things like keeping the CPU
number in a byte will need work ;-)


I just remembered that pretty soon there will be dual-core Opterons too, so
that in itself will add another level of NUMA to take into account. Internal
chip-connect vs. Hypertransport connect vs. customized board-to-board
connect.

Yousuf Khan
 
Russell Wallace said:
I don't know whether he's being sarcastic...


...but I hope you are! :P

NT was 64-bit clean, since the Alpha and MIPS ports seemed to make that a
requirement, as does the upcoming PPC port for Xbox2.

The biggest problems are getting all those 32-bit drivers converted to
64-bit, and getting 32-bit apps to work under a 64-bit OS, neither of which
was a problem for the prior ports (since they were 64-bit only).

Some "apps" like .NET were gratuitously dependent on the register size, and
those will need serious reworking, but the OS core was ported to AMD64 over
a year ago.

S
 
Dean Kent said:
My money is on embarassement...

Given MS just announced all AMD64 platforms have slipped to 1Q05,
embarrassment is pretty much a given -- not to mention Linux has been
shipping for AMD64 for over a year.
 
Stephen Sprunk said:
NT was 64-bit clean, since the Alpha and MIPS ports seemed to make that a
requirement, as does the upcoming PPC port for Xbox2.

I can't comment on the MIPS port, but the Alpha port was 32 bits, and
was pretty famous for it, because it was Plain Weird. I see a ton of
other wrong info in this thread, despite people's attempt to correct
it.

Followups reduced to groups I read.

-- greg
 
NT was 64-bit clean, since the Alpha and MIPS ports seemed to make that a
requirement, as does the upcoming PPC port for Xbox2.

I don't know how you could come to any of these conclusions, given the
public information anyway.
The biggest problems are getting all those 32-bit drivers converted to
64-bit, and getting 32-bit apps to work under a 64-bit OS, neither of
which was a problem for the prior ports (since they were 64-bit only).

I agree with the others here. Force the issue by eliminating those who
won't convert. It seems Linux has done a reasonable job of supporting
AMD64 *without* all the resources M$ can bring to bare.
Some "apps" like .NET were gratuitously dependent on the register size,
and those will need serious reworking, but the OS core was ported to
AMD64 over a year ago.

Ah, so we have another conspiracy theory. So you're on the "incompetence"
side?
 
Keith said:
Ah, so we have another conspiracy theory. So you're on the "incompetence"
side?

Some things are designed to be easily portable (such as DB2, perhaps?),
while others are not. The incompetence does not have to be with today's
coders, but could be due to yesterday's designers...

Regards,
Dean
 
Keith said:
I don't know how you could come to any of these conclusions, given the
public information anyway.

The Alpha and MIPS ports of WNT were 32-bit. The 64-bit WNT for Alpha
never was released publically (and AFAIK Linux/MIPS died before work
on 64-bit WNT started). However, WNT for IA-64 is 64-bit, so 64-bit
WNT exists ("WNT" here includes W2K, WXP etc.).
I agree with the others here. Force the issue by eliminating those who
won't convert. It seems Linux has done a reasonable job of supporting
AMD64 *without* all the resources M$ can bring to bare.

How does a good marketing machine and the ability to buy competitors
help in driver development? Or what kind of resources are you
thinking of that MS has and that Linux lacks?

Linux has profited here from something that is sometimes seen as a
disadvantage: That hardware vendors usually don't do Linux drivers, so
Linux developers had to write them themselves. Making them work on
64-bit kernels is less work than writing them from scratch or getting
the hardware vendor to do the 64-bit port (for a Windows version that
is not released yet).

To make 32-bit apps to work under a 64-bit OS, you need to convert the
32-bit system calls to 64-bit ones, and to provide all the 32-bit
libraries (and a way for the apps to link to the right libraries). If
you have a more complex infrastructure (as Debian does), you have to
adapt that as well (and that's why Debian has a pure64 port, with
the multiarch i386/amd64 port waiting for upstream extensions to the
infrastructure last time I looked). However, WNT should have already
tackled this for the IA-64 port, no?

Followups to comp.arch.

- anton
 
Back
Top