So, does the 7950GX2 count as a single card solution?

[josh6079]

Originally posted by: beggerking

1. explain to me then, what is your explaination of SLI software? how does it work that would makes it require hardware?

beggerking, how would you do anything with software if you didn't have hardware? Can you sit there and physically tell me that you have software sitting in your hand? Can you create software with out using hardware? If you don't have hardware, what is software on?

As far as SLI software, it is designed to offer different solutions to GPU rendering, such as AFR AFR2, Split-Screen, and SLI AA. Basically, it determines how the load is going to be balanced between the two GPU's and Memory controllers. Now, in a single card, you would not need SLI software since there is not balancing that has to take place since there is only one GPU and one memory controller.

information between 2 GPUs CAN be shared with SLI bridge btw.

Well you don't say......

What do you thinK is between the 7950's two pcb's? Yep, its a SLI connector. That means that the information is being shared. Why? Because there are two cards for the informations to be shared upon.

you can't do SLI AA on a single card, and what EXACTLY IS YOUR POINT? stop posting bullsh*t questions without actual point!

EXACTLY. So why can you do SLI AA on this single card?

Single card GPU each can only do 4xaa at once , so its pointless to call it SLIAA. so what is your point?

No, single Nvidia cards can do up to 8x AA as well. Dual cards and their SLI AA can do 16x due to a combined 8x on each card.

disable SLI so the same data is distributed to both GPUs.

???

little kid, please, please read do some research before you reply.
hardware works as long as it runs as it is designed for. 7950 is designed to take 2 input data and process them on 2 GPUs

As long as there is SLI, a dual card feature, enabled through the driver.

so as long as there are 2 input data coming into the card, the hardware is working and is working as it was designed for.

Maybe for you, since you play games in safe mode.

I'm sure your level won't grasp such distinction between software and hardware. Therefore I'm going to leave you here to rot. go ahead and believe your "what you see in hardware manager is what you get" theory, and oh ya, you do have dual CPU with your P4 HT.
right.

don't bother to reply, I'm done here with your crap. You simply don't listen and kept asking stupid questions, while making up dumb phrases such as "Driver path"
hahahahaha

Promise? That would be nice....considering you're the one not grasping anything.

Notice how you're the only one arguing your independent software theory?

"SOFTWARE HAS NOTHING TO DO WITH HARDWARE!!!!" hahahahaha

 

[enz660hp]

if its fits into one slot, its one card. We need to use that x16 bandwidth!!!

 

[BFG10K]

"Hyper-Threading doesn't add another physical CPU, it simply allows the utilization of unused pipeline locations from the existing CPU without duplicating an entire CPU core. "
what'd hell are you talking about? care to explain the bolded part? it meant nothing! , nonsense just as your "driver path" theory

I'm now convinced that I'm arguing with a 13 year old "tech"; it's obvious you don't have the faintest clue what the hell you're talking about.

You really have no idea what Hyper-Threading is, do you? To demonstrate how clueless you are I'll explain it to you one last time.

Hyper-Threading essentially allows an existing CPU to use its idle pipeline sections to run additional threads so that it runs code more efficiently due to a higher instruction throughput.

But because it's only one CPU it doesn't require the duplication of a second core so only 5% is added to the total die size.

1. explain to me then, what is your explaination of SLI software? how does it work that would makes it require hardware?

Load and rendering distribution done across two or more GPUs which (obviously) requires two or more GPUs. I would've thought the definition of SLI would be painfully obvious but I guess with your lacking understanding that isn't the case.

2. "how to get the "scheduler" to get SLI AA working on a single card." ... that is the DUMBEST question I've ever heard!

You claimed "the hardware has nothing to do with the software" so if that's the case demonstrate how to get SLI and SLI AA to operate on a single card.

do you even know what a scheduler is ? it has nothing to do with SLI AA. information between 2 GPUs CAN be shared with SLI bridge btw.

Except it can't be "shared" between one GPU which is my whole point.

Now please explain your "driver path" and your "HT utilize unused pipeline crap".

I've already done this repeatedly and given you still can't understand the basics I would suggest you take some remedial computing classes to help you.

The only thing more laughable than your "facts" is that you actually think what you're saying is correct and everyone else is wrong. That and your alarming lack of knowledge of the English language.

you can't do SLI AA on a single card, and what EXACTLY IS YOUR POINT?

That IS my point. The point is that your "software has nothing to do with hardware" and "it's just a scheduler" is complete rubbish.

Ignoring the hardware and claiming it's all about the software is a complete simpleton interpretation of the situation.

SLI AA means each GPU does 4x AA, then combine to produce 8x, then output.

Except that isn't what you said initially said so let me remind you of your first "definition" of SLI AA:

SLI AA = 2 GPUs each apply 8x on 1/2 screen which produce 8x AA.

Are you now telling us you have retracted this bullsh*t claim?

Single card GPU each can only do 4xaa at once , so its pointless to call it SLIAA. so what is your point?

I'm not calling it SLI AA, I'm pointing out that the hardware dictates what the software can do unlike your delusional claim that it can't.

little kid, please, please do some research before you reply.

Pot-kettle-black.

hardware works as long as it runs as it is designed for.

That isn't even a valid English sentence so before you call someone a "little kid" you may want to take some remedial English courses.

7950 is designed to take 2 input data and process them on 2 GPUs, so as long as there are 2 input data coming into the card, the hardware is working and is working as it was designed for.

Likewise single cards are designed to take one data input and process it on one GPU, that's why the concept of SLI doesn't exist on single cards and that's why the 7950 is not a single card.

I'm sure your level won't grasp such distinction between software and hardware.

You don't even have a distinction because in your world hardware doesn't exist.

Therefore I'm going to leave you here to rot.

:roll:

go ahead and believe your "what you see in hardware manager is what you get" theory,

The "hardware manager" has nothing do with it

and oh ya, you do have dual CPU with your P4 HT.

Oh so you now you believe the "hardware manager" despite it being obvious that a HT CPU is neither dual-core or dual-CPU? Another flip-flop on your part?

 

[potato28]

No its still two pcb's holding 1 core each.

 

[josh6079]

Hold on, BFG10K, you have to see this:

Originally posted by: beggerking

Yes. 7950GX2 is basically a SLI setup which beats any single GPU card.

Found here

Um.....and what is an SLI setup usually composed of? (whispers in ear, "Yep, two cards")

So why, beggerking, were you arguing so much only to later say that it is basically two cards? I thought in your eyes it was completely a single card, not "basically an SLI setup".

 

[josh6079]

Since beggerking began to bring the discussion in this thread to my PM box, replied twice to me, then put me on his ignore list so I couldn't PM him further, I'm going to reflect what our PM's were since they pertain to this thread:

His first PM to me in response to the last post I made before this one:

Originally PMed by: beggerking
GX2 uses SLI software, but its not 2 cards. its 2 GPUs.

Unless you are arguing your dual-core CPU is actually 2 socketed CPUs. Because SLI software = windows data scheduler.

My response was this:

Originally PMed by: josh6079
When did I argue about the dual-core CPU actually being 2 socketed CPU's? Are you sure you're not meaning to talk to BFG10K? I think he was the one refering to Dual CPU's and stuff.

You orginally said that the software for the GX2 doesn't mean that it is two 7900's slapped together. You backed up your claim with an analogy of a boot up into safe mode and how it doesn't need a driver to do so. From there, you've labeled IBM incorrect in their Driver Path statements and continued to argue with anyone who suggested the opposite of you. Also, you get everyone you agrue with mixed up and accuse them of doing things or saying things that they have never done nor said.

You are just plain wrong beggerking, be done with it. It is two pcbs, with 512Mb's and a 7900 series GPU on each set pcb with a fabricated SLI pin connector resting bewteen the pcbs. It requires SLI software to play games correctly. It is two cards from a software standpoint, like BFG10K said in his original statement, and it is almost two cards from a hardware standpoint, minus the fact that it can be placed into one PCI-E slot.

His next reply was:

Originally PMed by: beggerking
You simply can't distinguish what is SLI software vs SLI bridge.. software vs hardware..
I was talking about software SLI setup, not your 2 card crap.

I tried to reply, but for some reason he doesn't want to talk about this in private anymore. (I'm on his ignore list)

So, why again beggerking have you argued so extensively about the 7950 not being dependent on SLI software only to comment in another thread that it is basically an SLI setup? Why argue with BFG's statement about the 7950 being two cards from a software standpoint only to later agree?

 

[redbox]

So I asked my magic eight ball if the 7950GX2 was a single card and it's reply:"Maybe"
.....you guys don't want to know what it said about beggerking.

 

[josh6079]

Originally posted by: redbox
So I asked my magic eight ball if the 7950GX2 was a single card and it's reply:"Maybe"
.....you guys don't want to know what it said about beggerking.

we really didn't need that redbox.......

 

[BFG10K]

Oh look, Beggerking has a nice new signature:

BFG:
Hyper-Threading allows an existing CPU to use its idle pipeline

Except I never said that, what I said was:

Hyper-Threading doesn't add another physical CPU, it simply allows the utilization of unused pipeline locations from the existing CPU without duplicating an entire CPU core.

So Beggerking has now started telling lies and making up quotes that never existed.

Furthermore Beggerking's own link to Wikipedia confirms what I said is actually correct and he is wrong:

The technology improves processor performance under certain workloads by providing useful work for execution units that would otherwise be idle, for example during a cache miss.

Where execution resources in a non-Hyper-Threading capable processor are not used by the current task, and especially when the processor is stalled, a Hyper-Threading equipped processor may use those execution resources to execute the other scheduled task.

So this clueless liar has shown us that his own links prove he is wrong.

I have reported your signature to the mods.

 

[chr6]

Originally posted by: Rangoric

The X1900XTX can power two monitors at its full power.

A 7950GX2 can't. It only works at half strength when dealing with 2 monitors.

yeah, this is the issue im having, and why i want to trade my 7950gx2 for a 7900gtx

 

[beggerking]

BFG:

Hyper-Threading allows an existing CPU to use its idle pipeline

Except I never said that,

hahahahahahah you don't even remember what you said? link time:06/20/2006 07:47 AM
The fact you don't remember your own post simply imply you don't understand it yourself. oh ya, I pmed mod about all your threadcrapping. They are looking into it.

Furthermore Beggerking's own link to Wikipedia confirms what I said is actually correct and he is wrong:

The technology improves processor performance under certain workloads by providing useful work for execution units that would otherwise be idle, for example during a cache miss.

Where execution resources in a non-Hyper-Threading capable processor are not used by the current task, and especially when the processor is stalled, a Hyper-Threading equipped processor may use those execution resources to execute the other scheduled task.

So this clueless liar has shown us that his own links prove he is wrong.

.

I was referring to your

Hyper-Threading allows an existing CPU to use its idle pipeline

do you see anything above mentioning pipeline? it has NOTHING to do with HT. the correct definition is :
"An instruction pipeline is a technique used in the design of microprocessors and other digital electronic devices to increase their performance. Pipelining reduces cycle time of a processor and hence increases instruction throughput, the number of instructions that can be executed in a unit of time"

it has NOTHING!(NADA) to do with HT! Once again you are WRRRRONG! and yet accused me of being a lier.. exactly as when you asserted your "driver path" thing until I pointed out to you its "DATA PATH"!

stop being wrong. RESEARCH and THOROUGHly understand the basic concepts before you post. Once again , you embarrassed yourself.

 

[josh6079]

Originally posted by: beggerking
when you asserted your "driver path" thing until I pointed out to you its "DATA PATH"!

He didn't assert that beggerking, that was me. That makes you "WRRRRONG"

Anyways, IBM calls it a driver path and you think they're wrong too. Did you help make the Xbox360? Are you a multi-million dollar industry? Do you employ countless engineers? I wonder who I'll believe........

stop being wrong. RESEARCH and THOROUGHly understand the basic concepts before you post.

Hm.... "SOFTWARE HAS NOTHING TO DO WITH HARDWARE!!!!"

Where is the "THOROUGHly" done research "lier"?

Besides beggerking, you've already agreed with all of us in another thread: Thread Link

Originally posted by: beggerking
Yes. 7950GX2 is basically a SLI setup which beats any single GPU card.

Why do you persist on arguing this anymore? Didn't you say,

Originally posted by: beggerking
don't bother to reply, I'm done here with your crap.

Now you're back trying to reignite a dying fire. Just let it go.

 

[LittleNemoNES]

Originally posted by: beggerking

BFG:

Hyper-Threading allows an existing CPU to use its idle pipeline

Except I never said that,

hahahahahahah you don't even remember what you said? link time:06/20/2006 07:47 AM
The fact you don't remember your own post simply imply you don't understand it yourself. oh ya, I pmed mod about all your threadcrapping. They are looking into it.

Furthermore Beggerking's own link to Wikipedia confirms what I said is actually correct and he is wrong:

The technology improves processor performance under certain workloads by providing useful work for execution units that would otherwise be idle, for example during a cache miss.

Where execution resources in a non-Hyper-Threading capable processor are not used by the current task, and especially when the processor is stalled, a Hyper-Threading equipped processor may use those execution resources to execute the other scheduled task.

So this clueless liar has shown us that his own links prove he is wrong.

.

I was referring to your

Hyper-Threading allows an existing CPU to use its idle pipeline

do you see anything above mentioning pipeline? it has NOTHING to do with HT. the correct definition is :
"An instruction pipeline is a technique used in the design of microprocessors and other digital electronic devices to increase their performance. Pipelining reduces cycle time of a processor and hence increases instruction throughput, the number of instructions that can be executed in a unit of time"

it has NOTHING!(NADA) to do with HT! Once again you are WRRRRONG! and yet accused me of being a lier.. exactly as when you asserted your "driver path" thing until I pointed out to you its "DATA PATH"!

stop being wrong. RESEARCH and THOROUGHly understand the basic concepts before you post. Once again , you embarrassed yourself.

you're really petty... and obsessive

 

[beggerking]

Originally posted by: josh6079

Originally posted by: beggerking
when you asserted your "driver path" thing until I pointed out to you its "DATA PATH"!

He didn't assert that beggerking, that was me. That makes you "WRRRRONG"

and that only makes you a fooll for believing in him..

and here is BFG's definition to "driver path"( he has a couple):
"No, nVidia "made it up" when they implemented SLI support in the driver, something that was not necessary (or in fact undefined) for single cards. "here

then

"You don't know what a driver path is? It's a path that is taken in order to operate a given hardware device. For most devices it's generic but since GPUs have vastly different features their driver pathways tend to differ. "here

Anyways, IBM calls it a driver path and you think they're wrong too. Did you help make the Xbox360? Are you a multi-million dollar industry? Do you employ countless engineers? I wonder who I'll believe........

they dont' CALL it, they NAMED it Subsystem Device Driver Path Control Module (SDDPCM)
in description, it explains it "SDDPCM is a loadable path control module designed to support the multipath configuration environment in the IBM TotalStorage Enterprise Storage Server"

its pity that you even got that part wrong.. wow... its a name. let me repeat to you once again, there is no such thing as a driver path so stop derailing the thread.

Hm.... "SOFTWARE HAS NOTHING TO DO WITH HARDWARE!!!!"

Where is the "THOROUGHly" done research "lier"?

so tell me , genius. how does software relate to hardware? explain it with some facts, please.

and you have problem with reading comprehension. SLI setup != SLI software. you gotta get your hardware fact vs software fact straight.

SLI setup = 2 SLI capable cards with SLI bridge.
SLI software = NV driver.
Clear enough? Stop arguing unless you have facts and link to back it up! enough of your made up "driver path" phrases. research before you reply.

 

[redbox]

so tell me , genius. how does software relate to hardware? explain it with some facts, please.

There are many: DX10 is software right? Well when DX10 gets out try playing with it on any card besides a G80 or R600. You also say that SLI software is the NV driver right? If this is true then tell me how to fool the SLI software into thinking my 7800gt is two cards.

SLI setup = 2 SLI capable cards with SLI bridge. SLI software= NV driver clear enough?

Um don't you say the 7950GX2 is one card? I do believe that it uses SLI drivers so does that make it a SLI setup?

they dont' CALL it, they NAMED it Subsystem Device Driver Path Control Module (SDDPCM)

yes they named a control module that they made Subsystem Device Driver Path Control Module. What if Nvidia NAMED the Forceware drivers: SLI Drivers? Would it mean that SLI doesn't exist, because they didn't CALL it SLI they NAMED it that? Your being nitpicky besides arguing something that doesn't really change the out come of the discusion.

 

[josh6079]

beggerking, its over, let it go. You have nothing more to prove. I could go on all day breaking your comments up and trying to knock some sense into you and I'm sure you could do the same to me. (we've been through it countless times) The fact is you're not even talking about the 7950 anymore because your too busy trying to get the last word in, no matter how much nonsense it makes. You are overlooking many things in your arguments that contradict what you have said earlier, but I'm sure you are thinking the same thing about me. Just drop it already, all you're doing now is trolling considering I can't even PM you to discuss this further since you are ignoring me. Crying out in public on a thread that is long overdue for a lock in order to make your last worthless points isn't exactly smart. Regardless of what you (or I) think, the poll shows that about half of the people think that its one card while another half think its two. Let it go.

 

[beggerking]

I already did let it go, then you re-ignited it06/22/2006 03:44 AM post.

then just above for some odd reason you replied for BFG....and reasserted on the existance of "driver path"(rather than the correct term "data path") with the name of a software package from IBM....

umm..also, your signature don't exactly reflect your intent.

but I'm tired of arguing with you or BFG on your worthless point to prove the existance of "driver path". If you and BFG stop, I'll stop.

redbox: "DATA PATH" is a technical term, "driver path" don't even exist.

 

[josh6079]

You reignited it by contradicting yourself on a different thread: Link

I just brought your own evidence against yourself into the correct thread. You can't expect to argue with everyone and their dog in one thread, then go to another and make a post that contradicts your own previous arguments somewhere else and not have someone comment on it.

 

[beggerking]

Josh6079:
He didn't assert that beggerking, that was me. That makes you "WRRRRONG"

Anyways, IBM calls it a driver path and you think they're wrong too. Did you help make the Xbox360? Are you a multi-million dollar industry? Do you employ countless engineers? I wonder who I'll believe........

how did I contradict myself here?

bfg:
The driver path that is invoked is the SLI driver path, not the single GPU path. SLI is a function of multiple GPUs and therefore from a software standpoint it's two cards.

BFG's driver path 06/07/2006 10:29 PM

 

[josh6079]

Because BFG never started the "Driver Path" phrase that you are so bent on, I did. Earlier you had claimed that he had began the phrase.

When I say you contradicted yourself I am meaning in the thead I linked. You had claimed that the 7950GX2 is basically an SLI setup in there, yet here you have been arguing for pages about how it is not.

 

[beggerking]

Originally posted by: josh6079
Because BFG never started the "Driver Path" phrase that you are so bent on, I did. Earlier you had claimed that he had began the phrase.

bfg:
The driver path that is invoked is the SLI driver path, not the single GPU path. SLI is a function of multiple GPUs and therefore from a software standpoint it's two cards.

BFG's driver path 06/07/2006 10:29 PM

When I say you contradicted yourself I am meaning in the thead I linked. You had claimed that the 7950GX2 is basically an SLI setup in there, yet here you have been arguing for pages about how it is not.

basically a SLI setup that uses a single pci-e slot..therefore its a single card.

 

[josh6079]

Originally posted by: beggerking
basically a SLI setup that uses a single pci-e slot..therefore its a single card.

If that is the way you truly see it then you shouldn't have been arguing with BFG or any of us at all. I agree. From a hardware standpoint, and its ability to utilize only one PCI-E slot, it is a single card. However, from a software standpoint it is two due to the needed SLI profiles.

 

[Ulfhednar]

CLICK ME!

1.) It is two GO 7900s, each running at 8x speed so that they can share a slot.

2.) It does not even have just one PCI-E connector, it has a second inbetween the two cards as pictured above.

/thread

 

[josh6079]

It is two pcb's with corresponding GPU's and mem, but it is worthless when taken apart like that. Useful and together, this is one card hardware-wise.

 

[BFG10K]

hahahahahahah you don't even remember what you said? link time:06/20/2006 07:47 AM

I remember exactly what I said as my posts tend to stay un-edited, unlike the dirty stealth-edit tactics you employ. To refresh your memory, this is my full quote:

Hyper-Threading essentially allows an existing CPU to use its idle pipeline sections to run additional threads so that it runs code more efficiently due to a higher instruction throughput.

You chopped it off at the bolded word to make it sound like I said something completely different and then resorted to childish school-yard tactics of putting up signatures because you were beaten in the regular thread and couldn't deal with the responses.

The fact you don't remember your own post simply imply you don't understand it yourself. oh ya, I pmed mod about all your threadcrapping.

I see they've asked you to remove that ridiculous signature of yours. If you want to quote me then quote me properly instead of playing childish games and chopping my sentences to suit your agenda.

do you see anything above mentioning pipeline?

Pipeline sections.

Did you get that?

Let me repeat that for you again:

Pipeline *** SECTIONS ***, aka execution units. You'd know this if you even had a basic understanding of CPU architecture but you don't.

exactly as when you asserted your "driver path" thing until I pointed out to you its "DATA PATH"!

Except it is a driver path and no amount of tiresome rhetoric on your part will change that.

stop being wrong. RESEARCH and THOROUGHly understand the basic concepts before you post. Once again , you embarrassed yourself.

Just like when you linked to Wikipedia and your own links proved I was right and that you don't have a clue what you're talking about?

Let me re-quote the article you linked to again and highlight the relevant bits that back my claims:

The technology improves processor performance under certain workloads by providing useful work for execution units that would otherwise be idle, for example during a cache miss.

Where execution resources in a non-Hyper-Threading capable processor are not used by the current task, and especially when the processor is stalled, a Hyper-Threading equipped processor may use those execution resources to execute the other scheduled task.

Where exactly do you think execution units sit, Sherlock? That's right, on a pipeline, hence my original comment that totally went over your head as you proceeded to chop my quote to pieces.

Your lack of understanding of the issue is beyond comical.