BTW, @paul driver shows using NBAR rather than an ACL on ports. Just be aware, sometimes NBAR is just a "pretty face" on ACL protocol and port matching, but sometimes it does deep packet inspection and can recognize an application protocol using non-standard ports.
Also, Paul shows using a hierarchical policy, shaping all traffic at the "parent" level at 100Mbps (I believe - I didn't count all the zeros) and than guaranteeing your SMB traffic 10% of that (i.e. 10Mbps) in the child policy. That's a closer match to your "is it possible to guarantee 10M for the SMB ports 139, 445 on the 100M line?", although if the interface is actually running at 100Mbps, you don't need the parent shaper (and often will get better results).
Paul, unlike @Georg Pauwen doesn't prioritize your SMB traffic, but then again I don't understand "Can switch increase the priority of SMB(139,445) when we are using traffic all 100Mline?", especially the word "increase". Generally, as both Georg and Paul show, QoS policies are rather static. If you really want to change QoS rules "on-the-fly", based on current traffic loads, you would need to delve into something like EEM scripting.
If you would, if known, note the intended platform, and also further clarify what you're trying to accomplish, possible a better recommendation might be made.
