-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QST] How to use an Iterator over parameters #2067
Comments
I think it is actually easier for you to do it in a lower level - threadblock level: it has many usages of What you want to do seems can be inserted into the beginning of the epilogue. You need to make sure first without your change, the kernel can compile. If it cannot compile, it means this kernel is not supported. |
Hi @hwu36 , I guess you mean, for example, to use the code near line 321, maybe it is working. Still, eventually, I discovered how you could access an modify the filter parameters without recurring to the iterator.
I deduce the shape of the filters by observing the several readme documents in the repo. Perhaps this method is not as technical as using iterators. Still, it allows me to parallelise the access to the filters in operator() function with several threads and to modify its values. In any case, I would appreciate it if you could give me some insight about it. |
Yours is fine |
What is your question?
Hi, I am trying to use Iterators to access filter parameters in Conv2dFprop.
In more detail, I am trying to access these params in this particular place:
cutlass/include/cutlass/conv/kernel/implicit_gemm_convolution.h
Line 332 in 24f991e
I try to use Iterator_B, which I believe iterates over the convolution filters.
The code I am using is the following:
But, I get some errors about that methons valid() and get() are not available in Conv2dFpropFilterTileAccessIteratorOptimized:
How can I properly use IteratorB or access the pointer where the convolution filters are stored and access/modify them?
Thank you.
The text was updated successfully, but these errors were encountered: