From: Jozsef Kadlecsik <kadlec@netfilter.org>
To: "Марк Коренберг" <socketpair@gmail.com>
Cc: netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: ipset hash:net,iface - can not add more than 64 interfaces
Date: Tue, 28 Nov 2023 10:29:54 +0100 (CET) [thread overview]
Message-ID: <597e6941-7fb8-3d5-805f-8f92cbc67bcd@netfilter.org> (raw)
In-Reply-To: <CAEmTpZE=eaHE5CdFfZysXs9SZWWQqvEn56sb5ErmSjHWCpKB1w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
On Tue, 28 Nov 2023, Марк Коренберг wrote:
> Is there any options to store interface indices internally (instead of
> names) ? i.e. if I renamed an interface, it would also “rename” in ipset
> (actually just listing it would resolve indices to current names). This
> feature would speed up matching ipset in network stack because it does
> not require resolving index to name.
No, ipset does not support storing interface indices instead of names.
Best regards,
Jozsef
> вт, 28 нояб. 2023 г. в 09:48, Jozsef Kadlecsik <kadlec@netfilter.org>:
> >
> > Hi,
> >
> > On Tue, 28 Nov 2023, Марк Коренберг wrote:
> >
> > > for i in `seq 0 70`; do ip link del dummy$i; done;
> > > for i in `seq 0 70`; do ip link add type dummy; done;
> > > for i in `seq 0 70`; do ipset add qwe 0.0.0.0/0,dummy$i; done;
> > >
> > > Reveals the problem. Only 64 records can be added, but there are no
> > > obvious restrictions on that. I s it possible to increase the limit ?
> >
> > It is intentional. Such elements can be stored in the same hash bucket
> > only and 64 is the max size I'm willing to sacrifice for that. Please
> > note, that's a huge number and means linear evaluation, i.e. loosing
> > performance.
> >
> > Best regards,
> > Jozsef
> > --
> > E-mail : kadlec@blackhole.kfki.hu, kadlecsik.jozsef@wigner.hu
> > PGP key : https://wigner.hu/~kadlec/pgp_public_key.txt
> > Address : Wigner Research Centre for Physics
> > H-1525 Budapest 114, POB. 49, Hungary
>
>
>
> --
> Segmentation fault
>
--
E-mail : kadlec@blackhole.kfki.hu, kadlecsik.jozsef@wigner.hu
PGP key : https://wigner.hu/~kadlec/pgp_public_key.txt
Address : Wigner Research Centre for Physics
H-1525 Budapest 114, POB. 49, Hungary
next prev parent reply other threads:[~2023-11-28 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 4:29 ipset hash:net,iface - can not add more than 64 interfaces Марк Коренберг
2023-11-28 7:48 ` Jozsef Kadlecsik
2023-11-28 9:17 ` Марк Коренберг
2023-11-28 9:29 ` Jozsef Kadlecsik [this message]
2023-11-28 9:18 ` Марк Коренберг
2023-11-28 9:34 ` Jozsef Kadlecsik
[not found] ` <CAN_K0LQJfH9D9TBMWBxnbUbgWrG5C9YYENU4tkP=WfxRGyAUMA@mail.gmail.com>
2023-11-28 11:09 ` Марк Коренберг
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=597e6941-7fb8-3d5-805f-8f92cbc67bcd@netfilter.org \
--to=kadlec@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=socketpair@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 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).