Messages in this thread | | | Subject | Re: [PATCH v17 00/21] per memcg lru lock | From | Alex Shi <> | Date | Tue, 4 Aug 2020 14:14:00 +0800 |
| |
在 2020/8/3 下午11:07, Michal Hocko 写道: > On Thu 30-07-20 10:16:13, Alex Shi wrote: >> >> >> 在 2020/7/30 上午2:06, Hugh Dickins 写道: >>> On Wed, 29 Jul 2020, Alex Shi wrote: >>>> >>>> Is there any comments or suggestion for this patchset? >>>> Any hints will be very appreciated. >>> >>> Alex: it is now v5.8-rc7, obviously too late for this patchset to make >>> v5.9, so I'm currently concentrated on checking some patches headed for >>> v5.9 (and some bugfix patches of my own that I don't get time to send): >>> I'll get back to responding on lru_lock in a week or two's time. >> >> Hi Hugh, >> >> Thanks a lot for response! It's fine to wait longer. >> But thing would be more efficient if review get concentrated... >> I am still too new in mm area. > > I am sorry and owe you a review but it is hard to find time for that. > This is a large change and the review will be really far from trivial. > If this version is mostly stable then I would recommend not posting new > versions and simply remind people you expect the review from by a > targeted ping. >
hi Michal,
Thanks a lot for reminder!
Except a update on patch [PATCH v17 18/21] mm/lru: introduce the relock_page_lruvec function from Alexander, the patchset is stable on 5.8.
Just on linux-next, there are changes on hpage_nr_pages -> thp_nr_pages func name change, and lru_note_cost changes that they need a new update. And I have another 3 more patches, following this patchset which do clean up and optimzing.
Is it worth for a new patchset? or let me just update here?
Thanks Alex
| |