From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
Elenita Hinds <ecathinds@gmail.com>,
linux-can@vger.kernel.org
Subject: Re: j1939: Attempt to make j1939 network namespace-aware
Date: Thu, 8 Feb 2018 16:05:17 +0100 [thread overview]
Message-ID: <a03d5020-b257-4a81-1b59-bb91102ebe5a@pengutronix.de> (raw)
In-Reply-To: <20180206201650.GD1198@airbook.vandijck-laurijssen.be>
[-- Attachment #1.1: Type: text/plain, Size: 1221 bytes --]
On 02/06/2018 09:16 PM, Kurt Van Dijck wrote:
>> Elenita is right. The idea is to have different network namespaces (e.g. to
>> be used in (Docker-)containers) where each namespace has its own private
>> view to the network.
>
> So absolutely nothing is/should be shared between the namespaces
> from the userspace point of view?
>
> So the ideal j1939 implementation that shares nothing between
> interfaces only needs to forward an extra namespace parameter?
>
> How about ... /proc parameters? or Module parameters?
> or is that the main argument against them?
For now all proc related stuff is removed. There are two clean patches
to add things back or rather have them for reference in the j1939-proc
branch:
https://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git/log/?h=j1939-proc
> Can different namespaces re-use interface numbers (ifindex)?
>
> Anyway, I can start to take a look.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-02-08 15:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 20:31 j1939: Attempt to make j1939 network namespace-aware Elenita Hinds
2018-02-05 20:44 ` Kurt Van Dijck
2018-02-06 16:15 ` Elenita Hinds
2018-02-06 18:30 ` Oliver Hartkopp
2018-02-06 20:16 ` Kurt Van Dijck
2018-02-08 15:05 ` Marc Kleine-Budde [this message]
2018-02-08 21:13 ` Oliver Hartkopp
2018-02-06 8:52 ` Robert Schwebel
2018-02-06 20:37 ` Kurt Van Dijck
2018-02-07 16:41 ` Elenita Hinds
2018-02-08 15:08 ` Marc Kleine-Budde
2018-02-08 16:26 ` Elenita Hinds
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=a03d5020-b257-4a81-1b59-bb91102ebe5a@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=ecathinds@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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.