Skip to main content
improved on previous edit by using the SI-recommended abbreviations (thanks goes to https://unix.stackexchange.com/users/100397/roaima for pointing this out, in a review of https://unix.stackexchange.com/review/suggested-edits/312615)
Source Link
Eliah Kagan
  • 4.2k
  • 2
  • 28
  • 39

When in top, typing capital "E" cycles through different memory units (kibKiB, mibMiB, gigGiB, etc -., which are different from kbkB, mbMB and gbGB) in the total memory info:

The image shows tops general memory display with GiB as a unit.

While lower-case "e" does the same individual process lines:

The image shows processes in top where the memory is displayed in MiB

From the manpage:

2c. MEMORY Usage This portion consists of two lines which may express values in kibibytes (KiB) through exbibytes (EiB) depending on the scaling factor enforced with the 'E' interactive command. 

Version Information: top -version: procps-ng version 3.3.9   
System: CentOS 7

When in top, typing capital "E" cycles through different memory units (kib, mib, gig etc - which are different from kb, mb and gb) in the total memory info:

The image shows tops general memory display with GiB as a unit.

While lower-case "e" does the same individual process lines:

The image shows processes in top where the memory is displayed in MiB

From the manpage:

2c. MEMORY Usage This portion consists of two lines which may express values in kibibytes (KiB) through exbibytes (EiB) depending on the scaling factor enforced with the 'E' interactive command. 

Version Information: top -version: procps-ng version 3.3.9  System: CentOS 7

When in top, typing capital "E" cycles through different memory units (KiB, MiB, GiB, etc., which are different from kB, MB and GB) in the total memory info:

The image shows tops general memory display with GiB as a unit.

While lower-case "e" does the same individual process lines:

The image shows processes in top where the memory is displayed in MiB

From the manpage:

2c. MEMORY Usage This portion consists of two lines which may express values in kibibytes (KiB) through exbibytes (EiB) depending on the scaling factor enforced with the 'E' interactive command. 

Version Information: top -version: procps-ng version 3.3.9 
System: CentOS 7

When in top, typing capital "E" cycles through different memory units (kbkib, mbmib, gbgig etc - which are different from kb, mb and gb) in the total memory info:

The image shows tops general memory display with GiB as a unit.

While lower-case "e" does the same individual process lines:

The image shows processes in top where the memory is displayed in MiB

From the manpage:

2c. MEMORY Usage This portion consists of two lines which may express values in kibibytes (KiB) through exbibytes (EiB) depending on the scaling factor enforced with the 'E' interactive command. 

Version Information: top -version: procps-ng version 3.3.9 System: CentOS 7

When in top, typing capital "E" cycles through different memory units (kb, mb, gb etc) in the total memory info:

The image shows tops general memory display with GiB as a unit.

While lower-case "e" does the same individual process lines:

The image shows processes in top where the memory is displayed in MiB

From the manpage:

2c. MEMORY Usage This portion consists of two lines which may express values in kibibytes (KiB) through exbibytes (EiB) depending on the scaling factor enforced with the 'E' interactive command. 

Version Information: top -version: procps-ng version 3.3.9 System: CentOS 7

When in top, typing capital "E" cycles through different memory units (kib, mib, gig etc - which are different from kb, mb and gb) in the total memory info:

The image shows tops general memory display with GiB as a unit.

While lower-case "e" does the same individual process lines:

The image shows processes in top where the memory is displayed in MiB

From the manpage:

2c. MEMORY Usage This portion consists of two lines which may express values in kibibytes (KiB) through exbibytes (EiB) depending on the scaling factor enforced with the 'E' interactive command. 

Version Information: top -version: procps-ng version 3.3.9 System: CentOS 7

Added images
Source Link
Raphael Ahrens
  • 9.9k
  • 5
  • 39
  • 53

When in top, typing capital "E" cycles through different memory units (kb, mb, gb etc) in the total memory info:

enter image description hereThe image shows tops general memory display with GiB as a unit.

While lower-case "e" does the same individual process lines:

enter image description hereThe image shows processes in top where the memory is displayed in MiB

From the manpage:

2c. MEMORY Usage This portion consists of two lines which may express values in kibibytes (KiB) through exbibytes (EiB) depending on the scaling factor enforced with the 'E' interactive command. 

Version Information: top -version: procps-ng version 3.3.9 System: CentOS 7

When in top, typing capital "E" cycles through different memory units (kb, mb, gb etc) in the total memory info:

enter image description here

While lower-case "e" does the same individual process lines:

enter image description here

From the manpage:

2c. MEMORY Usage This portion consists of two lines which may express values in kibibytes (KiB) through exbibytes (EiB) depending on the scaling factor enforced with the 'E' interactive command. 

Version Information: top -version: procps-ng version 3.3.9 System: CentOS 7

When in top, typing capital "E" cycles through different memory units (kb, mb, gb etc) in the total memory info:

The image shows tops general memory display with GiB as a unit.

While lower-case "e" does the same individual process lines:

The image shows processes in top where the memory is displayed in MiB

From the manpage:

2c. MEMORY Usage This portion consists of two lines which may express values in kibibytes (KiB) through exbibytes (EiB) depending on the scaling factor enforced with the 'E' interactive command. 

Version Information: top -version: procps-ng version 3.3.9 System: CentOS 7

cited the manpage and gave version information (was just going to bump your answer, but I do not have the rep yet on this stack exchange).
Source Link
Loading
Source Link
Josh W
  • 3.9k
  • 1
  • 13
  • 2
Loading