# problems about cudaprof

**URL:** <https://forums.developer.nvidia.com/t/problems-about-cudaprof/15014>\
**Category:** CUDA Programming and Performance\
**Created:** [February 18, 2010, 4:20pm UTC](https://forums.developer.nvidia.com/t/problems-about-cudaprof/15014 "2010-02-18T16:20:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sgu](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sgu](https://forums.developer.nvidia.com/u/sgu)\
**Post date:** [February 18, 2010, 4:20pm UTC](https://forums.developer.nvidia.com/t/problems-about-cudaprof/15014/1 "2010-02-18T16:20:15Z")

</div>

Hi,  
I am using cudaprof under linux. However, the option for gld/gst coalesced/uncoalesced cannot be selected. Other options are fine.  
What could be wrong?  
Thank you.

---

<div class="post-metadata">

**Author:** ![avidday](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/avidday/32/59219_2.png) [@avidday](https://forums.developer.nvidia.com/u/avidday)\
**Post date:** [February 18, 2010, 4:25pm UTC](https://forums.developer.nvidia.com/t/problems-about-cudaprof/15014/2 "2010-02-18T16:25:05Z")

</div>

I would guess your are using a compute 1.2 or 1.3 capability GPU, and those counters are no longer valid for the latest GPUs. There are alternative, more useful memory transaction counters you can use instead.

---

<div class="post-metadata">

**Author:** ![sgu](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@sgu](https://forums.developer.nvidia.com/u/sgu)\
**Post date:** [February 18, 2010, 5:45pm UTC](https://forums.developer.nvidia.com/t/problems-about-cudaprof/15014/3 "2010-02-18T17:45:13Z")

</div>

Thanks for your reply.

Yes I am using cc 1.2

But Are you talking about the counters gld/gst\_32/64/128b? But from those counters, we will do some calculation to figure out whether the global memory access is coalesced or not.

Does gld/gst\_32/64/128b only count for direct global memory asscess nor it also counts the indirect global memory access though texture?

> [@](#):
>
> I would guess your are using a compute 1.2 or 1.3 capability GPU, and those counters are no longer valid for the latest GPUs. There are alternative, more useful memory transaction counters you can use instead.