From: "Ravich, Leonid" <Leonid.Ravich@dell.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"Idgar, Or" <Or.Idgar@Dell.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: RE: CMA enhancement - non-default areas in x86
Date: Wed, 13 May 2020 08:29:16 +0000 [thread overview]
Message-ID: <DM6PR19MB26827EFC4DDC6CB9DD5C52D098BF0@DM6PR19MB2682.namprd19.prod.outlook.com> (raw)
In-Reply-To: <20200513071413.GB766804@kroah.com>
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@linuxfoundation.org <gregkh@linuxfoundation.org>
> Sent: Wednesday, May 13, 2020 10:14 AM
> To: Idgar, Or
> Cc: linux-kernel@vger.kernel.org; linux-mm@kvack.org; 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
next prev parent reply other threads:[~2020-05-13 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 6:13 Idgar, Or
2020-05-13 6:47 ` gregkh
2020-05-13 7:00 ` Idgar, Or
2020-05-13 7:14 ` gregkh
2020-05-13 8:29 ` Ravich, Leonid [this message]
2020-05-13 8:33 ` gregkh
2020-05-13 9:43 ` Ravich, Leonid
2020-05-13 10:04 ` gregkh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DM6PR19MB26827EFC4DDC6CB9DD5C52D098BF0@DM6PR19MB2682.namprd19.prod.outlook.com \
--to=leonid.ravich@dell.com \
--cc=Or.Idgar@Dell.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox