ASM data extent VS tablespace extent

Please don't mix oracle extent with the data extents concepts being used here, see http://download.oracle.com/docs/cd/B28359_01/server.111/b31107/ostmg_gloss.htm#BABFCABI

I presume that you know about the concepts of tablespace extents (YOu can have uniform size of auto or also different size). These are intra-tablespace space management. For data extents described here, you can compare it with OS block in normal file system and each allocation using of ASM consists of one or more data extents (not tablespace extents).

So my question is that how can i have tablespaces with uniform extent size of say 100M on ASM? If so, will ASM further breakdown the extent sizes to its default AU size?

Just ike as you can use same tablespace extents size of 100 MB on a regular file system of OS block of 512 byte or 2k, or 4k (or whatever). In this case your database will want to write to allocate an extent of 100MB and then ASM will take over the responsibility that how it will physically store this 100MB extent on disk group by allocating Allocation unit. If on that disk group, your this 100MB extent is required to be allocated on an extent set(set of data extents) number 20001, and your allocation unit size for ASM is 1 MB, it will allocate 8*1 size ASM file extent and total around 13 extents (13*8 = 104 MB) so that your 100MB tablespace extent could be stored.