Messages in this thread | | | Subject | Re: [PATCH v2 0/3] printk: replace ringbuffer | From | Prarit Bhargava <> | Date | Wed, 13 May 2020 08:05:00 -0400 |
| |
On 5/1/20 5:40 AM, John Ogness wrote: > Hello, > > Here is a v2 for the first series to rework the printk subsystem. The > v1 and history are here [0]. This first series only replaces the > existing ringbuffer implementation. No locking is removed. No > semantics/behavior of printk are changed. > > The VMCOREINFO is updated. RFC patches for the external tools > crash(8) [1] and makedumpfile(8) [2] have been submitted that allow > the new ringbuffer to be correctly read. > > This series is in line with the agreements [3] made at the meeting > during LPC2019 in Lisbon, with 1 exception: support for dictionaries > will not be discontinued [4]. Dictionaries are stored in a separate > buffer so that they cannot interfere with the human-readable buffer. >
Hey John,
I tested this on two 128-cpu ppc64le power8 boxes, and a 64 core x86_64 box using your prb-test testsuite with the latest upstream kernel. The tests ran successfully for ~16 hours without any problems.
P.
| |