Page MenuHomeFreeBSD

Eliminate key press requirement "show vmopag" command output.
ClosedPublic

Authored by stevek on Dec 17 2021, 10:04 PM.
Tags
None
Referenced Files
F102390449: D33550.id100246.diff
Mon, Nov 11, 2:59 PM
F102370474: D33550.id.diff
Mon, Nov 11, 8:24 AM
F102357967: D33550.id100316.diff
Mon, Nov 11, 4:29 AM
F102356413: D33550.diff
Mon, Nov 11, 3:59 AM
Unknown Object (File)
Fri, Oct 25, 1:48 AM
Unknown Object (File)
Oct 10 2024, 3:43 PM
Unknown Object (File)
Sep 24 2024, 8:38 PM
Unknown Object (File)
Sep 24 2024, 4:10 PM

Details

Summary

One was required to press a key to continue after every 18 lines of
output. This requirement had been in the "show vmopag" command since it
was introduced, which was many years before paging was added to DDB.
With paging, this explict key check is no longer necessary.

Obtained from: Juniper Networks, Inc.
MFC after: 1 week

Test Plan

Run "show vmopag" from db> prompt and see that it does not need additional
keypresses other than the ones needed for the pager.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 43457
Build 40345: arc lint + arc unit

Event Timeline

jhb added a subscriber: jhb.

Magic 18's and not documented at all,

sys/vm/vm_object.c
2823

Somewhere (perhaps at the end of the loop) you might want to throw in a

if (db_pager_quit)
    return;

To allow exiting the output if it is long. I'm not sure if you really want to put it in all the places that checked before, maybe just at the start of each TAILQ_FOREACH() loop (both outer and inner)?

This revision is now accepted and ready to land.Dec 18 2021, 12:23 AM

Thanks, this saves me a submission.

sys/vm/vm_object.c
2823

This is exactly where I placed these returns in my diff. The output is quite long so I would say they are necessary.

Add db_pager_quit checks per review comments

This revision now requires review to proceed.Dec 20 2021, 12:38 AM
This revision was not accepted when it landed; it landed in state Needs Review.Dec 20 2021, 12:41 AM
This revision was automatically updated to reflect the committed changes.