On Tue, Oct 13, 2020 at 1:06 AM Joerg Roedel wrote:
>
> So pre-allocating has its implications. If we decide to pre-allocate on
> x86-32 too, then we should be prepared for that fall-out of the higher
> memory usage.
Ok, fair enough. Probably not worth worrying about then, particularly
since
On Mon, Oct 12, 2020 at 03:07:45PM -0700, Linus Torvalds wrote:
> On Mon, Oct 12, 2020 at 10:24 AM Ingo Molnar wrote:
> >
> > Do not sync vmalloc/ioremap mappings on x86-64 kernels.
> >
> > Hopefully now without the bugs!
>
> Let's hope so.
>
> If this turns out to work this time, can we do a
The pull request you sent on Mon, 12 Oct 2020 19:24:15 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mm-2020-10-12
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c1b4ec85ee40cc7a9f7b48bea9013094f2d88203
Thank you!
--
Deet-doot-dot, I am a
On Mon, Oct 12, 2020 at 10:24 AM Ingo Molnar wrote:
>
> Do not sync vmalloc/ioremap mappings on x86-64 kernels.
>
> Hopefully now without the bugs!
Let's hope so.
If this turns out to work this time, can we do a similar preallocation
of the page directories on 32-bit? Because I think now x86-32
Linus,
Please pull the latest x86/mm git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mm-2020-10-12
# HEAD: 7a27ef5e83089090f3a4073a9157c862ef00acfc x86/mm/64: Update comment
in preallocate_vmalloc_pages()
Do not sync vmalloc/ioremap mappings on x86-64
5 matches
Mail list logo