Re: General slowness with using 64Gb HIGHMEM option on 32-bit kernel

Ok, I found a palliative.

Now I'm working with "mem=6770M" option, that gives me 6072MB RAM (of
6144 total).
Interesting, that if you choose too much, like "mem=6800M", system
behaviour is exactly the same as without any options.

Can it be that kernel incorrectly sets amount of memory to use so such
a situation occurs?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: General slowness with using 64Gb HIGHMEM option on 32-bit kernel
    • From: Rik van Riel <[email protected]>

• References:
  • General slowness with using 64Gb HIGHMEM option on 32-bit kernel
    • From: "Sergey Popov" <[email protected]>
  • Re: General slowness with using 64Gb HIGHMEM option on 32-bit kernel
    • From: Chuck Ebbert <[email protected]>

• Prev by Date: [GIT PULL] Correct the SMAP check in the e820 probe (fixed)
• Next by Date: Re: [PATCH] writeback: remove unnecessary wait in throttle_vm_writeout()
• Previous by thread: Re: General slowness with using 64Gb HIGHMEM option on 32-bit kernel
• Next by thread: Re: General slowness with using 64Gb HIGHMEM option on 32-bit kernel
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]