RFC: Upgrade filter integer size to 64-bit

Maria Matějka maria.matejka at nic.cz
Mon Mar 28 22:51:47 CEST 2022


Hello!

I'm curious as well and I'd like to ask you also, if you could, to send me (privately) a binary and a corefile of such a case you are writing about. I'll inspect the memory and tell exactly how much you'd be affected by the u32->u64 change.

Thanks a lot!
Maria

On March 28, 2022 8:18:09 PM UTC, Douglas Fischer <fischerdouglas at gmail.com> wrote:
>Hello Trisha!
>
>This scenario you mentioned made me curious!
>
>Can you comment a little (as far as possible respecting contracts) how is
>this scenario with little memory and many Kernel routes?
>
>What kind of hardware?
>Where would this be applied?
>
>Em seg., 28 de mar. de 2022 às 13:55, Trisha Biswas <tbiswas at fastly.com>
>escreveu:
>
>> We do have use cases where we run BIRD in low memory environments with a
>> lot of routes in the kernel, so moving everything to 64-bits could
>> potentially hurt these scenarios. Option #3 would be very confusing, so
>> we'd have to vote for keeping things as is.
>>
>> Thanks,
>> Trisha
>> --
>>
>> *Trisha Biswas* | Sr. Software Engineer, Network Systems
>> fastly.com | @fastly <https://twitter.com/fastly> | LinkedIn
>> <http://www.linkedin.com/company/fastly>
>>
>>
>> On Mon, Mar 28, 2022 at 5:04 AM Mathew Heard <me at mheard.com> wrote:
>>
>>> Is there even any userbase running bird on embedded hardware (that might
>>> be adversely affected)?
>>>
>>> Dn42 comes to mind. Perhaps? But realistically we aren't talking about
>>> much of an increase surely?
>>>
>>> Other than that I like 64bit only.
>>>
>>> On Mon, 28 Mar 2022, 10:20 pm Douglas Fischer, <fischerdouglas at gmail.com>
>>> wrote:
>>>
>>>> I need to agree with Toke!
>>>> "having Bird behave differently on different archs is bound to be
>>>> incredibly confusing..."
>>>>
>>>> And, on the other hand, what would be the downside of having everything
>>>> in 64?
>>>> Using a little more memory than might be the minimum usable?
>>>>
>>>> This kind of care I see being taken for applications that run platforms
>>>> with serious memory limitations.
>>>> I don't see that this is BIRD's niche.
>>>>
>>>>
>>>> In a real scenario of high demand using BIRD, how much memory would be
>>>> "wasted"?
>>>> In these real high demand scenarios, who uses 32bit these days?
>>>>
>>>> I would worry more about CPU cycles.
>>>>
>>>> Em sáb., 26 de mar. de 2022 às 19:19, Toke Høiland-Jørgensen <
>>>> toke at toke.dk> escreveu:
>>>>
>>>>> Maria Matejka <maria.matejka at nic.cz> writes:
>>>>>
>>>>> > Is there anybody who would try to convince me that I shouldn't make
>>>>> > filter integers and route attribute integers both 64 bits wide?
>>>>>
>>>>> I think switching everything to 64-bits sounds quite sensible. Whatever
>>>>> you do, please don't go with option 3, though, having Bird behave
>>>>> differently on different archs is bound to be incredibly confusing... :)
>>>>>
>>>>> -Toke
>>>>>
>>>>
>>>>
>>>> --
>>>> Douglas Fernando Fischer
>>>> Engº de Controle e Automação
>>>>
>>>
>
>-- 
>Douglas Fernando Fischer
>Engº de Controle e Automação

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20220328/4bb44235/attachment.htm>


More information about the Bird-users mailing list