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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Limit zfs_dirty_data_max_max to 4G #6081

Merged
merged 1 commit into from
May 1, 2017
Merged

Limit zfs_dirty_data_max_max to 4G #6081

merged 1 commit into from
May 1, 2017

Conversation

behlendorf
Copy link
Contributor

Reinstate default 4G zfs_dirty_data_max_max limit.

Motivation and Context

Issue #6072.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Performance enhancement (non-breaking change which improves efficiency)
  • Code cleanup (non-breaking change which makes code smaller or more readable)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the ZFS on Linux code style requirements.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • All commit messages are properly formatted and contain Signed-off-by.
  • Change has been approved by a ZFS on Linux member.

@behlendorf
Limit zfs_dirty_data_max_max to 4G
00212af 
Reinstate default 4G zfs_dirty_data_max_max limit.

Signed-off-by: Brian Behlendorf <[email protected]>
Issue openzfs#6072
@mention-bot
Copy link

@behlendorf, thanks for your PR! By analyzing the history of the files in this pull request, we identified @grwilson, @prakashsurya and @dankimmel to be potential reviewers.

@behlendorf behlendorf mentioned this pull request Apr 28, 2017
Closed
tuxoko
tuxoko approved these changes Apr 28, 2017
View reviewed changes
Copy link
Contributor

@tuxoko tuxoko left a comment

Choose a reason for hiding this comment

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

Yeah, I forgot to open a pull request of this.

@behlendorf behlendorf merged commit e99932f into openzfs:master May 1, 2017
tonyhutter pushed a commit to tonyhutter/zfs that referenced this pull request May 26, 2017
@behlendorf @tonyhutter
Limit zfs_dirty_data_max_max to 4G
9e9db6d 
Reinstate default 4G zfs_dirty_data_max_max limit.

Reviewed-by: Giuseppe Di Natale <[email protected]>
Reviewed-by: Chunwei Chen <[email protected]>
Reviewed-by: George Melikov <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes openzfs#6072
Closes openzfs#6081
tonyhutter pushed a commit that referenced this pull request Jun 9, 2017
@behlendorf @tonyhutter
Limit zfs_dirty_data_max_max to 4G
a83a4f9 
Reinstate default 4G zfs_dirty_data_max_max limit.

Reviewed-by: Giuseppe Di Natale <[email protected]>
Reviewed-by: Chunwei Chen <[email protected]>
Reviewed-by: George Melikov <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes #6072
Closes #6081
@behlendorf behlendorf deleted the issue-6072 branch April 19, 2021 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dinatale2 dinatale2 dinatale2 approved these changes

@gmelikov gmelikov gmelikov approved these changes

@tuxoko tuxoko tuxoko approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
5 participants
@behlendorf @mention-bot @tuxoko @gmelikov @dinatale2