On Wed 20-03-13 11:58:20, David Rientjes wrote:
> On Wed, 20 Mar 2013, Michal Hocko wrote:
>
> > > I didn't do this because it isn't already exported in /proc/meminfo and
> > > since we've made an effort to reduce the amount of information emitted by
> > > the oom killer at oom kill time to avoi
On Wed, 20 Mar 2013, Michal Hocko wrote:
> > I didn't do this because it isn't already exported in /proc/meminfo and
> > since we've made an effort to reduce the amount of information emitted by
> > the oom killer at oom kill time to avoid spamming the kernel log, I only
> > print the default h
On Wed 20-03-13 11:46:12, David Rientjes wrote:
> On Wed, 20 Mar 2013, Michal Hocko wrote:
>
> > On Tue 19-03-13 17:18:12, David Rientjes wrote:
> > > Particularly in oom conditions, it's troublesome that hugetlb memory is
> > > not displayed. All other meminfo that is emitted will not add up to
On Wed, 20 Mar 2013, Michal Hocko wrote:
> On Tue 19-03-13 17:18:12, David Rientjes wrote:
> > Particularly in oom conditions, it's troublesome that hugetlb memory is
> > not displayed. All other meminfo that is emitted will not add up to what
> > is expected, and there is no artifact left in t
On Tue 19-03-13 17:18:12, David Rientjes wrote:
> Particularly in oom conditions, it's troublesome that hugetlb memory is
> not displayed. All other meminfo that is emitted will not add up to what
> is expected, and there is no artifact left in the kernel log to show that
> a potentially signif
Particularly in oom conditions, it's troublesome that hugetlb memory is
not displayed. All other meminfo that is emitted will not add up to what
is expected, and there is no artifact left in the kernel log to show that
a potentially significant amount of memory is actually allocated as
hugepag
6 matches
Mail list logo
