From: Satoshi OSHIMA <satoshi.oshima.fk@hitachi.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.org>,
David Miller <davem@davemloft.net>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
Herbert Xu <herbert@gondor.apana.org.au>,
netdev <netdev@vger.kernel.org>, ?? ?? <yoshfuji@linux-ipv6.org>,
Yumiko SUGITA <yumiko.sugita.yf@hitachi.com>,
"??@RedHat" <haoki@redhat.com>
Subject: Re: [RFC/PATCH 4/4] UDP memory usage accounting (take 4): memory limitation
Date: Thu, 11 Oct 2007 21:51:14 +0900 [thread overview]
Message-ID: <470E1C42.1050901@hitachi.com> (raw)
In-Reply-To: <20071005085257.24b2e5cc@freepuppy.rosehill>
Hi Stephen,
Thank you for your comment.
>> {
>> + .ctl_name = NET_UDP_MEM,
>> + .procname = "udp_mem",
>> + .data = &sysctl_udp_mem,
>> + .maxlen = sizeof(sysctl_udp_mem),
>> + .mode = 0644,
>> + .proc_handler = &proc_dointvec
>> + },
>> + {
>> .ctl_name = NET_TCP_APP_WIN,
>> .procname = "tcp_app_win",
>> .data = &sysctl_tcp_app_win,
>
> if you use &proc_dointvec_minmax, then you could inforce min/max
> values for udp_mem for the sysctl
udp_mem has two meanings:
* turn off this limitation function (currently udp_mem<=4096)
* limit udp memory (currently udp_mem>4096)
To realize this, udp_mem is evaluated whether udp_mem equals
4096 or smaller in UDP and IP layers.
If udp_mem has proc_dointvec_minmax or dedicated proc handler,
turn off check must be done in UDP and IP layers. This means
there is no reduction of the check in UDP and IP layers.
If you pointed out that minus value of udp_mem is strange,
I agree. I'll fix it.
How about this?
min=4096 (and turn off limitation)
udp_mem>4096 (and turn on limitation)
Satoshi Oshima
next prev parent reply other threads:[~2007-10-11 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 14:59 [RFC/PATCH 0/4]UDP memory accounting (take 4) Satoshi OSHIMA
2007-10-05 15:00 ` [RFC/PATCH 1/4] UDP memory usage accounting (take 4): fix send buffer check Satoshi OSHIMA
2007-10-05 15:01 ` [RFC/PATCH 2/4] UDP memory usage accounting (take 4): accounting unit and variable Satoshi OSHIMA
2007-10-07 10:09 ` Evgeniy Polyakov
2007-10-10 8:14 ` Satoshi OSHIMA
2007-10-05 15:02 ` [RFC/PATCH 3/4] UDP memory usage accounting (take 4): memory usage accounting Satoshi OSHIMA
2007-10-05 15:02 ` [RFC/PATCH 4/4] UDP memory usage accounting (take 4): memory limitation Satoshi OSHIMA
2007-10-05 15:52 ` Stephen Hemminger
2007-10-11 12:51 ` Satoshi OSHIMA [this message]
2007-10-11 19:46 ` Stephen Hemminger
2007-10-12 11:58 ` Satoshi OSHIMA
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=470E1C42.1050901@hitachi.com \
--to=satoshi.oshima.fk@hitachi.com \
--cc=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=haoki@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=johnpol@2ka.mipt.ru \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=yoshfuji@linux-ipv6.org \
--cc=yumiko.sugita.yf@hitachi.com \
/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.