diff options
| author | kshithijiyer <kshithij.ki@gmail.com> | 2019-06-05 19:40:29 +0530 |
|---|---|---|
| committer | Amar Tumballi <amarts@redhat.com> | 2019-06-08 05:45:35 +0000 |
| commit | 2eaf8e846afd71c30f2a6ff6f863a39b1145b8b6 (patch) | |
| tree | 333b3494bf767ab195717fe4e8cdf48398681a7f /doc/developer-guide/brickmux-thread-reduction.md | |
| parent | 2ff76fa45c53b8e291cf70c98b28800f3ed5f6fc (diff) | |
Fixing formatting errors in markdown files
There are a lot of fromatting error is markdown
files peresent under /doc directiory of the project.
Fixing formatting errors and sending a patch.
Fixes: bz#1718273
Change-Id: I08f938088bbaaafddf634f73616ea0dbfe7aedf3
Signed-off-by: kshithijiyer <kshithij.ki@gmail.com>
Diffstat (limited to 'doc/developer-guide/brickmux-thread-reduction.md')
| -rw-r--r-- | doc/developer-guide/brickmux-thread-reduction.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/developer-guide/brickmux-thread-reduction.md b/doc/developer-guide/brickmux-thread-reduction.md index 83462c06b50..7d76e8ff579 100644 --- a/doc/developer-guide/brickmux-thread-reduction.md +++ b/doc/developer-guide/brickmux-thread-reduction.md @@ -1,4 +1,4 @@ -#Resource usage reduction in brick multiplexing +# Resource usage reduction in brick multiplexing Each brick is regresented with a graph of translators in a brick process. Each translator in the graph has its own set of threads and mem pools @@ -24,7 +24,7 @@ threads: 4. aio-thread - changelog and bitrot threads(even when the features are not enabled) -##io-threads +## io-threads io-threads should be made global to the process, having 16+ threads for each brick does not make sense. But io-thread translator is loaded in @@ -38,7 +38,7 @@ This poses performance issues due to lock-contention in the io-threds layer. This also shall be addressed by having multiple locks instead of one global lock for io-threads. -##Posix threads +## Posix threads Most of the posix threads execute tasks in a timely manner, hence it can be replaced with a timer whose handler register a task to synctask framework, once the task is complete, the timer is registered again. With this we can eliminate @@ -56,7 +56,7 @@ api in synctask that can cancel all the tasks from a given translator. For future, this will be replced to use global thread-pool(once implemented). -##Changelog and bitrot threads +## Changelog and bitrot threads In the initial implementation, the threads are not created if the feature is not enabled. We need to share threads across changelog instances if we plan |