From: Vasiliy Kulikov <segoon@openwall.com>
To: Solar Designer <solar@openwall.com>
Cc: Colin Walters <walters@verbum.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Pavel Kankovsky <peak@argo.troja.mff.cuni.cz>
Subject: Re: [RFC] ipv4: add ICMP socket kind
Date: Wed, 22 Dec 2010 14:03:18 +0300 [thread overview]
Message-ID: <20101222110318.GA6224@albatros> (raw)
In-Reply-To: <20101221213212.GA26006@openwall.com>
On Wed, Dec 22, 2010 at 00:32 +0300, Solar Designer wrote:
> We use OpenVZ containers
> heavily, and we don't want to run an instance of such process per
> container (up to a few hundred per system).
Besides memory usage daemons cannot allocate reliably unique icmp echo
identifiers as they don't know anything about already assigned idents.
Thanks,
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
prev parent reply other threads:[~2010-12-22 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 18:18 [RFC] ipv4: add ICMP socket kind Vasiliy Kulikov
2010-12-21 18:46 ` Colin Walters
2010-12-21 19:46 ` Solar Designer
2010-12-21 20:46 ` Colin Walters
2010-12-21 21:32 ` Solar Designer
2010-12-22 11:03 ` Vasiliy Kulikov [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=20101222110318.GA6224@albatros \
--to=segoon@openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peak@argo.troja.mff.cuni.cz \
--cc=solar@openwall.com \
--cc=walters@verbum.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).