Did Digitlife jump the gun announcing NV40?
- Thread starter g__day
- Start date
I noticed Abit wasn't on the list of vendors providing 6800 Ultra cards. Maybe Nvidia is a bit mad at them for going ATI?
________
METEOR RIDEAU
________
METEOR RIDEAU
Last edited by a moderator:
chavvdarrr
Veteran
Also diagrams:
Pixel pipe:
loop:
shader1 or Tex
shader2
-------------
also
"co-issue - 2 independant instruction executing on same shader unit as 3/1 or 2/2 (R3xx can execute at 3/1)" <- that's funny
" GF6800 dual-issue - 2 instructions in same cicle on different shader units"
Hellbinder
Banned
My origional comment was based on a statement in the thread made by another poster. Now that i see the linked page it makes more sense.
Hellbinder
Banned
Gotta love how they are telling everyone how "R300" from two years ago.. "Cant do that"...
surfhurleydude
Newcomer
Hellbinder said:Gotta love how they are telling everyone how "R300" from two years ago.. "Cant do that"...
Maybe because the R3xx line up is the only competing card with the NV40? Remember, the R420 has not been announced yet!
THANK YOU!!!!!Me said:
surfhurleydude
Newcomer
bloodbob said:I guess they got confused about the time zone because on the digilife post they said exactly 17:00 so I'm guessin 17:00 wherever timezone we are going to see alot of NV40 posts
Perhaps they thought the NDA was up at 5:00 PM, but rather 5:00 AM... I don't know how they confuse it since they're on the 24 hour clock... Anyways, it is less than 7 hours until 5 AM where they are, perhaps we'll see some shit then.
Might be needed...
Anyway, they don't say anything about how many vertex shader units there are, or indeed, give any vertex shader performance numbers at all... Maybe the pixel pipes doubles as vertex shaders too?
(Ok, ok. Baseless speculation I admit, but why else wouldn't they say anything on the subject??)And that die shot was VEEERY interesting. Not nearly as regular as I expected, though most pixel pipes seems to be clearly distinguishable as a square block. I didn't bother to try and find all 16 as they get more and more staggered as one proceeds from top left towards bottom right; up to around 12 is fairly easy though.
Guden Oden said:Anyway, they don't say anything about how many vertex shader units there are, or indeed, give any vertex shader performance numbers at all... Maybe the pixel pipes doubles as vertex shaders too?
Looks like 6 VS to me
Mintmaster
Veteran
I think they just mean 8 total fp32 ops per clock per pipe, i.e. two vector4 ops per pipe per clock. R300 can do a texture access and a vector4 op per clock, so that's also 8 ops per clock using similar terminology.
8 * 16 = 128, NVidia's magic number.
NV40, however, can do another arithmetic vector4 op instead of a texture op if it wants to, which will pay dividends down the line, and they can also split vector4 ops into vector3 + scalar (like R300) or vector2 + vector2.
In other words, FAR more throughput per pipe than NV30, and as games use more arithmetic in their shaders, significantly more than R300 per pipe as well.
Of course, all this hinges on me correctly interpreting those diagrams.
8 * 16 = 128, NVidia's magic number.
NV40, however, can do another arithmetic vector4 op instead of a texture op if it wants to, which will pay dividends down the line, and they can also split vector4 ops into vector3 + scalar (like R300) or vector2 + vector2.
In other words, FAR more throughput per pipe than NV30, and as games use more arithmetic in their shaders, significantly more than R300 per pipe as well.
Of course, all this hinges on me correctly interpreting those diagrams.
