Conflict in shared memory

I would know a thing about shared memory. When N threads try to read the same location in the shared memory there is N conflict and the access will be serialized, and when all threads in a warp try to access the same location, the information will be broadcasted to all threads, right?? the question is: When all threads of two different warps access the same location, the information is broadcasted to all 64 threads or serialized in 2 access (the first 32 thread and then the other 32)?? And this happens only when the access is for 32 bit (4 byte) or also if it is for 1 (a character, for example) or 2 bytes?? Thanks.

I would know a thing about shared memory. When N threads try to read the same location in the shared memory there is N conflict and the access will be serialized, and when all threads in a warp try to access the same location, the information will be broadcasted to all threads, right?? the question is: When all threads of two different warps access the same location, the information is broadcasted to all 64 threads or serialized in 2 access (the first 32 thread and then the other 32)?? And this happens only when the access is for 32 bit (4 byte) or also if it is for 1 (a character, for example) or 2 bytes?? Thanks.

bank-conflict only occurs inside a warp (more precisely, half-warp), and each warp runs independently.

bank-conflict only occurs inside a warp (more precisely, half-warp), and each warp runs independently.

Ok, thanks. this is true also if the transactions are of 1 byte?? if 4 threads in the same half-warp try to access in a different byte in a 4-byte segment there are 4 conflicts??

Ok, thanks. this is true also if the transactions are of 1 byte?? if 4 threads in the same half-warp try to access in a different byte in a 4-byte segment there are 4 conflicts??