From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: Andrew Lunn <andrew@lunn.ch>, Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-next 0/7] net: ipmr: more cleanups and mfc netlink support
Date: Thu, 26 Nov 2015 17:48:47 +0100 [thread overview]
Message-ID: <565737EF.9030504@cumulusnetworks.com> (raw)
In-Reply-To: <20151126163502.GB4094@lunn.ch>
On 11/26/2015 05:35 PM, Andrew Lunn wrote:
> On Thu, Nov 26, 2015 at 03:23:43PM +0100, Nikolay Aleksandrov wrote:
>> From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
>>
>> Hi,
>> This set continues with the minor cleanups in the first 6 patches and
>> patch 7 adds the first new feature - MFC manipulation via netlink.
>
> Hi Nikolay
>
> Great to see somebody working on multicast.
>
> Do you have any plans to remove the 32 VIF limit?
>
> I've run out if VIFs on a VPN server with lots of clients. I took the
> "quick fix" of recompiling the kernel and userspace with 256 VIFs. But
> it would be nice if you could define a netlink API which does not have
> this limit and modify the core code to be more dynamic.
>
> Andrew
>
Hi Andrew,
I'm glad people are still using it. :-) To answer your question - yes, I plan
to remove that limit, in fact I have a private version where it's done and this
API is the first step, you can see it uses the generic rtnh which supports
ifindex passing, so it'll be a matter of a few small changes to remove it.
The hardest part is keeping current user-space compatible with everything, but
I have the necessary workarounds for that. In the end it should be much more
usable and to some extent without mrtsock application running as well.
Thanks,
Nik
next prev parent reply other threads:[~2015-11-26 16:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 14:23 [PATCH net-next 0/7] net: ipmr: more cleanups and mfc netlink support Nikolay Aleksandrov
2015-11-26 14:23 ` [PATCH net-next 1/7] net: remove unnecessary mroute.h includes Nikolay Aleksandrov
2015-11-26 14:23 ` [PATCH net-next 2/7] net: ipmr: remove unused MFC_NOTIFY flag and make the flags enum Nikolay Aleksandrov
2015-11-26 14:23 ` [PATCH net-next 3/7] net: ipmr: adjust mroute.h style and drop extern Nikolay Aleksandrov
2015-11-26 14:23 ` [PATCH net-next 4/7] net: ipmr: move struct mr_table and VIF_EXISTS to mroute.h Nikolay Aleksandrov
2015-11-26 14:23 ` [PATCH net-next 5/7] net: ipmr: move pimsm_enabled to pim.h and rename Nikolay Aleksandrov
2015-11-26 14:23 ` [PATCH net-next 6/7] net: ipmr: fix setsockopt error return Nikolay Aleksandrov
2015-11-26 14:23 ` [PATCH net-next 7/7] net: ipmr: add mfc newroute/delroute netlink support Nikolay Aleksandrov
2015-11-26 16:35 ` [PATCH net-next 0/7] net: ipmr: more cleanups and mfc " Andrew Lunn
2015-11-26 16:48 ` Nikolay Aleksandrov [this message]
2015-11-30 20:26 ` David Miller
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=565737EF.9030504@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.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;
as well as URLs for NNTP newsgroup(s).