From: "Alexander V. Lukyanov" <lav@netis.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with 2.6.18: memory leak(?)
Date: Tue, 28 Nov 2006 09:42:36 +0300 [thread overview]
Message-ID: <20061128064236.GA19797@night.netis.ru> (raw)
In-Reply-To: <20061127193834.b5ca80db.akpm@osdl.org>
On Mon, Nov 27, 2006 at 07:38:34PM -0800, Andrew Morton wrote:
> It's not necessarily a leak. Networking tried to allocate two
You are right, it is not a leak. Probably the memory usage increased for some
other reason.
> physically-contiguous pages from atomic context, but no such two pages were
> available. The packet will be dropped and things should recover.
>
> Increasing /proc/sys/vm/min_free_kbytes will reduce the frequency somewhat.
> If it's actually a problem, which I doubt?
It is a problem. The messages load syslog and thus disk, network performance
decreases due to lost packets. I'll try to increase min_free_kbytes and
see if it helps.
--
Alexander.
prev parent reply other threads:[~2006-11-28 6:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 12:44 Problem with 2.6.18: memory leak(?) Alexander V. Lukyanov
2006-11-28 3:38 ` Andrew Morton
2006-11-28 6:42 ` Alexander V. Lukyanov [this message]
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=20061128064236.GA19797@night.netis.ru \
--to=lav@netis.ru \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.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