netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Volodymyr Bendiuga <volodymyr.bendiuga@gmail.com>
Cc: Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Volodymyr Bendiuga <valdr.linuxnext@gmail.com>,
	netdev@vger.kernel.org,
	Volodymyr Bendiuga <volodymyr.bendiuga@westermo.se>,
	John Crispin <john@phrozen.org>
Subject: Re: [PATCH net-next 1/3] net:dsa:mv88e6xxx: use hashtable to store multicast entries
Date: Fri, 16 Dec 2016 11:08:02 +0100	[thread overview]
Message-ID: <20161216100802.GA20359@lunn.ch> (raw)
In-Reply-To: <CABHmqqCOYMPA-Py7Uu4gsQ=s8CrQd-tT4-Db+j8eJH9=2s4L2g@mail.gmail.com>

On Fri, Dec 16, 2016 at 10:24:28AM +0100, Volodymyr Bendiuga wrote:
> Hi all,
> 
> Does this mean we all agree on implementing caching
> mechanism in net/dsa layer? If yes, then I can start
> working on it immediately.

Volodymyr

Could you provide us with your test script, which adds multicast MAC
addresses to ports. I would like to do some profiling with it.

	  Thanks
		Andrew

  parent reply	other threads:[~2016-12-16 10:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 13:39 [PATCH net-next 1/3] net:dsa:mv88e6xxx: use hashtable to store multicast entries Volodymyr Bendiuga
2016-12-12 13:54 ` Andrew Lunn
2016-12-12 14:18 ` Andrew Lunn
2016-12-12 15:03 ` Vivien Didelot
     [not found]   ` <CAMr9Lbp5eCg1oyWGN+uiDEcF0VZuKUi87FH6JYTGj6pL82R+Mw@mail.gmail.com>
2016-12-12 16:07     ` Andrew Lunn
2016-12-12 16:37     ` Florian Fainelli
2016-12-12 17:11       ` Vivien Didelot
2016-12-12 19:09       ` Andrew Lunn
2016-12-12 20:03         ` Vivien Didelot
     [not found]         ` <CAMr9LbqyvrRYe_m34Ufzxkf2Vef3LbMQiuoiwVX0mK=hW6euyA@mail.gmail.com>
2016-12-13 15:09           ` Andrew Lunn
     [not found]             ` <CABHmqqB-6-L124hrAjNxd4kO3zYp9R=RM1X6PXyuQW6Hapiv4g@mail.gmail.com>
2016-12-14 10:46               ` Andrew Lunn
     [not found]                 ` <CABHmqqDpiN2kwkTgrM8Qu8EEx3Sjk2yVBy8QQAJppGfJ6-MV5Q@mail.gmail.com>
2016-12-15 17:21                   ` Vivien Didelot
2016-12-15 17:32                     ` Florian Fainelli
2016-12-15 17:50                       ` Vivien Didelot
     [not found]                         ` <CABHmqqCOYMPA-Py7Uu4gsQ=s8CrQd-tT4-Db+j8eJH9=2s4L2g@mail.gmail.com>
2016-12-16  9:31                           ` John Crispin
2016-12-16 10:08                           ` Andrew Lunn [this message]
     [not found]                             ` <CABHmqqAQddcQZqVBi7gTjR40cHx6+aQebmsY3BwJgeEbLsX5Yw@mail.gmail.com>
2016-12-16 11:01                               ` Andrew Lunn
2016-12-23  9:30                                 ` Volodymyr Bendiuga
2016-12-23 10:17                                   ` Andrew Lunn
2016-12-15 17:47                     ` John Crispin
2016-12-12 16:22 ` Vivien Didelot

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=20161216100802.GA20359@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=john@phrozen.org \
    --cc=netdev@vger.kernel.org \
    --cc=valdr.linuxnext@gmail.com \
    --cc=vivien.didelot@savoirfairelinux.com \
    --cc=volodymyr.bendiuga@gmail.com \
    --cc=volodymyr.bendiuga@westermo.se \
    /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).