linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Klaus Ethgen <Klaus+lkml@ethgen.de>
To: Michal Hocko <mhocko@kernel.org>
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:15:27 +0100	[thread overview]
Message-ID: <20170104081527.hq5q4ngevcl3c7k6@ikki.ethgen.ch> (raw)
In-Reply-To: <20170104080639.GB25453@dhcp22.suse.cz>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

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.

Regards
   Klaus
- -- 
Klaus Ethgen                                       http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16            Klaus Ethgen <Klaus@Ethgen.ch>
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Comment: Charset: ISO-8859-1

iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlhsrxoACgkQpnwKsYAZ
9qz1CQv/YLYqrABY+8HfYmRoUEPMgPbmWeSeIRiIgiBoN6XmHQ0hCBLecl6mmGoP
P9RgR62mU9LEtEqvrgFbX+/MXsdVefWozf0C+b3gs5Sym4VHoHvMWm9q1sdY845R
1sbhACXFLzgYYZ+uXwMg+pwYb3ZW70N1GQcUdbEOBWdWzlWcoKVGwIj6awNfX7RH
gOFP3KsXsdPKaIMHmF3+0VamGY1xfbL0kvm4nzqqfrD5YmIbGaZoRqv8lF8yz1b/
JH6SEc6X9gcknvvTCj7EZgq4nmrDW5KYE935CcS85khUdvp80aXe+y5YgBhjfjOx
BYcTxejHgSfEEKEqvhlQ7Pmi49QpYcwxyLU2UTwrXFcxPKY7xm9iPO6Pn/NHSsMF
YCCphIfMv0Rgy/QOATOdECXFhJWzChNEAQTYIl3UrzBT0PAfnr30E0B13dgpfISU
TZPcWYjXsokiHLzqDDjN0VIcXaPfR+RCNQUcCwHUJYRCBY+upuZogLnM6lOHhZWN
aUzVem/l
=kiM7
-----END PGP SIGNATURE-----

--
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>

  reply	other threads:[~2017-01-04  8:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161225205251.nny6k5wol2s4ufq7@ikki.ethgen.ch>
2016-12-26 11:00 ` Michal Hocko
2016-12-27 11:28   ` Michal Hocko
2016-12-30 11:11     ` Michal Hocko
2016-12-30 16:52       ` [KERNEL] " Klaus Ethgen
2016-12-30 17:23         ` Michal Hocko
2017-01-04  8:06           ` Michal Hocko
2017-01-04  8:15             ` Klaus Ethgen [this message]
2017-01-04  8:31               ` [KERNEL] " Michal Hocko
2017-01-04  9:50                 ` [KERNEL] " 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: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=20170104081527.hq5q4ngevcl3c7k6@ikki.ethgen.ch \
    --to=klaus+lkml@ethgen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox