On 12/12/25 7:53 PM, Paulo Guilherme (MGC URPE SDN) wrote:
> Hi Dumitru and Mark,
> 
> Yes, I agree with you. The next few days I will study these patches and
> try backporting of them adapting to ovn-ic, thanks!
> 

Hi Paulo,

Just making sure, do you mean you'll be preparing a v3 with those I-P
graph visualization changes included or are you planning on doing that
as a follow up patch?

Thanks,
Dumitru

> Regards
> 
> Paulo
> 
> Em sex., 12 de dez. de 2025 às 04:54, Dumitru Ceara <[email protected]
> <mailto:[email protected]>> escreveu:
> 
>     Hi Paulo,
> 
>     On 12/11/25 11:20 PM, Mark Michelson via dev wrote:
>     > Wow Paulo, this is fantastic! I think this provides a great
>     > jumping-off point for developing further incremental processing in
>     > ovn-ic.
> 
>     Indeed, thanks a lot for working on this!
> 
>     >
>     > Acked-by: Mark Michelson <[email protected]
>     <mailto:[email protected]>>
>     >
>     > On Wed, Dec 10, 2025 at 7:28 AM Paulo Guilherme Silva via dev
>     > <[email protected] <mailto:[email protected]>> wrote:
>     >>
>     >> Initial implementation adds a single node (ic). This single
>     >> node executes the ovn-ic processing pipeline but does not do so
>     >> incrementally.
>     >>
>     >> In order to develop incremental processing for ovn-ic, the code
>     >> will be organised with a .c/.h file for each I-P node following
>     >> the naming convention en-<node name>.c/.h. These files will
>     >> contain definition of the node data, the main node processing
>     >> functions and change handlers (if any). The purpose of these nodes
>     >> will be coordination of the nodes work and implemention of the
>     >> relevant interfaces to plug into the I-P framework. The actual
>     >> work that will be executed by the node will be organised into
>     >> a companion file or files. Ideally this file will follow the
>     >> naming convention of the node: e.g. en-<node name>.c is
>     >> associated with <node name>.c.
>     >>
>     >> Initial node topology sees the ic node dependent on all DB
>     >> nodes. This structure and approach was heavily influenced
>     >> by the way I+P was developed and evolved in the northd daemon.
>     >>
>     >> Signed-off-by: Paulo Guilherme Silva
>     <[email protected] <mailto:[email protected]>>
>     >>
>     >> ---
> 
>     Commits 2a9e7e2e87db ("northd: controller: Support dumping a visual
>     representation of the I-P graph.") [0] and afcb8c99f4d8 ("docs: Add OVN
>     Incremental Processing Engine documentation.") [1] added and documented
>     support for getting a visual representation of the I-P engine in
>     ovn-northd and ovn-controller [2].
> 
>     With your patch ovn-ic starts using the I-P engine so it might be nice
>     if we add an implementation of inc_proc_graph_dump() in ovn-ic too.
> 
>     Hopefully that helps us later when/if we try to add finer grain
>     incremental processing to ovn-ic.
> 
>     What do you think?
> 
>     Regards,
>     Dumitru
> 
>     [0] https://github.com/ovn-org/ovn/commit/2a9e7e2 <https://
>     github.com/ovn-org/ovn/commit/2a9e7e2>
>     [1] https://github.com/ovn-org/ovn/commit/afcb8c9 <https://
>     github.com/ovn-org/ovn/commit/afcb8c9>
>     [2]
>     https://github.com/ovn-org/ovn/blob/main/Documentation/topics/
>     incremental-processing/incremental-processing.rst#graph-
>     visualization <https://github.com/ovn-org/ovn/blob/main/
>     Documentation/topics/incremental-processing/incremental-
>     processing.rst#graph-visualization>
> 
> 
> 
> 
> /‘Esta mensagem é direcionada apenas para os endereços constantes no
> cabeçalho inicial. Se você não está listado nos endereços constantes no
> cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa
> mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas
> estão imediatamente anuladas e proibidas’./
> 
> / //‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para
> assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não
> poderá aceitar a responsabilidade por quaisquer perdas ou danos causados
> por esse e-mail ou por seus anexos’./
> 

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to