Re: [PATCH 8/8] net: Implement socketat.

On 09/23/2010 04:11 PM, jamal wrote:

On Thu, 2010-09-23 at 15:53 +0400, Pavel Emelyanov wrote:

quoted

Why does it matter? You told, that the usage scenario was to
add routes to container. If I do 2 syscalls instead of 1, is
it THAT worse?

Anything to do with socket IO that requires namespace awareness
applies for usage; it could be tcp/udp/etc socket. If it doesnt
make any difference performance wise using one scheme vs other
to write/read heavy messages then i dont see an issue and socketat
is redundant.

That's what my point is about - unless we know why would we need it
we don't need it.

Eric, please clarify, what is the need in creating a socket in foreign
net namespace?