All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Paul Mackerras <paulus@samba.org>,
	davem@davemloft.net, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, devel@openvz.org, xemul@openvz.org
Cc: James Chapman <jchapman@katalix.com>
Subject: Re: [RFC 4/4] net: ppp_generic - introduce net-namespace functionality
Date: Sun, 11 Jan 2009 11:25:22 +0300	[thread overview]
Message-ID: <20090111082522.GC7686@localhost> (raw)
In-Reply-To: <20090111074652.GB7686@localhost>

[Cyrill Gorcunov - Sun, Jan 11, 2009 at 10:46:52AM +0300]
| [Paul Mackerras - Sun, Jan 11, 2009 at 11:33:21AM +1100]
| | Cyrill Gorcunov writes:
| | 
| | > From: Cyrill Gorcunov <gorcunov@gmail.com>
| | > Subecjt: [RFC] net: ppp_generic - introduce net-namespace functionality
| | > 
| | > - Each namespace contain ppp channels and units separately
| | >   with appropriate locks
| | 
| | This looks like a lot of uglification to me.  Why exactly do
| | individual network drivers need to know or care about namespaces?
| | 
| | Paul.
| | 
| 
| Unfortunately in the whole series ppp has been change more
| then others and it's looks ugly indeed that is why it was RFC.
| Namespaces imply isolation of data right? Including private
| data being 'user related' -- ie units passed to user in one
| namespace should not interfere with units passed to user in
| another namespace. So if I will not 'bind' units pool to
| namespaces it would be possible to steal unit from one namespace
| proposed for another namespace. Right?
| 
| 		- Cyrill -

Anyway, thanks for review -- I'll check if I could make this
series less 'ugly'. I just wanna hear what people think about
this series 'in general' (or maybe even test it [James, thanks!] :) --
since the series is RFC and not to include in any kind of tree.

		- Cyrill -

  reply	other threads:[~2009-01-11  8:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090109195154.320495476@gmail.com>
2009-01-09 19:51 ` [RFC 1/4] net: pppoe - code cleanup and helpers Cyrill Gorcunov
2009-01-09 19:51 ` [RFC 2/4] net: pppoe - introduce net-namespace functionality Cyrill Gorcunov
2009-01-09 19:51 ` [RFC 3/4] net: pppol2tp " Cyrill Gorcunov
2009-01-10 11:06   ` James Chapman
2009-01-10 11:13     ` Cyrill Gorcunov
2009-01-10 12:54       ` Cyrill Gorcunov
2009-01-10 13:13         ` James Chapman
2009-01-10 15:05         ` James Chapman
2009-01-10 15:19           ` Cyrill Gorcunov
2009-01-10 16:12             ` Cyrill Gorcunov
2009-01-10 18:14               ` James Chapman
2009-01-10 18:51                 ` Cyrill Gorcunov
2009-01-11  7:36         ` David Miller
2009-01-09 19:51 ` [RFC 4/4] net: ppp_generic " Cyrill Gorcunov
2009-01-10  9:22   ` Cyrill Gorcunov
2009-01-10  9:28     ` Cyrill Gorcunov
2009-01-11  0:33       ` Paul Mackerras
2009-01-11  7:39         ` David Miller
2009-01-11  7:46         ` Cyrill Gorcunov
2009-01-11  8:25           ` Cyrill Gorcunov [this message]
2009-01-11 11:20 Herbert Xu

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=20090111082522.GC7686@localhost \
    --to=gorcunov@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devel@openvz.org \
    --cc=jchapman@katalix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=xemul@openvz.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 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.