netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: den@sw.ru
Cc: ebiederm@xmission.com, den@openvz.org, containers@lists.osdl.org,
	netdev@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH 2.6.25] netns: struct net content re-work
Date: Tue, 11 Dec 2007 02:27:24 -0800 (PST)	[thread overview]
Message-ID: <20071211.022724.142575368.davem@davemloft.net> (raw)
In-Reply-To: <475E3D59.10804@sw.ru>

From: "Denis V. Lunev" <den@sw.ru>
Date: Tue, 11 Dec 2007 10:33:45 +0300

> Eric W. Biederman wrote:
> > The idea of separate structures make sense, and seems needed and useful.
> > 
> > "Denis V. Lunev" <den@openvz.org> writes:
> > 
> >> diff --git a/include/net/netns/unix.h b/include/net/netns/unix.h
> >> new file mode 100644
> >> index 0000000..27b4e7f
> >> --- /dev/null
> >> +++ b/include/net/netns/unix.h
> >                    ^^^^^^
> > Given that we are making this per protocol adding a separate directory
> > to hold them seems to be the wrong grouping.  Ideally we want everything
> > for the protocol all together in the same location so it is easy
> > to find.  Possibly with a user/kernel split.
> > 
> > So perhaps unix_net.h
> The idea was simple:
> - I can name 5 files right now
> - I want them to be shown to gather by ls
> - so, there are 2 ways, namely:
>   # include/net/netns/unix.h
>   # include/net/netns-unix.h

I have no real objection to the new directory.

      reply	other threads:[~2007-12-11 10:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 16:36 [PATCH 2.6.25] netns: struct net content re-work Denis V. Lunev
2007-12-10 17:32 ` Daniel Lezcano
2007-12-10 17:50   ` Kirill Korotaev
2007-12-11  4:04     ` Eric W. Biederman
2007-12-11  4:12       ` David Miller
2007-12-11  3:52 ` Eric W. Biederman
     [not found]   ` <m1prxd28h3.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-12-11  7:33     ` Denis V. Lunev
2007-12-11 10:27       ` David Miller [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=20071211.022724.142575368.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=containers@lists.osdl.org \
    --cc=den@openvz.org \
    --cc=den@sw.ru \
    --cc=ebiederm@xmission.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.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).