-
Notifications
You must be signed in to change notification settings - Fork 615
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove stages from Pipeline API #5244
Conversation
2923781
to
dbb217b
Compare
CI MESSAGE: [11867574]: BUILD STARTED |
39a401e
to
0491441
Compare
CI MESSAGE: [11867574]: BUILD FAILED |
* @return The number of calls to be made | ||
*/ | ||
DLL_PUBLIC int | ||
daliInputFeedCount(daliPipelineHandle *pipe_handle, const char *input_name); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this corresponds to the daliSetExternalInput...
function set, maybe it would be good to call it daliExternalInputFeedCount
? Alternatively, if this function can be used on any input (not only the external one), maybe the documentation should be modified, since now it points to the daliSetExternal...
function only?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not entirely satisfied with this name. I was thinking about something like InputPrefetchCount
or InputPrefetchFeedCount
.
Alternatively, if this function can be used on any input (not only the external one),
What other inputs are there? Everything that's not external just feeds itself. Even if you called it on some other operator, the information would be non-actionable and even misleading.
dali/pipeline/pipeline.h
Outdated
* @param fill_queue If true, the inputs are fed `InputFeedCount(name)` times; | ||
* otherwise it's fed once. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it be plural?
* @param fill_queue If true, the inputs are fed `InputFeedCount(name)` times; | |
* otherwise it's fed once. | |
* @param fill_queue If true, the inputs are fed `InputFeedCount(name)` times; | |
* otherwise they're fed once. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I guess...
CI MESSAGE: [11881000]: BUILD STARTED |
a317968
to
3cda968
Compare
CI MESSAGE: [11881000]: BUILD FAILED |
CI MESSAGE: [11886704]: BUILD STARTED |
CI MESSAGE: [11888104]: BUILD STARTED |
CI MESSAGE: [11886704]: BUILD FAILED |
CI MESSAGE: [11888104]: BUILD FAILED |
CI MESSAGE: [11907275]: BUILD STARTED |
CI MESSAGE: [11907275]: BUILD FAILED |
CI MESSAGE: [11908302]: BUILD STARTED |
CI MESSAGE: [11908302]: BUILD FAILED |
CI MESSAGE: [11961717]: BUILD STARTED |
CI MESSAGE: [11961717]: BUILD PASSED |
DLL_PUBLIC virtual void RunCPU() = 0; | ||
DLL_PUBLIC virtual void RunMixed() = 0; | ||
DLL_PUBLIC virtual void RunGPU() = 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These functions go away from the interface...
DLL_PUBLIC virtual void RunCPU(); | ||
DLL_PUBLIC virtual void RunMixed(); | ||
DLL_PUBLIC virtual void RunGPU(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...and re-emerge as an implementation detail.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have yet to read a few files, but I am leaving a few comment that crossed my mind so far.
8478c9a
to
4b2a1ef
Compare
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Add Pipeline::Prefetch. Rework prefetching mechanism in Python. Fix tests. Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
4b2a1ef
to
dbf894f
Compare
CI MESSAGE: [12427612]: BUILD STARTED |
CI MESSAGE: [12427612]: BUILD FAILED |
CI MESSAGE: [12427612]: BUILD PASSED |
CI MESSAGE: [12433588]: BUILD STARTED |
Category:
New feature (non-breaking change which adds functionality)
Refactoring (Redesign of existing code that doesn't affect functionality)
Description:
What
Get rid of separate RunCPU/RunGPU from Pipeline and Executor interface
Why
Because it doesn't make sense to have separate APIs for running stages when we want to get rid of stages (or, if you prefer, have a flexible number of stages)
Why we can do it
These APIs are NOT present in Python or C and C++ is not official/stable/whatever
How
Additional information:
Affected modules and functionalities:
Executor, Pipeline, Python frontend for the pipeline, C API, TF plugin
Key points relevant for the review:
Tests:
Existing tests apply - ALL OF THEM except those that called the removed APIs from C++ directly.
Checklist
Documentation
DALI team only
Requirements
REQ IDs: N/A
JIRA TASK: DALI-3743