Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1417490
| From | Sergey Senozhatsky <sergey.senozhatsky@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] mm/zsmalloc: add trace events for zs_compact |
| Date | 2016-06-08 16:20 +0200 |
| Message-ID | <rHMuS-1eQ-33@gated-at.bofh.it> (permalink) |
| References | <rHl1D-tV-7@gated-at.bofh.it> <rHznX-1aY-21@gated-at.bofh.it> <rHAN4-1YC-19@gated-at.bofh.it> <rHE4h-4dP-3@gated-at.bofh.it> <rHFjI-4Tu-29@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hello, On (06/08/16 14:39), Ganesh Mahendran wrote: > >> > On Tue, Jun 07, 2016 at 04:56:44PM +0800, Ganesh Mahendran wrote: > >> >> Currently zsmalloc is widely used in android device. > >> >> Sometimes, we want to see how frequently zs_compact is > >> >> triggered or how may pages freed by zs_compact(), or which > >> >> zsmalloc pool is compacted. > >> >> > >> >> Most of the time, user can get the brief information from > >> >> trace_mm_shrink_slab_[start | end], but in some senario, > >> >> they do not use zsmalloc shrinker, but trigger compaction manually. > >> >> So add some trace events in zs_compact is convenient. Also we > >> >> can add some zsmalloc specific information(pool name, total compact > >> >> pages, etc) in zsmalloc trace. > >> > > >> > Sorry, I cannot understand what's the problem now and what you want to > >> > solve. Could you elaborate it a bit? > >> > > >> > Thanks. > >> > >> We have backported the zs_compact() to our product(kernel 3.18). > >> It is usefull for a longtime running device. > >> But there is not a convenient way to get the detailed information > >> of zs_comapct() which is usefull for performance optimization. > >> Information about how much time zs_compact used, which pool is > >> compacted, how many page freed, etc. sorry, couldn't check my email earlier. zs_compact() is just one of the N sites that are getting called by the shrinker; optimization here will "solve" only 1/N of the problems. are there any trace events in any other shrinker callbacks? why trace_mm_shrink_slab_start()/trace_mm_shrink_slab_end()/etc. don't work you? -ss
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH] mm/zsmalloc: add trace events for zs_compact Ganesh Mahendran <opensource.ganesh@gmail.com> - 2016-06-07 11:00 +0200
Re: [PATCH] mm/zsmalloc: add trace events for zs_compact Minchan Kim <minchan@kernel.org> - 2016-06-08 02:20 +0200
Re: [PATCH] mm/zsmalloc: add trace events for zs_compact Ganesh Mahendran <opensource.ganesh@gmail.com> - 2016-06-08 03:50 +0200
Re: [PATCH] mm/zsmalloc: add trace events for zs_compact Minchan Kim <minchan@kernel.org> - 2016-06-08 07:20 +0200
Re: [PATCH] mm/zsmalloc: add trace events for zs_compact Ganesh Mahendran <opensource.ganesh@gmail.com> - 2016-06-08 08:40 +0200
Re: [PATCH] mm/zsmalloc: add trace events for zs_compact Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-06-08 16:20 +0200
csiph-web