Skip to content
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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FEATURE] Support v2 volume without dedicated CPU cores #7064

Open
derekbit opened this issue Nov 8, 2023 · 1 comment
Open

[FEATURE] Support v2 volume without dedicated CPU cores #7064

derekbit opened this issue Nov 8, 2023 · 1 comment
Labels
area/v2-data-engine v2 data engine (SPDK) investigation-needed Need to identify the case before estimating and starting the development kind/feature Feature request, new feature priority/0 Must be fixed in this release (managed by PO) require/auto-e2e-test Require adding/updating auto e2e test cases if they can be automated require/doc Require updating the longhorn.io documentation require/lep Require adding/updating enhancement proposal
Milestone
v1.8.0

Comments

@derekbit
Copy link
Member

derekbit commented Nov 8, 2023

Is your feature request related to a problem? Please describe (馃憤 if you like this request)

Currently, each instance-manager pod needs a dedicated CPU core for supporting v2 volumes. It makes v2 volume feature is unable to run in a computing resource limited environment.

SPDK supports scheduler feature using lightweight threads for avoiding the high CPU consumption. Even though the feature is still an experimental feature, it is still worth trying and integrating it into v2 volume.

Describe the solution you'd like

Describe alternatives you've considered

Additional context
@derekbit derekbit added kind/feature Feature request, new feature require/auto-e2e-test Require adding/updating auto e2e test cases if they can be automated require/doc Require updating the longhorn.io documentation require/lep Require adding/updating enhancement proposal area/v2-data-engine v2 data engine (SPDK) labels Nov 8, 2023
@github-actions github-actions bot mentioned this issue Nov 8, 2023
Open
@innobead innobead added this to the v1.7.0 milestone Nov 8, 2023
@innobead innobead added priority/0 Must be fixed in this release (managed by PO) investigation-needed Need to identify the case before estimating and starting the development labels Nov 8, 2023
@derekbit derekbit modified the milestones: v1.7.0, v1.8.0 May 17, 2024
@derekbit
Copy link
Member Author

cc @DamiaSan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/v2-data-engine v2 data engine (SPDK) investigation-needed Need to identify the case before estimating and starting the development kind/feature Feature request, new feature priority/0 Must be fixed in this release (managed by PO) require/auto-e2e-test Require adding/updating auto e2e test cases if they can be automated require/doc Require updating the longhorn.io documentation require/lep Require adding/updating enhancement proposal
Projects
None yet
Milestone
v1.8.0
Development

No branches or pull requests
2 participants
@innobead @derekbit