On Mon 28-01-19 10:26:16, Andrew Morton wrote:
> On Fri, 25 Jan 2019 18:24:16 +0100 Michal Hocko wrote:
>
> > > > out_of_memory
> > > > select_bad_process # no task
> > > >
> > > > If Thread1 didn't race it would bail out from try_charge and force the
> > > > charge. We can achieve th
On Fri, 25 Jan 2019 18:24:16 +0100 Michal Hocko wrote:
> > > out_of_memory
> > > select_bad_process # no task
> > >
> > > If Thread1 didn't race it would bail out from try_charge and force the
> > > charge. We can achieve the same by checking tsk_is_oom_victim inside the
> > > oom_loc
On 2019/01/26 3:33, Johannes Weiner wrote:
> On Fri, Jan 25, 2019 at 06:24:16PM +0100, Michal Hocko wrote:
>> On Fri 25-01-19 11:56:24, Johannes Weiner wrote:
>>> It looks like this problem is happening in production systems:
>>>
>>> https://www.spinics.net/lists/cgroups/msg21268.html
>>>
>>> where
On Fri, Jan 25, 2019 at 06:24:16PM +0100, Michal Hocko wrote:
> On Fri 25-01-19 11:56:24, Johannes Weiner wrote:
> > On Wed, Jan 09, 2019 at 11:03:06AM -0800, a...@linux-foundation.org wrote:
> > >
> > > The patch titled
> > > Subject: memcg: do not report racy no-eligible OOM tasks
> > > has
On Fri 25-01-19 11:56:24, Johannes Weiner wrote:
> On Wed, Jan 09, 2019 at 11:03:06AM -0800, a...@linux-foundation.org wrote:
> >
> > The patch titled
> > Subject: memcg: do not report racy no-eligible OOM tasks
> > has been added to the -mm tree. Its filename is
> > memcg-do-not-report
On Wed, Jan 09, 2019 at 11:03:06AM -0800, a...@linux-foundation.org wrote:
>
> The patch titled
> Subject: memcg: do not report racy no-eligible OOM tasks
> has been added to the -mm tree. Its filename is
> memcg-do-not-report-racy-no-eligible-oom-tasks.patch
>
> This patch should soon
6 matches
Mail list logo
