Allowing multiple instances of kernel protocol to use same table

[Alexander Demenshin]

Hi,

Is there any specific reason why each instance of kernel protocol must 
use unique table?

What I want to achieve is to export different protocols (OSPF, BGP etc) 
to different kernel tables,
but the only way I can do this currently is to use pipe, instead of 
export filter only.

My concern is duplication of data - BGP table has over 500k routes, so 
keeping this in master *and*
piping to another one for kernel export is a waste of resources (both 
RAM and CPU).

Thank you!

-- 
With best regards,
Alexander.