Re: Does Latency is more important or Skew is more important
As others have said, it does depend greatly on your individual application. But a good rule of thumb to help you decide which is more important to your design is that synchronous interface timing depends more strongly on latency ("clock insertion delay") while internal register->register timing depends more strongly on clock skew (difference between clock arrival times at the registers).
Skew is not necessarily bad. And minimal internal clock skew should not normally be a goal in itself -- it is a just one part of an overall strategy to meet internal timing path requirements. Skew can sometimes even be used intentionally to improve timing paths ("useful skew").
And like papertiger mentioned, as insertion delay (latency) increases, OCV effects increase. Careful design of the clock tree can mitigate some small portion of this effect in many cases.
You will usually have to decide which is more important to your specific design because they are conflicting goals. Reducing skew will usually increase latency because you will be adding more delay to make the shortest paths as long as the longest paths, and individual branches in the clock tree will, on average, have smaller fanout with more levels in clock tree. Conversely, optimizing for minimum latency will probably result in greater skew because of fewer clock tree levels, higher fanout at each level, and less skew-balancing delay added to the fastest paths.
Best Regards
-- J.