From: Johannes Berg <johannes@sipsolutions.net>
To: Vadim Kochan <vadim4j@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH net-next] Allow to set net namespace for wireless device via RTM_LINK
Date: Mon, 05 Jan 2015 10:22:04 +0100 [thread overview]
Message-ID: <1420449724.1898.1.camel@sipsolutions.net> (raw)
In-Reply-To: <CAMw6YJKLWQmT-fqg1QLDHbCxnpxWyJUSX+wvOB_pFyE=8HfSfQ@mail.gmail.com> (sfid-20141224_104849_030943_677BDE3C)
On Wed, 2014-12-24 at 11:48 +0200, Vadim Kochan wrote:
> 1) Set NETIF_F_NETNS_LOCAL for phy wireless device only if there
> is at least one virtual interface which was created on it
You mean at least two? I'd think the behaviour becomes hard to predict,
but I guess ultimately that'd be somewhat reasonable.
> 2) What about to inherit netns for newer created interfaces from
> the phy device ?
Hmm? This already happens - a given phy is only in a single netns and
all interfaces must be created in the same netns.
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Vadim Kochan <vadim4j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>,
"netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH net-next] Allow to set net namespace for wireless device via RTM_LINK
Date: Mon, 05 Jan 2015 10:22:04 +0100 [thread overview]
Message-ID: <1420449724.1898.1.camel@sipsolutions.net> (raw)
In-Reply-To: <CAMw6YJKLWQmT-fqg1QLDHbCxnpxWyJUSX+wvOB_pFyE=8HfSfQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (sfid-20141224_104849_030943_677BDE3C)
On Wed, 2014-12-24 at 11:48 +0200, Vadim Kochan wrote:
> 1) Set NETIF_F_NETNS_LOCAL for phy wireless device only if there
> is at least one virtual interface which was created on it
You mean at least two? I'd think the behaviour becomes hard to predict,
but I guess ultimately that'd be somewhat reasonable.
> 2) What about to inherit netns for newer created interfaces from
> the phy device ?
Hmm? This already happens - a given phy is only in a single netns and
all interfaces must be created in the same netns.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-01-05 9:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 20:35 [PATCH net-next] Allow to set net namespace for wireless device via RTM_LINK Vadim Kochan
2014-09-18 21:25 ` Johannes Berg
2014-09-18 21:25 ` Johannes Berg
2014-10-14 12:16 ` vadim4j
2014-10-20 9:47 ` Johannes Berg
2014-10-20 9:47 ` Johannes Berg
2014-10-20 10:46 ` Marcel Holtmann
2014-10-20 10:46 ` Marcel Holtmann
2014-10-20 10:52 ` Johannes Berg
2014-10-20 10:52 ` Johannes Berg
2014-12-24 9:48 ` Vadim Kochan
2015-01-05 9:22 ` Johannes Berg [this message]
2015-01-05 9:22 ` Johannes Berg
2015-01-12 9:07 ` Vadim Kochan
2015-01-12 9:42 ` Johannes Berg
2015-01-12 9:57 ` Vadim Kochan
2015-01-12 9:58 ` Johannes Berg
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=1420449724.1898.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=vadim4j@gmail.com \
/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.