mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2024-12-21 15:56:42 +00:00
Code Issues 1 Projects Releases Wiki Activity

design: push-pull: fix missing markup & drop needless escaping

Browse source 
Additionally: Assorted minor improvements.
This commit is contained in:
Reynaldo H. Verdejo Pinochet 2017-03-20 13:35:13 -07:00
parent c2eb75ee4d
commit 46c2f754fa
1 changed files with 7 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
markdown/design/draft-push-pull.md
View file

@ -24,7 +24,7 @@ Usages of pull based scheduling:
API for pull-based scheduling: API for pull-based scheduling:
- an element that wants to pull data from a peer element needs to call - an element that wants to pull data from a peer element needs to call
the pull\_range() method. This methods requires an offset and a the `pull_range()` method. This method requires an offset and a
size. It is possible to leave the offset and size at -1, indicating size. It is possible to leave the offset and size at -1, indicating
that any offset or size is acceptable, this of course removes the that any offset or size is acceptable, this of course removes the
advantages of getrange based scheduling. advantages of getrange based scheduling.
@ -47,7 +47,7 @@ Current scheduling decision:
- core selects scheduling type starting on sinks by looking at - core selects scheduling type starting on sinks by looking at
existence of loop function on sinkpad and calling existence of loop function on sinkpad and calling
\_check\_pull\_range() on the source pad to activate the pads in `_check_pull_range()` on the source pad to activate the pads in
push/pull mode. push/pull mode.
- element proxies pull mode pad activation to peer pad. - element proxies pull mode pad activation to peer pad.
@ -55,13 +55,13 @@ Current scheduling decision:
Problems: Problems:
- core makes a tough desicion without knowing anything about the - core makes a tough desicion without knowing anything about the
element. Some elements are able to deal with a pull\_range() without element. Some elements are able to deal with a `pull_range()` without
offset while others need full random access. offset while others need full random access.
Requirements: Requirements:
- element should be able to select scheduling method itself based on - element should be able to select scheduling method itself based on
how it can use the peer element pull\_range. This includes if the how it can use the peer element `pull_range()`. This includes if the
peer can operate with or without offset/size. This also means that peer can operate with or without offset/size. This also means that
the core does not need to select the scheduling method anymore and the core does not need to select the scheduling method anymore and
allows for more efficient scheduling methods adjusted for the allows for more efficient scheduling methods adjusted for the
@ -73,7 +73,7 @@ Proposition:
- pads queries scheduling mode of peer pad. This query is rather - pads queries scheduling mode of peer pad. This query is rather
finegrained and allows the element to know if the peer supports finegrained and allows the element to know if the peer supports
offsets and sizes in the get\_range function. A proposition for the offsets and sizes in the `get_range()` function. A proposition for the
query is outlined in draft-query.txt. query is outlined in draft-query.txt.
- pad selects scheduling mode and informs the peer pad of this - pad selects scheduling mode and informs the peer pad of this
@ -81,8 +81,7 @@ Proposition:
Things to query: Things to query:
- pad can do real random access (downstream peer can ask for offset - pad can do real random access (downstream peer can ask for offset `!= -1`)
\!= -1)
- min offset - min offset
@ -92,8 +91,7 @@ Things to query:
- align: all offsets should be aligned with this value. - align: all offsets should be aligned with this value.
- pad can give ranges from A to B length (peer can ask for A ⇐ length - pad can give ranges from A to B length (peer can ask for `A ⇐ length ⇐ B`)
⇐ B)
- min length - min length