> What specific problem are you trying to solve? Are trying to see how > many huge pages were hit by memory errors? Yes, I'd like to know how many huge pages are not available because of the memory errors. Just like HardwareCorrupted in the /proc/meminfo. But the HardwareCorrupted only adds one page size when a huge page is hit by memory errors, and mixes with normal pages. So I think we should add a new counts to track the memory errors on hugetlbfs. -- Bin Wang
