RE: CMA enhancement - non-default areas in x86

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



PCIe NTB 
Documentation/driver-api/ntb.rst

1) Basically PCI bridge between to root complex / PCI switches 
2) using out of OS memory is one solution but then this memory is
Limited for usage by other stack, ex: get_user_pages on this memory will fail, 
Therefore attempting to use it for block layer with (o_direct) will fail. 
 
Acutely any generic stack which attempts to "pin" this memory will fail.

Leonid Ravich 
> -----Original Message-----
> From: gregkh@xxxxxxxxxxxxxxxxxxx <gregkh@xxxxxxxxxxxxxxxxxxx>
> Sent: Wednesday, May 13, 2020 10:14 AM
> To: Idgar, Or
> Cc: linux-kernel@xxxxxxxxxxxxxxx; linux-mm@xxxxxxxxx; Ravich, Leonid
> Subject: Re: CMA enhancement - non-default areas in x86
> 
> On Wed, May 13, 2020 at 07:00:12AM +0000, Idgar, Or wrote:
> > > For what type of device?
> > NTB (Non-Transparent Bridge).
> 
> 
> Very odd quoting style...
> 
> Anyway, what exactly is a non-transparent bridge, and why doesn't your
> bios/uefi implementation properly reserve the memory for it so that the OS
> does not use it?
> 
> thanks,
> 
> greg k-h





[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux