[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <470F61D4.6040808@hitachi.com>
Date: Fri, 12 Oct 2007 21:00:20 +0900
From: Satoshi OSHIMA <satoshi.oshima.fk@...achi.com>
To: David Miller <davem@...emloft.net>, netdev <netdev@...r.kernel.org>
Cc: Hideo AOKI <hideo.aoki.tk@...achi.com>,
Yumiko SUGITA <yumiko.sugita.yf@...achi.com>,
"青木@RedHat" <haoki@...hat.com>,
Andi Kleen <andi@...stfloor.org>,
Evgeniy Polyakov <johnpol@....mipt.ru>,
Herbert Xu <herbert@...dor.apana.org.au>,
Stephen Hemminger <shemminger@...ux-foundation.org>,
吉藤 英明
<yoshfuji@...ux-ipv6.org>
Subject: [PATCH 0/4]UDP memory accounting and limitation(take 5)
Hi,
I revised a patch set of UDP memory accounting and
limitation.
This patch set is for kernel 2.6.23. The differences
from take 4 are
* removing unnessesary EXPORT_SYMBOLs
* adding minimal limit of /proc/sys/net/udp_mem
* bugfix of UDP limit affecting protocol other
than UDP
* introducing __ip_check_max_skb_pages()
* using CTL_UNNUMBERED
* adding udp_mem usage to Documentation/networking/ip_sysctl.txt
How to use UDP memory limitation:
This patch set add
/proc/sys/net/ipv4/udp_mem
as a tuning parameter.
When you give the number that is greater than 4096,
UDP memory limitation will work. The number of pages
for socket buffer is limited up to udp_mem[pages].
Currently this function drops the packet when
it is sent or received and the number of pages for
socket buffer is beyond the limit. It won't collect
the buffer that is already allocated.
On the other hand, udp_mem is specified as 4096,
UDP memory limitaion will not work.
The deafult number of udp_mem is 4096.
Comment, review and test are welcome.
Thanks,
Satoshi Oshima
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists