* [dpdk-dev] ABI/API stability towards drivers
@ 2021-07-02 8:00 Morten Brørup
2021-07-02 9:45 ` [dpdk-dev] [dpdk-techboard] " Ferruh Yigit
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Morten Brørup @ 2021-07-02 8:00 UTC (permalink / raw)
To: dpdk-techboard; +Cc: dpdk-dev
Regarding the ongoing ABI stability project, it is suggested to export driver interfaces as internal.
What are we targeting regarding ABI and API stability towards drivers?
-Morten
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [dpdk-dev] [dpdk-techboard] ABI/API stability towards drivers
2021-07-02 8:00 [dpdk-dev] ABI/API stability towards drivers Morten Brørup
@ 2021-07-02 9:45 ` Ferruh Yigit
2021-07-02 12:26 ` Thomas Monjalon
2021-07-07 18:46 ` [dpdk-dev] " Tyler Retzlaff
2 siblings, 0 replies; 4+ messages in thread
From: Ferruh Yigit @ 2021-07-02 9:45 UTC (permalink / raw)
To: Morten Brørup, dpdk-techboard; +Cc: dpdk-dev
On 7/2/2021 10:00 AM, Morten Brørup wrote:
> Regarding the ongoing ABI stability project, it is suggested to export driver interfaces as internal.
>
> What are we targeting regarding ABI and API stability towards drivers?
>
Hi Morten,
It is about some device abstraction libraries, like cryptodev, exposing the
internal driver to library interface to the application. And any change on them
causing an unnecessary ABI break.
So target is not drivers, but hide everything from application that only needs
to be between lib and driver.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] [dpdk-techboard] ABI/API stability towards drivers
2021-07-02 8:00 [dpdk-dev] ABI/API stability towards drivers Morten Brørup
2021-07-02 9:45 ` [dpdk-dev] [dpdk-techboard] " Ferruh Yigit
@ 2021-07-02 12:26 ` Thomas Monjalon
2021-07-07 18:46 ` [dpdk-dev] " Tyler Retzlaff
2 siblings, 0 replies; 4+ messages in thread
From: Thomas Monjalon @ 2021-07-02 12:26 UTC (permalink / raw)
To: Morten Brørup; +Cc: dpdk-techboard, dpdk-dev
02/07/2021 10:00, Morten Brørup:
> Regarding the ongoing ABI stability project, it is suggested to export driver interfaces as internal.
>
> What are we targeting regarding ABI and API stability towards drivers?
No stability for driver interface.
It is recommended to make drivers internal.
If a driver is kept external to DPDK, there is a maintenance cost.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] ABI/API stability towards drivers
2021-07-02 8:00 [dpdk-dev] ABI/API stability towards drivers Morten Brørup
2021-07-02 9:45 ` [dpdk-dev] [dpdk-techboard] " Ferruh Yigit
2021-07-02 12:26 ` Thomas Monjalon
@ 2021-07-07 18:46 ` Tyler Retzlaff
2 siblings, 0 replies; 4+ messages in thread
From: Tyler Retzlaff @ 2021-07-07 18:46 UTC (permalink / raw)
To: Morten Brørup; +Cc: dpdk-techboard, dpdk-dev
On Fri, Jul 02, 2021 at 10:00:11AM +0200, Morten Brørup wrote:
> Regarding the ongoing ABI stability project, it is suggested to export driver interfaces as internal.
>
> What are we targeting regarding ABI and API stability towards drivers?
last discussed the outcome was that there was no promise of api/abi stability
at all for drivers only applications. tech-board may have discussed it
further i don't know.
we (Microsoft) would like to see them evolve to stable abi/api but we
understand the challenges and effort involved. so driver stability is
pretty much the interface consumers problem right now for drivers built
in-tree and out of tree.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-07-07 18:46 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-02 8:00 [dpdk-dev] ABI/API stability towards drivers Morten Brørup
2021-07-02 9:45 ` [dpdk-dev] [dpdk-techboard] " Ferruh Yigit
2021-07-02 12:26 ` Thomas Monjalon
2021-07-07 18:46 ` [dpdk-dev] " Tyler Retzlaff
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).