From: Michal Hocko <mhocko@kernel.org>
To: Klaus Ethgen <Klaus+lkml@ethgen.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [KERNEL] Re: [KERNEL] Re: Bug 4.9 and memorymanagement
Date: Wed, 4 Jan 2017 09:31:17 +0100 [thread overview]
Message-ID: <20170104083117.GC25453@dhcp22.suse.cz> (raw)
In-Reply-To: <20170104081527.hq5q4ngevcl3c7k6@ikki.ethgen.ch>
On Wed 04-01-17 09:15:27, Klaus Ethgen wrote:
> Hi Michal,
>
> Am Mi den 4. Jan 2017 um 9:06 schrieb Michal Hocko:
>
> > > Just try to run with the patch and do what you do normally. If you do
> > > not see any OOMs in few days it should be sufficient evidence. From your
> > > previous logs it seems you hit the problem quite early after few hours
> > > as far as I remember.
> >
> > Did you have chance to run with the patch? I would like to post it for
> > inclusion and feedback from you is really useful.
>
> Yes. It runs since 2017-01-01 and without problems until today.
>
> I think it looks good but that is just my feeling. I don't know if it is
> to early to say that.
>
> I also did some heavy git repository actions to big repositories. The
> system is in swap and still no OOMs.
OK, that is a good indication. I will add your Reported-by to the patch
and if you feel comfortable also Tested-by.
Thanks!
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org>
To: Klaus Ethgen <Klaus+lkml@ethgen.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [KERNEL] Re: [KERNEL] Re: Bug 4.9 and memorymanagement
Date: Wed, 4 Jan 2017 09:31:17 +0100 [thread overview]
Message-ID: <20170104083117.GC25453@dhcp22.suse.cz> (raw)
In-Reply-To: <20170104081527.hq5q4ngevcl3c7k6@ikki.ethgen.ch>
On Wed 04-01-17 09:15:27, Klaus Ethgen wrote:
> Hi Michal,
>
> Am Mi den 4. Jan 2017 um 9:06 schrieb Michal Hocko:
>
> > > Just try to run with the patch and do what you do normally. If you do
> > > not see any OOMs in few days it should be sufficient evidence. From your
> > > previous logs it seems you hit the problem quite early after few hours
> > > as far as I remember.
> >
> > Did you have chance to run with the patch? I would like to post it for
> > inclusion and feedback from you is really useful.
>
> Yes. It runs since 2017-01-01 and without problems until today.
>
> I think it looks good but that is just my feeling. I don't know if it is
> to early to say that.
>
> I also did some heavy git repository actions to big repositories. The
> system is in swap and still no OOMs.
OK, that is a good indication. I will add your Reported-by to the patch
and if you feel comfortable also Tested-by.
Thanks!
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-01-04 8:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 20:52 Bug 4.9 and memorymanagement Klaus Ethgen
2016-12-26 11:00 ` Michal Hocko
2016-12-26 11:00 ` Michal Hocko
2016-12-27 11:28 ` Michal Hocko
2016-12-27 11:28 ` Michal Hocko
2016-12-30 11:11 ` Michal Hocko
2016-12-30 11:11 ` Michal Hocko
2016-12-30 16:52 ` [KERNEL] " Klaus Ethgen
2016-12-30 16:52 ` Klaus Ethgen
2016-12-30 17:23 ` Michal Hocko
2016-12-30 17:23 ` Michal Hocko
2017-01-04 8:06 ` Michal Hocko
2017-01-04 8:06 ` Michal Hocko
2017-01-04 8:15 ` [KERNEL] " Klaus Ethgen
2017-01-04 8:15 ` Klaus Ethgen
2017-01-04 8:31 ` Michal Hocko [this message]
2017-01-04 8:31 ` Michal Hocko
2017-01-04 9:50 ` [KERNEL] " Klaus Ethgen
2017-01-04 9:50 ` Klaus Ethgen
[not found] ` <66baf7dd-c5e3-e11c-092f-3a642c306e63@I-love.SAKURA.ne.jp>
2016-12-27 11:48 ` Klaus Ethgen
2016-12-27 12:05 ` Michal Hocko
2016-12-27 12:05 ` Michal Hocko
2016-12-27 12:14 ` Klaus Ethgen
2016-12-27 12:14 ` Klaus Ethgen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170104083117.GC25453@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=Klaus+lkml@ethgen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.