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.

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

Already on GitHub? Sign in to your account

Adding huge page volume plugin. #764

Merged
merged 3 commits into from
Jul 17, 2017

Conversation

PiotrProkop
Copy link

Adding support for applications requiring hugetlbfs.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jun 26, 2017
@PiotrProkop
Copy link
Author

@derekwaynecarr @sjenning

pre-allocated huge pages instead of THP.
pre-allocated huge pages instead of THP.

DPDK-based applications are going to request huge pages using `mmap()` system

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to call out how we will ensure this is present/automate it ?

Copy link
Author

@PiotrProkop PiotrProkop Jun 28, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huge page volume plugin will make sure that this mount point will be present. Do you think I should add such comment?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I think that would be useful

**Target 1.8+**

Implement huge page volume plugin. Accounting and limiting huge pages before
`Phase 2` can be done via OIR(opaque integer resources).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will OIR be deprecated in favor of resource classes @vishh ? If so, is it ok to continue leveraging this for alpha features?


// HugePagesSource represents Linux HugeTlbPage https://www.kernel.org/doc/Documentation/vm/hugetlbpage.txt
type HugePagesVolumeSource struct {
// Defaults to 2M

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is architecture specific - defaulting to /proc/meminfo Hugepagesize would allow the proposal to support different archs in the future.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right I will change the proposal 😄

@cmluciano
Copy link

This addresses most of my feedback, but I would like an answer to the OIR question from Vish or Derek.

@derekwaynecarr derekwaynecarr self-assigned this Jul 10, 2017
@derekwaynecarr
Copy link
Member

this is fine. i want to take another pass over the whole proposal this week so we can get a full pr up and start knocking out the code.

@derekwaynecarr derekwaynecarr merged commit 00d7112 into kubernetes:hugepage-proposal Jul 17, 2017
danehans pushed a commit to danehans/community that referenced this pull request Jul 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants