From: "Gangurde, Abhijit" <abhijit.gangurde@amd.com>
To: David Marchand <david.marchand@redhat.com>
Cc: "Gupta, Nipun" <Nipun.Gupta@amd.com>,
"Agarwal, Nikhil" <nikhil.agarwal@amd.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <Ferruh.Yigit@amd.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Subject: RE: [PATCH v3] bus/cdx: provide driver flag for optional resource mapping
Date: Fri, 13 Oct 2023 11:51:48 +0000 [thread overview]
Message-ID: <DM4PR12MB77654FC47773557B308390668FD2A@DM4PR12MB7765.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8wfxW_FQj9mWFjZWotM=g4xUVzsCdCXDnPqh+F=hkizrg@mail.gmail.com>
> > > > +/**
> > > > + * Map the CDX device resources in user space virtual memory address.
> > > > + *
> > > > + * Note that driver should not call this function when flag
> > > > + * RTE_CDX_DRV_NEED_MAPPING is set, as EAL will do that for
> > > > + * you when it's on.
> > >
> > > Why should we export this function in the application ABI, if it is
> > > only used by drivers?
> >
> > This can be called from an application as well if this flag is not set hence, we
> need to export this function.
>
> What kind of applications / in which usecase, one would need to map
> the device resources?
> Except a driver?
I understand that it is probably not the ideal use case, but some of the customers
are using a single application which also registers itself as driver. Probably such
applications need to use internal APIs instead of making these APIs external.
Will analyze it further and send another rev of this patch.
Thanks,
Abhijit
next prev parent reply other threads:[~2023-10-13 11:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 10:39 [PATCH] " Abhijit Gangurde
2023-07-04 11:22 ` Gupta, Nipun
2023-07-05 6:52 ` [PATCH v2] " Abhijit Gangurde
2023-07-11 5:51 ` [PATCH v3] " Abhijit Gangurde
2023-07-11 15:05 ` Gupta, Nipun
2023-09-29 15:17 ` David Marchand
2023-10-04 10:06 ` Gangurde, Abhijit
2023-10-04 12:54 ` David Marchand
2023-10-13 11:51 ` Gangurde, Abhijit [this message]
2023-10-13 12:15 ` David Marchand
2023-07-07 8:35 ` [PATCH] " Gupta, Nipun
2023-10-16 9:16 ` [PATCH v4 1/1] " Abhijit Gangurde
2023-10-16 15:21 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM4PR12MB77654FC47773557B308390668FD2A@DM4PR12MB7765.namprd12.prod.outlook.com \
--to=abhijit.gangurde@amd.com \
--cc=Ferruh.Yigit@amd.com \
--cc=Nipun.Gupta@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nikhil.agarwal@amd.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).