From: starlight@binnacle.cx
To: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, Rafael Aquini <aquini@linux.com>
Subject: Re: [Bugme-new] [Bug 38032] New: default values of /proc/sys/net/ipv4/udp_mem does not consider huge page allocation
Date: Wed, 06 Jul 2011 21:31:15 -0400 [thread overview]
Message-ID: <6.2.5.6.2.20110706212254.05bff4c8@binnacle.cx> (raw)
In-Reply-To: <20110706160318.2c604ae9.akpm@linux-foundation.org>
For anyone who may not have read the bugzilla, a
possibly larger concern subsequently discovered is
that actual kernel memory consumption is double the
total of the values reported by 'netstat -nau', at
least when mostly small packets are received and
a RHEL 5 kernel is in use. The tunable enforces based
on the 'netstat' value rather than the actual value
in the RH kernel. Maybe not an issue in the
mainline, but it took a few additional system
hangs in the lab before we figured this out
and divided the 'udm_mem' maximum value in half.
At 04:03 PM 7/6/2011 -0700, Andrew Morton wrote:
>
>(switched to email. Please respond via emailed reply-to-all,
>not via the bugzilla web interface).
>
>(cc's added)
>
>On Tue, 21 Jun 2011 00:35:22 GMT
>bugzilla-daemon@bugzilla.kernel.org wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=38032
>>
>> Summary: default values of
>/proc/sys/net/ipv4/udp_mem does not
>> consider huge page allocatio
>> Product: Memory Management
>> Version: 2.5
>> Platform: All
>> OS/Version: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: normal
>> Priority: P1
>> Component: Other
>> AssignedTo: akpm@linux-foundation.org
>> ReportedBy: starlight@binnacle.cx
>> Regression: No
>>
>>
>> In the RHEL 5.5 back-port of this tunable we ran into trouble locking up
>> systems because the boot-time default is set based on physical memory does not
>> account for the hugepages= in the boot parameters. So the UDP socket buffer
>> limit can exceed phyisical memory. Don't know if this is an issue in mainline
>> kernels but it seems likely so reporting this as a courtesy. Seems like it
>> would be easy to fix the default to account for the memory reserved by
>> hugepages which is not available for slab allocations.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=714833
>>
>
>Yes, we've made similar mistakes in other places.
>
>I don't think we really have an official formula for what callers
>should be doing here. net/ipv4/udp.c:udp_init() does
>
> nr_pages = totalram_pages - totalhigh_pages;
>
>
>which assumes that totalram_pages does not include the pages which were
>lost to hugepage allocations.
>
>I *think* that this is now the case, but it wasn't always the case - we
>made relatively recent fixes to the totalram_pages maintenance.
>
>Perhaps UDP should be using the misnamed nr_free_buffer_pages()
>here.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-07-07 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-38032-10286@https.bugzilla.kernel.org/>
2011-07-06 23:03 ` [Bugme-new] [Bug 38032] New: default values of /proc/sys/net/ipv4/udp_mem does not consider huge page allocatio Andrew Morton
2011-07-07 1:31 ` starlight [this message]
2011-07-07 3:59 ` [Bugme-new] [Bug 38032] New: default values of /proc/sys/net/ipv4/udp_mem does not consider huge page allocation Eric Dumazet
2011-07-07 4:38 ` Eric Dumazet
2011-07-07 7:27 ` David Miller
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=6.2.5.6.2.20110706212254.05bff4c8@binnacle.cx \
--to=starlight@binnacle.cx \
--cc=akpm@linux-foundation.org \
--cc=aquini@linux.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).