search for: 0t1070318720

...because c_min was also 1GB, and I was not sure if c_max could be larger than c_min....Anyway, I set c_max to 1GB. After a workload run....: > arc::print -tad { . . . ffffffffc02e29e8 uint64_t size = 0t3099832832 ffffffffc02e29f0 uint64_t p = 0t16540761088 ffffffffc02e29f8 uint64_t c = 0t1070318720 ffffffffc02e2a00 uint64_t c_min = 0t1070318720 ffffffffc02e2a08 uint64_t c_max = 0t1070318720 . . . "size" is at 3GB, with c_max at 1GB. What gives? I''m looking at the code now, but was under the impression c_max would limit ARC growth. Granted, it''s not a factor...