Ticket #83 (closed enhancement: later)

Opened 6 years ago

Last modified 5 years ago

evaluate process and I/O schedulers

Reported by: laforge@… Owned by: willie_chen@…
Priority: high Milestone:
Component: kernel Version: current svn head
Severity: minor Keywords:
Cc: buglog@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:
Reproducible:

Description

to choose which one is best for our device/application

Change History

comment:1 Changed 6 years ago by laforge@…

IO: I have now disabled the anticipatory scheduler (large, complex) and switched
to the default of the deadline scheduler. If that one gives too little equality
between processes, we can enable the CFQ (which is built as a module in -moko6
kernel)

comment:2 Changed 6 years ago by sean_mosko@…

  • Owner changed from laforge@… to teddy@…
  • Milestone set to Phase 1

comment:3 Changed 6 years ago by alphaone@…

  • Milestone changed from Phase 1 to Phase 2

Optimization can be done when the typical workload is finalized

comment:4 Changed 6 years ago by laforge@…

  • Owner changed from teddy@… to laforge@…

comment:5 Changed 6 years ago by willie_chen@…

  • Owner changed from laforge@… to michael@…

comment:6 Changed 5 years ago by willie_chen@…

  • Owner changed from michael@… to willie_chen@…

comment:7 Changed 5 years ago by willie_chen@…

  • Status changed from new to closed
  • Resolution set to later

It's an evaluation issue.

comment:8 Changed 5 years ago by anonymous

Milestone Phase 2 deleted

Note: See TracTickets for help on using tickets.