[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5CB44DFD-2807-4FD8-B409-FD28A53DE8B6@gmail.com>
Date: Fri, 23 Dec 2016 10:30:27 +0100
From: Volodymyr Bendiuga <volodymyr.bendiuga@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Vivien Didelot <vivien.didelot@...oirfairelinux.com>,
Florian Fainelli <f.fainelli@...il.com>,
Volodymyr Bendiuga <valdr.linuxnext@...il.com>,
netdev@...r.kernel.org,
Volodymyr Bendiuga <volodymyr.bendiuga@...termo.se>,
John Crispin <john@...ozen.org>
Subject: Re: [PATCH net-next 1/3] net:dsa:mv88e6xxx: use hashtable to store
multicast entries
Hi Andrew,
Here is the program I promised you.
There is a .c and Makefile attached to this mail. Simply type ”make” to build it.
There is a dependency on libnl3, which needs to be installed. If you don’t have it
Just install it: "apt-get install libnl-3-dev libnl-route-3-dev” if you use ubuntu based
Linux.
What the program does is it creates a libnl cache, inserts into it some hardcoded
Multicast entries, and then adds entries to the kernel (to the bridge and to hardware).
By default the program looks for interfaces that have ”eth” in their names. If your interfaces
Have different names, just correct that line in the code. Otherwise it should just run straight away.
When entries are added the timing is presented. By default the program uses vlan id 1. If you need
To override it, just pass "-v 2” or whatever vlan id you wish.
Please try running the program with hash table patch and without. You should see a significant difference.
Let me know if there is something you need help with.
Thanks,
Volodymyr
Download attachment "Makefile" of type "application/octet-stream" (326 bytes)
Download attachment "fdbtest.c" of type "application/octet-stream" (6045 bytes)
> 16 dec. 2016 kl. 12:01 skrev Andrew Lunn <andrew@...n.ch>:
>
> On Fri, Dec 16, 2016 at 11:26:01AM +0100, Volodymyr Bendiuga wrote:
>> Hi Andrew,
>>
>> I don't have any script right now, the code I have is a part of
>> the OS, but I could write simple C program which represents
>> what we are doing with mc entries and send it to you for profiling.
>
> It would be nice to have a benchmark test we can use to test out
> ideas.
>
> Please try to make the code flexible. The slave interface names on my
> boards are probably not the same as on your. Also, the number of ports
> may differ.
>
> Thanks
> Andrew
Powered by blists - more mailing lists