From: Eric Dumazet <eric.dumazet@gmail.com>
To: pavel@pavlinux.ru
Cc: Shan Wei <shanwei@cn.fujitsu.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] Sysctl interface to UNIX_INFLIGHT_TRIGGER_GC v.3
Date: Fri, 10 Dec 2010 14:04:33 +0100 [thread overview]
Message-ID: <1291986273.3580.16.camel@edumazet-laptop> (raw)
In-Reply-To: <4D0221A2.4010602@pavlinux.ru>
Le vendredi 10 décembre 2010 à 15:48 +0300, Pavel Vasilyev a écrit :
> On 10.12.2010 06:45, Shan Wei wrote:
> > Pavel Vasilyev wrote, at 12/10/2010 01:26 AM:
> >> Sysctl interface to UNIX_INFLIGHT_TRIGGER_GC.
> >> IMHO convenient for testing.
> >>
> >> +inflight_trigger_gc - INTEGER
> >> + The maximal number of inflight sockets for force garbage collect.
> >> +
> >> + Default: 16000
> >
> > 1) For lower payload and enough memory, it's not necessary to force garbage collection.
> > So set it to 0, disable gc.
>
>
> May be, set default to 2000, and zero to disable
>
zero to disable ?
Maybe you missed commit 9915672d41273f5b77 intent.
If you have no limit (like old kernels), you can freeze your machine,
even if it has terabytes of ram, running a single program, even as a non
root user.
When we discussed about the fix, we said a limit was needed, obviously.
Now you'll have to prove we need to make it a sysctl (yet
another /proc/sys/net parameter, yet another documentation to add...)
Even changing default from 16000 to 2000 must be for a valid reason (a
real use case)
next prev parent reply other threads:[~2010-12-10 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 17:26 [PATCH] Sysctl interface to UNIX_INFLIGHT_TRIGGER_GC v.2 Pavel Vasilyev
2010-12-10 3:45 ` Shan Wei
2010-12-10 12:48 ` [PATCH] Sysctl interface to UNIX_INFLIGHT_TRIGGER_GC v.3 Pavel Vasilyev
2010-12-10 13:04 ` Eric Dumazet [this message]
2010-12-10 20:56 ` 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=1291986273.3580.16.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pavel@pavlinux.ru \
--cc=shanwei@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox