From: Hideo AOKI <haoki@redhat.com>
To: Bill Fink <billfink@mindspring.com>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Satoshi Oshima <satoshi.oshima.fk@hitachi.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Andi Kleen <andi@firstfloor.org>,
Stephen Hemminger <shemminger@linux-foundation.org>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
yoshfuji@linux-ipv6.org,
Yumiko Sugita <yumiko.sugita.yf@hitachi.com>
Subject: Re: [PATCH 5/5] introduce udp_rmem and udp_wmem
Date: Sat, 03 Nov 2007 00:42:00 +0900 [thread overview]
Message-ID: <472B4548.7090603@redhat.com> (raw)
In-Reply-To: <20071030005248.b0e6e9d2.billfink@mindspring.com>
Hello,
I'm sorry to not respond quickly.
Bill Fink wrote:
> On Mon, 29 Oct 2007, Hideo AOKI wrote:
>
>> This patch added /proc/sys/net/udp_rmem and /proc/sys/net/udp_rmem.
>> Each UDP packet is drooped when the number of pages for socket buffer
>> is beyond the limit and the socket already consumes minimum buffer.
>
> I think you meant /proc/sys/net/ipv4/udp_{r,w}mem above.
You're right. New parameters are added to /proc/sys/net/ipv4.
> Patch not in-lined making replying more difficult.
I apologize for the inconvenient. I'll send patch as in-line next time.
>>> +udp_rmem - INTEGER
>> + Minimal size of receive buffer used by UDP sockets. Each UDP socket
>> + is able to use the size for receiving data, even if total pages of UDP
>> + sockets exceed udp_mem. The unit is byte.
>> + Default: 4096
>> +
>> +udp_wmem - INTEGER
>> + Minimal size of send buffer used by UDP sockets. Each UDP socket is
>> + able to use the size for sending data, even if total pages of UDP
>> + sockets exceed udp_mem. The unit is byte.
>> + Default: 4096
>> +
>> CIPSOv4 Variables:
>>
>> cipso_cache_enable - BOOLEAN
>
> I think either the above should be renamed to udp_{r,w}mem_min, or
> they should be changed to a 3-tuple like tcp_{r,w}mem, and the code
> refactored accordingly (but then what to do about
> /proc/sys/net/core/{r,w}mem_max).
>
> -Bill
I understood. Then, I'll rename them to udp_{r,w}mem_min next take.
Please let me know if there is any suggestions.
Many thanks,
Hideo
--
Hitachi Computer Products (America) Inc.
prev parent reply other threads:[~2007-11-02 15:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 21:18 [PATCH 0/5] UDP memory accounting and limitation (take 6) Hideo AOKI
2007-10-29 21:22 ` [PATCH 1/5] fix send buffer check Hideo AOKI
2007-11-09 12:24 ` Herbert Xu
2007-11-14 3:25 ` Hideo AOKI
2007-10-29 21:23 ` [PATCH 2/5] accounting unit and variable Hideo AOKI
2007-11-09 12:34 ` Herbert Xu
2007-11-14 3:27 ` Hideo AOKI
2007-11-14 3:45 ` Herbert Xu
2007-11-14 3:55 ` David Miller
2007-11-14 15:32 ` Hideo AOKI
2007-11-14 23:30 ` Hideo AOKI
2007-11-15 1:09 ` Herbert Xu
2007-11-15 21:37 ` Hideo AOKI
2007-10-29 21:23 ` [PATCH 3/5] memory accounting Hideo AOKI
2007-11-09 13:07 ` Herbert Xu
2007-10-29 21:23 ` [PATCH 4/5] memory limitation by using udp_mem Hideo AOKI
2007-10-29 21:23 ` [PATCH 5/5] introduce udp_rmem and udp_wmem Hideo AOKI
2007-10-30 4:52 ` Bill Fink
2007-11-02 15:42 ` Hideo AOKI [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=472B4548.7090603@redhat.com \
--to=haoki@redhat.com \
--cc=andi@firstfloor.org \
--cc=billfink@mindspring.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=johnpol@2ka.mipt.ru \
--cc=netdev@vger.kernel.org \
--cc=satoshi.oshima.fk@hitachi.com \
--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.