On 7/9/2019 5:40 PM, Christoph Hellwig wrote:
On Tue, Jul 09, 2019 at 05:37:18PM +0300, Max Gurtovoy wrote:
On 7/9/2019 5:32 PM, Christoph Hellwig wrote:
On Tue, Jul 09, 2019 at 05:31:37PM +0300, Max Gurtovoy wrote:
Are we ok with working on a solution during kernel-5.3 cycle ?
You can star
On 7/9/2019 5:32 PM, Christoph Hellwig wrote:
On Tue, Jul 09, 2019 at 05:31:37PM +0300, Max Gurtovoy wrote:
Are we ok with working on a solution during kernel-5.3 cycle ?
You can start working on it any time, no need to ask for permission.
I just want to make sure we don't remove it from th
On 7/9/2019 4:59 PM, Christoph Hellwig wrote:
On Tue, Jul 09, 2019 at 01:49:04PM +, Max Gurtovoy wrote:
Hi Greg/Christoph,
Can we leave it meanwhile till we'll find a general solution (for the upcoming
kernel) ?
I guess we can somehow generalize the P2P initialization process for PPC and
; Michael Ellerman
; linuxppc-dev@lists.ozlabs.org; Max Gurtovoy
Subject: Re: [PATCH 1/3] powerpc/powernv: remove the unused pnv_pci_set_p2p
function
On Mon, May 06, 2019 at 10:46:11AM +0200, Frederic Barrat wrote:
> Hi,
>
> The PCI p2p and tunnel code is used by the Mellanox CX5 driver
On Tue, Jul 09, 2019 at 06:06:54PM +0300, Max Gurtovoy wrote:
>
> On 7/9/2019 5:40 PM, Christoph Hellwig wrote:
> > On Tue, Jul 09, 2019 at 05:37:18PM +0300, Max Gurtovoy wrote:
> > > On 7/9/2019 5:32 PM, Christoph Hellwig wrote:
> > > > On Tue, Jul 09, 2019 at 05:31:37PM +0300, Max Gurtovoy wrote
On Tue, Jul 09, 2019 at 06:06:54PM +0300, Max Gurtovoy wrote:
> Also this code was merged before the p2p API for p2pmem.
Yes, without a single user or intention to submit a user, and without
covering the most useful use case (PCIe switches). While at the same
time the people involved completely i
On Tue, Jul 09, 2019 at 05:37:18PM +0300, Max Gurtovoy wrote:
>
> On 7/9/2019 5:32 PM, Christoph Hellwig wrote:
>> On Tue, Jul 09, 2019 at 05:31:37PM +0300, Max Gurtovoy wrote:
>>> Are we ok with working on a solution during kernel-5.3 cycle ?
>> You can start working on it any time, no need to ask
On Tue, Jul 09, 2019 at 05:31:37PM +0300, Max Gurtovoy wrote:
> Are we ok with working on a solution during kernel-5.3 cycle ?
You can start working on it any time, no need to ask for permission.
On Tue, Jul 09, 2019 at 01:49:04PM +, Max Gurtovoy wrote:
> Hi Greg/Christoph,
> Can we leave it meanwhile till we'll find a general solution (for the
> upcoming kernel) ?
> I guess we can somehow generalize the P2P initialization process for PPC and
> leave it empty for now for other archs.
On Mon, May 06, 2019 at 10:46:11AM +0200, Frederic Barrat wrote:
> Hi,
>
> The PCI p2p and tunnel code is used by the Mellanox CX5 driver, at least
> their latest, out of tree version, which is used for CORAL. My
> understanding is that they'll upstream it at some point, though I don't
> know wh
On Mon, May 06, 2019 at 10:46:11AM +0200, Frederic Barrat wrote:
> Hi,
>
> The PCI p2p and tunnel code is used by the Mellanox CX5 driver, at least
> their latest, out of tree version, which is used for CORAL. My
> understanding is that they'll upstream it at some point, though I don't
> know wh
Hi,
The PCI p2p and tunnel code is used by the Mellanox CX5 driver, at least
their latest, out of tree version, which is used for CORAL. My
understanding is that they'll upstream it at some point, though I don't
know what their schedule is like.
Fred
Le 26/04/2019 à 14:49, Christoph Hell
This function has never been used since it has been added to the tree.
We also now have proper PCIe P2P APIs in the core kernel, and any new
P2P support should be using those.
Signed-off-by: Christoph Hellwig
---
arch/powerpc/include/asm/opal.h| 2 -
arch/powerpc/include/asm/pnv-pci
13 matches
Mail list logo
