> -----Original Message-----
> From: David Marchand <david.march...@redhat.com>
> Sent: Friday, November 8, 2024 7:08 PM
> To: Jerin Jacob <jer...@marvell.com>
> Cc: Huichao Cai <chcch...@163.com>; Kiran Kumar Kokkilagadda
> <kirankum...@marvell.com>; Nithin Kumar Dabilpuram
> <ndabilpu...@marvell.com>; yanzhirun_...@163.com; dev@dpdk.org;
> Thomas Monjalon <tho...@monjalon.net>; Robin Jarry <rja...@redhat.com>
> Subject: Re: Re:RE: [EXTERNAL] [PATCH] graph: optimize graph search when
> scheduling nodes
>
> Hello Jerin, On Fri, Nov 8, 2024 at 1: 22 PM Jerin Jacob <jerinj@ marvell.
> com>
> wrote: > > > Is n't breaking the ABI? > > > > So can't we modify the ABI, or
> is
> there any special operation required to modify > >
> Hello Jerin,
Hello David,
>
> On Fri, Nov 8, 2024 at 1:22 PM Jerin Jacob <jer...@marvell.com> wrote:
> > > > Is n't breaking the ABI?
> > >
> > > So can't we modify the ABI, or is there any special operation
> > > required to modify the ABI?
> >
> > Only LTS release (xx.11) can change the ABI after sending deprecation
> > notice.
> > Looking at the pahole output, one option will be making dispatch and
> > new semi fastpath Additions like xstat_off can be min cache aligned
> > to make room for future expansion and to make sure have better
> performance.
>
> Adding holes may be a short term solution, but in my opinion, the slow path
> part should be entirely hidden and we only expose the fp part.
The new cache line alignment items are proposed are fastpath items only.
> Reminder, those holes must be in a "known state" as we release v24.11 so that
> the presence of future additions can be safely detected.
>
>
> --
> David Marchand
