Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1739811
| From | Michal Hocko <mhocko@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v3] mm: introduce validity check on vm dirtiness settings |
| Date | 2017-09-26 14:00 +0200 |
| Message-ID | <utWGR-4jM-7@gated-at.bofh.it> (permalink) |
| References | <ursae-6K5-21@gated-at.bofh.it> <utVhM-3uw-27@gated-at.bofh.it> <utVUu-3YA-7@gated-at.bofh.it> <utWdR-46A-21@gated-at.bofh.it> <utWxc-4fP-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue 26-09-17 19:45:45, Yafang Shao wrote: > 2017-09-26 19:26 GMT+08:00 Michal Hocko <mhocko@kernel.org>: > > On Tue 26-09-17 19:06:37, Yafang Shao wrote: [...] > >> Anyway, there's no document on that direct limits should not less than > >> background limits. > > > > Then improve the documentation. > > I have improved the kernel documentation as well, in order to make it > more clear for the newbies. Why do we need to update the code then? > >> > To be honest I am not entirely sure this is worth the code and the > >> > future maintenance burden. > >> I'm not sure if this code is a burden for the future maintenance, but > >> I think that if we don't introduce this code it is a burden to the > >> admins. > > > > anytime we might need to tweak background vs direct limit we would have > > to change these checks as well and that sounds like a maint. burden to > > me. > > Would pls. show me some example ? What kind of examples would you like to see. I meant that if the current logic of bacground vs. direct limit changes the code to check it which is at a different place IIRC would have to be kept in sync. That being said, this is my personal opinion, I will not object if there is a general consensus on merging this. I just believe that this is not simply worth adding a single line of code. You can then a lot of harm by setting different values which would pass the added check. -- Michal Hocko SUSE Labs
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v3] mm: introduce validity check on vm dirtiness settings Yafang Shao <laoar.shao@gmail.com> - 2017-09-19 17:00 +0200
Re: [PATCH v3] mm: introduce validity check on vm dirtiness settings Michal Hocko <mhocko@kernel.org> - 2017-09-26 12:30 +0200
Re: [PATCH v3] mm: introduce validity check on vm dirtiness settings Yafang Shao <laoar.shao@gmail.com> - 2017-09-26 13:10 +0200
Re: [PATCH v3] mm: introduce validity check on vm dirtiness settings Michal Hocko <mhocko@kernel.org> - 2017-09-26 13:30 +0200
Re: [PATCH v3] mm: introduce validity check on vm dirtiness settings Yafang Shao <laoar.shao@gmail.com> - 2017-09-26 13:50 +0200
Re: [PATCH v3] mm: introduce validity check on vm dirtiness settings Michal Hocko <mhocko@kernel.org> - 2017-09-26 14:00 +0200
Re: [PATCH v3] mm: introduce validity check on vm dirtiness settings Jan Kara <jack@suse.cz> - 2017-09-26 15:40 +0200
csiph-web