committed memory is much much more than limit

Can someone explain why the committed memory is much more that the limit and total physical ram?

mahmood@n1:~$ cat /proc/meminfo
MemTotal:       66108396 kB
MemFree:        50265064 kB
Buffers:               0 kB
Cached:           403164 kB
SwapCached:            0 kB
Active:         14470564 kB
Inactive:         109088 kB
Active(anon):   14179068 kB
Inactive(anon):        0 kB
Active(file):     291496 kB
Inactive(file):   109088 kB
Unevictable:       13228 kB
Mlocked:           13228 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:      14190380 kB
Mapped:            26976 kB
Shmem:               244 kB
Slab:              37160 kB
SReclaimable:      12396 kB
SUnreclaim:        24764 kB
KernelStack:        3656 kB
PageTables:        33888 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:    33054196 kB
Committed_AS:   160452848 kB
VmallocTotal:   34359738367 kB
VmallocUsed:      383056 kB
VmallocChunk:   34308529128 kB
HardwareCorrupted:     0 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:        8896 kB
DirectMap2M:     3135488 kB
DirectMap1G:    63963136 kB

What does it mean? is it good or bad?

I'd say it was swap, but you don't appear to have any swap (SwapTotal 0).

So I look at the documentation. meminfo documentation take 2 [LWN.net] Committed_AS is some theoretical estimate of how much memory you might need, worst case. It does not reflect an actual current usage.

That page doesn't mention CommitLimit though.

Closed by request