Project

General

Profile

Osd - ScrubSnapTrim IO prioritization

Summary

At the moment, scrub and snap trimming live in their own work queues in the disk tp. As a result, there is not sufficiently fine grained control over how scrub and snap trimming interact with servicing client requests. I propose processing these tasks through the OpWQ instead. That way, each scrub/snap trim item can have an associated priority and cost as with client IO and recovery messages.

Owners

  • Samuel Just (Red Hat)
  • Name (Affiliation)
  • Name

Interested Parties

  • Name (Affiliation)
  • Name (Affiliation)
  • Name

Current Status

Scrub and snap trim currently operate in their own work queues which limits our ability to prioritize client IO vs these tasks.

Detailed Description

Probably, we simply expand the type in the OpWQ to be a Message|ScrubItem|SnapTrimItem and process them appropriately.

Work items

Coding tasks

  1. Task 1
  2. Task 2
  3. Task 3

Build / release tasks

  1. Task 1
  2. Task 2
  3. Task 3

Documentation tasks

  1. Task 1
  2. Task 2
  3. Task 3

Deprecation tasks

  1. Task 1
  2. Task 2
  3. Task 3