On 11/6/22 18:22, Conor Dooley wrote: >> + +------------------+---------+------------------+---------+----------------------------------------------------------+ >> + | Start addr | Offset | End addr | Size | VM area description | >> + +==================+=========+==================+=========+==========================================================+ >> + | 0000000000000000 | 0 | 0000003fffffffff | 256 GB | user-space virtual memory, different per mm | >> + +------------------+---------+------------------+---------+----------------------------------------------------------+ >> + | 0000004000000000 | +256 GB | ffffffbfffffffff | ~16M TB | ... huge, almost 64 bits wide hole of non-canonical | >> + | | | | | virtual memory addresses up to the -256 GB | >> + | | | | | starting offset of kernel mappings. | >> + +------------------+---------+------------------+---------+----------------------------------------------------------+ >> + | Kernel-space virtual memory, shared between all processes: | >> + +------------------+---------+------------------+---------+----------------------------------------------------------+ >> + | ffffffc6fee00000 | -228 GB | ffffffc6feffffff | 2 MB | fixmap | >> + +------------------+---------+------------------+---------+----------------------------------------------------------+ >> + | ffffffc6ff000000 | -228 GB | ffffffc6ffffffff | 16 MB | PCI io | >> + +------------------+---------+------------------+---------+----------------------------------------------------------+ > ^ > Will these numbers remain right-aligned in the formatted doc? They were > aligned before in the text form & no longer appear to be. > These numbers also become wrapped in their cells. However, in order to fix alignment of these, custom CSS is needed, similar to one in StackOverflow [1]. [1]: https://stackoverflow.com/a/7351383 Thanks. -- An old man doll... just what I always wanted! - Clara
