Hello Lisa, On Mon, 10 Dec 2012 14:06:05 -0700 Lisa Mitchell <lisa.mitchell at hp.com> wrote: > On Fri, 2012-12-07 at 05:26 +0000, Atsushi Kumagai wrote: > > Atushi, I put the kernel patch from https://lkml.org/lkml/2012/11/21/90 > that you had in the release notes, along with the modifications you > specified for a 2.6.32 kernel in > http://lists.infradead.org/pipermail/kexec/2012-December/007461.html > on my RHEL 6.3 kernel source, and built a patched kernel in order to > hopefully enable use of the mem map array logic feature during my dump > testing. > > I do not have the use of the 4 TB system again, so I constrained a 256 > GB system to a crashkernel size of 136M, which would cause the cyclic > buffer feature to be used and timed some dumps. > > I compared the dump time on the system with the makedumpfile 1.4 version > that ships with RHEL 6.3, using crashkernel=256M to contain the full > bitmap, to both the patched and unpatched kernels using > makedumpfilev1.5.1GA. Here were the results, using the file timestamps. > All dumps were taken with core_collector makedumpfile -c --message-level > 1 -d 31 > > > 1. RHEL 6.3 2.6.32.279 kernel, makedumpfile 1.4, crashkernel=256M > ls -al --time-style=full-iso 127.0.0.1-2012-12-10-16:44 > total 802160 > drwxr-xr-x. 2 root root 4096 2012-12-10 16:51:36.909648053 -0700 . > drwxr-xr-x. 12 root root 4096 2012-12-10 16:44:59.213529059 > -0700 .. > -rw-------. 1 root root 821396774 2012-12-10 16:51:36.821529854 -0700 > vmcore > > Time to write out the dump file: 6.5 minutes > > > 2. RHEL 6.3 2.6.32.279 kernel, makedumpfile 1.5.1GA, crashkernel=136M > > ls -al --time-style=full-iso 127.0.0.1-2012-12-10-15:17:18 > total 806132 > drwxr-xr-x. 2 root root 4096 2012-12-10 15:27:28.799600723 -0700 . > drwxr-xr-x. 11 root root 4096 2012-12-10 15:17:19.202329188 > -0700 .. > -rw-------. 1 root root 825465058 2012-12-10 15:27:28.774327293 -0700 > vmcore > > Time to write out the dump file: 10 minutes, 10 seconds > > 3. Patched RHEL 6.3 kernel, makedumpfile 1.5.1GA, crashkernel=136M > > ls -al --time-style=full-iso 127.0.0.1-2012-12-10-14:42 ^M:28^M > total 808764^M > drwxr-xr-x. 2 root root 4096 2012-12-10 14:50:04.263144379 > -0700 .^M > drwxr-xr-x. 10 root root 4096 2012-12-10 14:42:29.230903264 > -0700 ..^M > -rw-------. 1 root root 828160709 2012-12-10 14:50:04.212739485 -0700 > vmcore^M > > Time to write out the dump file: 7.5 minutes > > > The above indicates that with the kernel patch we got a dump file write > time 2 minutes shorter than using makedumpfile 1.5.1 without the kernel > patch. However, with the kernel patch (and hopefully this enabled the > mem map array logic feature) I still got a dump time that was about 2 > minutes longer, or in this case about 30% longer than the old > makedumpfile 1.4, using the full bitmap. > > So I still see a regression, which will have to be projected to the > multi TB systems. In cyclic mode, we can save only a chunk of bitmap at a time, this fact forces us to scan each cyclic region twice as below: Step1: To determine the offset of kdump's page data region. Step2: To distinguish whether each page is unnecessary or not. Step1 should be done before writing phase (write_kdump_pages_and_bitmap_cyclic()) and step2 is run while writing phase, the whole scan is needed for each step. On the other hand, v1.4 can execute both step1 and step2 with the temporary bitmap file, the whole scan is done just one time to create the file. It's a disadvantage in performance, but I think it's unavoidable. (There is the exception when the number of cycles is 1, but current version also scan twice in spite of redundancy.) If more performance is needed, I think we should invent other approaches like the idea discussed in the thread below: http://lists.infradead.org/pipermail/kexec/2012-December/007494.html Besides, I think v1.4 with the local disc which can contain the temporary bitmap file is the fastest version for now. > Atushi, am I using the new makedumpfile 1.5.1GA correctly with the > kernel patch? Yes, I think you can use mem_map array logic correctly with the patch. And you can confirm it with -D option. If you didn't meet the conditions to use mem_map array logic, the message below will be showed. "Can't select page_is_buddy handler; follow free lists instead of mem_map array." > I didn't understand how to use the options of makedumpfile you > mentioned, and when I tried with a vmlinux file, and the -x option, > makedumpfile didn't even start, just failed and reset. It might be another problem related -x option. For investigation, could you run the command below and show its messages ? There is no need to run in 2nd kernel environment. # makedumpfile -g vmcoreinfo -x vmlinux Thanks Atsushi Kumagai > > I was hoping with the kernel patch in place, that with the default > settings of makedumpfile, the mem map array logic would automatically be > used. If not, I am still puzzled as to how to invoke it.
