Diving Deeper: The Maxwell 2 Memory Crossbar & ROP Partitions

Now that we have a basic understanding of the proper specifications of the GTX 970 we can dig deeper into its architecture and layout. As we mentioned previously, the GTX 970 ships with an unusual configuration, one we’ve never quite seen before. In it, thanks to a new feature of the Maxwell architecture, NVIDIA has been able to disable part of a ROP/Memory Controller partition, something that they could not do on Kepler or earlier generation designs. As a result of this the intended behavior of the GTX 970 is different than the GTX 980 or any theoretical Maxwell part with a completely disabled ROP/MC partition.

The biggest impact of this configuration is that it creates the segmented memory conditions NVIDIA outlined in their earlier statement. Due to performance issues from the unbalanced ROP/MC partition, NVIDIA segments the memory into a high-performance 3.5GB segment – what they refer to as segment 0 – and a low-performance 512MB (0.5GB) segment containing the rest of the RAM. It is this segmentation that results in some of the previously-unusual memory allocation behaviors and memory bandwidth benchmarks on the GTX 970.

But in order to understand just why the segments exist, how they are allocated, and how they influence performance, we first need to learn about the Maxwell memory crossbar.


GTX 970 Memory Crossbar

In the above diagram from NVIDIA, NVIDIA illustrates at a high-level overview how the Maxwell memory crossbar is laid out, and specifically how it’s configured for GTX 970. In it we have the 16 GM204 SMMs at the top connected to the crossbar, meanwhile below we have 4 ROP/MC partitions, with each partition divided up into individual ROP/L2 units and memory controllers. Note that the specific units disabled on any GTX 970 chip will vary – it’s not necessarily the 1/3/5 SMMs or the last ROP/MC partition – but from a high level overview this is consistent for GTX 970 regardless of which specific physical units have been disabled.

In any case, while the crossbar shows how the SMMs and ROP/MC partitions are connected via the crossbar, memory segmentation is really a story about the ROP/MC partitions. The SMMs do not play a role in how GTX 970’s memory is configured – the crossbar abstracts all of that – and the crossbar itself matters only in as much as the ROP/MC partitions are connected to it.

When it comes to the ROP/MC partitions then, we can see first-hand in the GTX 970 what’s new in the architecture. In Kepler and previous generation designs, NVIDIA’s granularity for disabling ROP/MC partitions was all or nothing – either the entire partition was turned on or the entire partition was turned off. However starting with Maxwell, NVIDIA has gained the ability to disable the individual ROP/L2 units within a partition, allowing one of the two ROP/L2 units to be disabled. This essentially introduces a 3rd possible option: a partially-enabled ROP/MC partition, backed by two memory controllers and a single ROP/L2 unit. Meanwhile the memory controllers are still tied together, and disabling one of them requires disabling the entire partition.

NVIDIA ROP/Memory Controller Configuration Options
Kepler Maxwell
ROP/MC Partition Fully Enabled ROP/MC Partition Fully Enabled
N/A ROP/MC Partition Partially Disabled
ROP/MC Partition Fully Disabled ROP/MC Partition Fully Disabled

It’s this option that the GTX 970 leverages, and in doing so becomes the first Maxwell part to use this feature. NVIDIA has disabled 1 ROP/L2 unit, removing 8 “ROPs” (or rather 1 unit capable of 8 pixels/clock) and 256KB of L2 cache from the GTX 970. This is why the GTX 970 is left with 56 ROPs spread over the 4 partitions, along with 1.75MB of L2 cache.

Meanwhile there’s one other new feature here that’s activated only on the partially disabled partition, and that’s the link between the first and second units of the ROP partition. Typically each ROP/L2 unit would have a link to a port on the crossbar and a link to its own dedicated 32-bit memory controller channel; however because GTX 970 disabled a ROP/L2 unit, the “buddy” link comes in to play. This link is essentially the lynchpin of Maxwell’s new partial disable functionality, and allows the second half of the memory controller to stay active. This link only needs to be active when a ROP/L2 unit is disabled, and NVIDIA has confirmed that it is a full bandwidth link identical to the normal ROP/L2 to MC link, meaning it’s capable of 4 32 byte requests per clock (2 reads and 2 writes). Ultimately this link is what makes a partially disabled partition possible, and is also what makes it possible to have the full 256-bit memory bus present and active in spite of the lack of a ROP/L2 unit and its associated crossbar port.

Finally, because of this configuration and the lack of a ROP/L2 unit we get to the memory segments.  Although the full 256-bit memory bus is present and active on GTX 970 and capable of providing 224GB/sec of combined memory bandwidth between the DRAM modules and the memory controllers, it’s a bit of a misnomer to say the card has that much bandwidth between the memory controllers and everything else, at least in the same sense that the GTX 980 does.

Like virtually every other operation on a GPU, memory accesses are done in parallel to improve throughput. On a fully enabled card such as GTX 980 these operations are striped across all of the memory controllers in what NVIDIA calls a 1KB stride. In doing this, each and every 32 bit memory channel needs a direct link to the crossbar through its partner ROP/L2 unit. However in the case of the GTX 970 a wrench is thrown into the works, as there are 7 crossbar ports and 8 memory channels.

Ultimately due to the design of the crossbars and the memory controllers, it is not possible for 1 crossbar port to carry the full load of 2 memory channels in all circumstances. The crossbar port and its attached ROP/L2 unit can access both memory channels at once, splitting up the 4 operations among them, but there is only 1 read return bus and 1 write data bas, and hence in practice it cannot issue identical operations to both memory channels at once . As a result NVIDIA has segmented the GTX 970’s memory into the now-familiar 3.5GB and 512MB segments. In the case of the 3.5GB segment, this behaves otherwise identically to a fully enabled card such as the GTX 980, with the 1KB stride being striped over 7 crossbar ports, and hence 7 DRAM modules. Meanwhile the 8th and final DRAM module sits in its own 512MB segment, and must be addressed by the crossbar on its own.

This in turn is why the 224GB/sec memory bandwidth number for the GTX 970 is technically correct and yet still not entirely useful as we move past the memory controllers, as it is not possible to actually get that much bandwidth at once when doing a pure read or a pure write. In the case of pure reads for example, GTX 970 can read the 3.5GB segment at 196GB/sec (7GHz * 7 ports * 32-bits), or it can read the 512MB segment at 28GB/sec, but it cannot read from both at once; it is a true XOR situation. The same is also true for writes, as only one segment can be written to at a time.

Unfortunately what this means is that accessing the weaker 512MB segment blocks access to the stronger 3.5GB segment if both memory operations are identical; or put another way, using the 512MB segment can harm the performance of the 3.5GB segment. For example, if we want to issue reads to both segments at once, reading the 512MB segment blocks any other reads to the 3.5GB segment for that cycle. If the 3.5GB segment is blocked in this fashion and doesn't have a non-blocking write to work on instead, it would have to go idle for that cycle, which would reduce the effective memory bandwidth of the 3.5GB segment. This means that taken over time in our example, the larger the percentage of the time the crossbar is reading the 512MB segment, the lower the effective read memory bandwidth would be from the 3.5GB segment.

Despite all of this, achieving peak memory bandwidth performance on the GTX 970 is still possible, but it requires much more effort since simple striping will not do the trick. The easiest and most effective solution in this regard is to interleave reads and writes over the segments, such that one segment is writing while another segment is reading. Interleaving in this fashion allows both segments to work at once – avoiding the blocking effect of the shared read and write buses – and makes it more likely that both segments are doing useful work rather than waiting for their turn on an operation. However because this is only applicable to situations where more than 3.5GB of VRAM is in use and both segments are necessary, this means it's only theoretically possible to achieve 224GB/sec when more than 3.5GB of VRAM is in use. In any situations below 3.5GB we are de-facto limited to just the larger segment, in which case there are only 7 memory channels (196GB/sec) to stripe memory operations across. NVIDIA could of course interleave operations sooner than that and use both segments more often, but due to the blocking effect we've discussed before the performance hit from using the 512MB segment can quickly become greater than any gains.

The end result of all of this is that the GTX 970 has a unique memory layout that needs to be accounted for by the operating system and NVIDIA’s drivers, as the use of multiple segments adds a new level of complexity to optimizing memory performance. Unequal in size and performance, among the two segments the 3.5GB segment is a larger, faster, and otherwise more preferable segment to the 512MB segment. Which means from a logical hierarchical perspective, the 512MB segment essentially serves as an additional layer of memory between the main VRAM and system memory, being slower than the 3.5GB segment but offering almost 2x the performance of going out over the PCIe bus to system memory.

The upshot here is that while this is the first time NVIDIA has used this specific ROP/MC configuration in a product, this is not the first product they have designed with segmented or otherwise unbalanced memory configurations. Since the GTX 500 series, on some midrange SKUs NVIDIA has used unbalanced/asymmetrical memory configurations, most recently on the GTX 660 and GTX 660 Ti. In the case of both of those cards, NVIDIA utilized a 192-bit memory bus with 2GB of VRAM attached, which meant that some memory controllers had more VRAM attached to them than others. The end result as it turns out is very similar, and while NVIDIA has never explained in-depth how they handle memory allocation on those cards, it turns out that it’s very similar to GTX 970’s memory segmentation. Which is to say that NVIDIA actually has multiple generations of experience with segmented memory, and this is not the first time they have implemented it. Rather this is first time we’ve seen such a configuration on a high-performance card such as the GTX 970.


For Comparison: GTX 660 Ti's Unbalanced Memory Bus

NVIDIA Maxwell Family Memory Controller Configurations
Part Memory Segments
GTX 980 1 Segment (4x8 MC)
GTX 970 2 Segments (4x7 MC)
GTX 980M 1 Segment (4x8 MC)
GTX 970M 1 Segment (3x6 MC)
GTX 965M 1 Segment (2x4 MC)

As for why NVIDIA is using such a configuration here, the crux of the matter is money and yields. Without the ability to partially disable a ROP/MC partition, NVIDIA would either have to spec a card to use a fully enabled partition – essentially reducing yields for that card and driving up costs – or disable the entire partition and lose all of the benefits of the additional ROPs, memory, and the memory controller. This finer granularity allows NVIDIA to better control how they harvest bad chips and what resulting configurations they bring to market, along with making a single ROP/L2 defect less harmful to overall performance by keeping the rest of a partition online. Otherwise, to stick with a “balanced” configuration with as many crossbar ports as DRAM modules would result in either a higher spec GTX 970, or a lower spec card with a 192-bit memory bus.

In the grand scheme of things then, depending on how you want to define memory capacity the GTX 970 can be said to have either 3.5GB of VRAM or 4GB of VRAM. Only the first 3.5GB segment is a high-speed (full bandwidth) segment, and for naïve operations this is the segment that software will want to use. However the final 512MB segment is accessible, and despite its lower performance it is still usable and still far better than going to system memory, in which case GTX 970 has and can access a full 4GB of VRAM. This means that both answers can be correct, and like so many other facets of modern technology, the true answer is often more complex than a single number.

GeForce GTX 970: Correcting The Specs & Exploring Memory Allocation Segmented Memory Allocation in Software
POST A COMMENT

398 Comments

View All Comments

  • Kutark - Tuesday, January 27, 2015 - link

    b/c consumers are dumb and if the 970 had 1mb less ram than 4gb it would of decreased sales. There is a reason they moved away from stuff like having 1.2gb or 1.5gb, etc etc. People like big solid numbers. Reply
  • HisDivineOrder - Tuesday, January 27, 2015 - link

    You give lawyers so much credit. Often, lawyers like being one to start such things and don't care much if they manage to finish it. Reply
  • maximumGPU - Wednesday, January 28, 2015 - link

    I'd say both Jarred. Sure, i look at performance first, but performance metrics tell me how good the card is NOW. The next thing i do is look at the specs and try and estimate how future proof my purchase will be.
    A 3GB 970 would show great metrics at 1080p, but i wouldn't buy it because i know ram is ever more important thanks to the consoles catching up.
    Since i game at 1440p, 4GB was my minimum ram threshold. i thought i got that with the 970, but instead got 3.5 + 0.5GB of slow ram. That makes my card less future proof than i thought and could've well affected my buying decision, regardless of its current performance metrics.
    Reply
  • Ranger101 - Tuesday, January 27, 2015 - link

    No surprises as to Nvidia's behaviour, as a company they are of course a rapacious juggernaut, but Tut Tut Anandtech, what would the great founder have to say?

    Having read many recent articles in the GPU section, I am mostly impressed by the high quality of writing, however those who read between the lines of Mr Smith's Gpu reviews, realise that appearances of impartiality in his writing are misleading and that he is in fact a staunch and unrelenting supporter of camp green. ( Everyone is of course biased, it's just less appropriate to let it shine through in technical website reviews.)

    It should therefore come as no surpise that in his initial review these issues "escaped" his attention, despite the fact that "a limited number of flags were raised" and that in the follow up article, he unashamedly wields the Bastard sword of Nvidia. LOL.

    You must remember these things happen for a reason Ryan and I once again encourage you to temper your bias in forthcoming utterances...AMD still make good cards and a little competition is good....right? :)
    Reply
  • just4U - Tuesday, January 27, 2015 - link

    I think the fact that Ryan gets accused of being in favor of AMD and Nvidia means that's he's doing a pretty good job of not really being in either camp. If anything I'd simply suggest his expectations on performance are limited and when the cards actually do better.. he tends to point that out. Not really a bad thing considering how underwhelming hardware leaps are these days in most segments. Smaller jumps not the leaps and bounds we were all once used to. Reply
  • OrphanageExplosion - Tuesday, January 27, 2015 - link

    Oh do behave. When Anandtech had the AMD News Center sponsorship all we ever heard from the commentariat was that the site, and Ryan specifically, were AMD biased. I think we all know where the bias is on Anandtech - and it's in the comments, not the editorial. Reply
  • HisDivineOrder - Tuesday, January 27, 2015 - link

    You're talking about the same guy that just took it on AMD's word that Mantle was going to be "virtually identical" to the same low level access API as the Xbox One and that subsequently Mantle was AMD bringing the Xbox One's low level access language to PC gaming.

    Seriously. If the guy is biased toward anything, he's biased toward believing more of AMD's statements than he really ought to, but I've had a hard time really blaming him since AMD had JUST paid for him (and his buddy journalists) to go to Hawaii on a beach trip and vacation under the excuse that it was to present the GPU part called "Hawaii." I mean, if I was tatken to Hawaii, I'd probably be willing to believe anything they told me, too.

    Still, don't mistake the man for an nVidia fanboy. He's clearly not. Lots of other people questioned that AMD party line far more than Anandtech did back in the day and it took a long time before they acknowledged that AMD had hoodwinked them and they never REALLY admitted it wholeheartedly.

    Because AMD suggesting that Mantle was anything but a completely proprietary and locked-in API was a lie and no hardware company has yet to sign up in spite of the fact Intel tried very hard to research the subject and was rebuffed by AMD for months.

    Intel likes to do anything they can do for free and they read all the press (like Ryan's) that suggested Mantle was going to be free and freely available, but as it turned out, that was more hyperbole on the part of AMD.

    Yet I saw nothing of that on Anandtech. No, I don't think there's much evidence of his being "a staunch and unrelenting supporter of camp green" unless you're recalling the heady days of AMD's time as a "green" company.
    Reply
  • Gothmoth - Tuesday, January 27, 2015 - link

    as if you read or even UNDERSTAND what ROP´s mean before you buy a card.....

    you and all the others are just trolls who have to much time on their hands....
    Reply
  • Kutark - Tuesday, January 27, 2015 - link

    I honestly don't understand why people are so up in arms over this. At the end of the day the performance figures still stand. The situations in which this news could actually arise and cause any problems are so limited its not even funny. At the resolutions and settings most games operate at don't use anywhere close to 4gb of vram.

    Honestly if i didn't have SLI'd 760's i'd go out and buy a 970 tonight, regardless of any of this information.

    That being said, this is another article that proves why anandtech is easily the best tech website out there. Thorough and honest, unbiased, just, amazing, love it. Sorry for all the commas.
    Reply
  • Kutark - Tuesday, January 27, 2015 - link

    Meant to say gamers, not games. Regardless. Reply

Log in

Don't have an account? Sign up now