From: Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: davem@davemloft.net, linux-omap@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jiri@mellanox.com, andrew@lunn.ch
Subject: Re: [RFC PATCH net-next 2/5] net: 8021q: vlan_dev: add vid tag for uc and mc address lists
Date: Wed, 5 Dec 2018 02:04:51 +0200 [thread overview]
Message-ID: <20181205000450.GB3507@khorivan> (raw)
In-Reply-To: <756cbb25-3062-91e8-0613-66bb887f937e@gmail.com>
On Tue, Dec 04, 2018 at 11:49:27AM -0800, Florian Fainelli wrote:
...
>>
>> I was thinking also about pinned list of vlans to the address, but in
>> this case this information also has to be synced by members of device
>> chain,
>> because it can be modified on any device level and it looks not very
>> friendly,
>> and at the end address space has addresses with pinned lists of vlans with
>> their pointers. But keeping this stuff in sync is not simplest decision.
>>
>>
>
>I really think we are not communicating properly, it really seems to me
>that if you had the information about the upper device trying to add an
>address to the lower device filter's either through notification or call
>to ndo_set_rxmode, you could be solving your problems. What are we
>missing here?
Sry, missed this one. The problem in getting the owner of address.
Just simple case: vlan/macvlan/real_dev or vlan/.../.../real_dev
The real dev hasn't simple way to get vid the address belong to, or it has?
>--
>Florian
--
Regards,
Ivan Khoronzhuk
next prev parent reply other threads:[~2018-12-05 0:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 18:40 [RFC PATCH net-next 0/5] net: allow hw addresses for virtual devices Ivan Khoronzhuk
2018-12-03 18:40 ` [RFC PATCH net-next 1/5] net: core: dev_addr_lists: add VID to device address space Ivan Khoronzhuk
2018-12-03 18:40 ` [RFC PATCH net-next 2/5] net: 8021q: vlan_dev: add vid tag for uc and mc address lists Ivan Khoronzhuk
2018-12-03 22:17 ` Florian Fainelli
2018-12-03 23:51 ` Ivan Khoronzhuk
2018-12-03 23:57 ` Florian Fainelli
2018-12-04 1:32 ` Ivan Khoronzhuk
2018-12-04 18:57 ` Ivan Khoronzhuk
2018-12-04 19:49 ` Florian Fainelli
2018-12-04 23:42 ` Ivan Khoronzhuk
2019-01-21 23:37 ` Florian Fainelli
2019-01-22 13:12 ` Ivan Khoronzhuk
2019-02-13 16:17 ` Ivan Khoronzhuk
2019-02-14 4:49 ` Florian Fainelli
2019-02-14 13:03 ` Ivan Khoronzhuk
2018-12-05 0:04 ` Ivan Khoronzhuk [this message]
2019-01-08 5:01 ` Florian Fainelli
2019-01-08 18:21 ` Florian Fainelli
2019-01-22 14:15 ` Ivan Khoronzhuk
2018-12-03 18:40 ` [RFC PATCH net-next 3/5] net: 8021q: vlan_dev: add vid tag for vlan device mac address Ivan Khoronzhuk
2018-12-03 18:40 ` [RFC PATCH net-next 4/5] net: ethernet: add default vid len for all ehternet kind devices Ivan Khoronzhuk
2018-12-03 18:40 ` [RFC PATCH net-next 5/5] net: ethernet: ti: cpsw: update mc vlan and add uc vlan support based on addr vids Ivan Khoronzhuk
2018-12-03 22:25 ` [RFC PATCH net-next 0/5] net: allow hw addresses for virtual devices Florian Fainelli
2018-12-04 1:15 ` Ivan Khoronzhuk
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=20181205000450.GB3507@khorivan \
--to=ivan.khoronzhuk@linaro.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jiri@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--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