- Original Message -
>
> Hi Dave,
>
>
> On 8/8/2018 2:24 PM, Dave Anderson wrote:
> >
> > Kazu,
> >
> > Nicely done! It's a huge improvement in readability, cleans up some
> > unnecessary duplication, and tests well on all of my old and new
> > kernel dumpfiles that I have on
Hi Dave,
On 8/8/2018 2:24 PM, Dave Anderson wrote:
>
> Kazu,
>
> Nicely done! It's a huge improvement in readability, cleans up some
> unnecessary duplication, and tests well on all of my old and new
> kernel dumpfiles that I have on hand. Queued for crash-7.2.4:
>
>
>
Kazu,
Nicely done! It's a huge improvement in readability, cleans up some
unnecessary duplication, and tests well on all of my old and new
kernel dumpfiles that I have on hand. Queued for crash-7.2.4:
https://github.com/crash-utility/crash/commit/455da1ae5c7f22ba870aa57e071dad340749bdcd
Hi Kazu,
I'll be back from vacation next week, and I'll take a look at the patch then.
Sounds like a reasonable idea, and I have plenty of "old" sample vmcores.
Thanks, Dave
Sent from my Verizon, Samsung Galaxy smartphone
Original message From: Kazuhito Hagio
Date:
Nowadays, "kmem -s" output can have long lines due to cache name with
memcg name, and I don't think that it's human-readable as it is.
crash> kmem -s
CACHENAME OBJSIZE ALLOCATED TOTAL SLABS SSIZE
8a1522c15380 kmalloc-128(12536:session-11.scope) 128 111
