linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Frederic Barrat <fbarrat@linux.ibm.com>
Cc: Paul Mackerras <paulus@samba.org>,
	Max Gurtovoy <maxg@mellanox.com>,
	linuxppc-dev@lists.ozlabs.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 1/3] powerpc/powernv: remove the unused pnv_pci_set_p2p function
Date: Thu, 23 May 2019 09:52:53 +0200	[thread overview]
Message-ID: <20190523075253.GA12946@lst.de> (raw)
In-Reply-To: <99c4c4a9-8a18-61ed-174a-9ffaec3d2e44@linux.ibm.com>

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 what their schedule is like.

FYI, Max who wrote (at least larger parts of) that code is on Cc agreed
that all P2P code should go through the kernel P2P infrastructure and
might be able to spend some cycles on it.

Which still doesn't change anything about that fact that we [1]
generally don't add infrastructure for anything that is not in the
tree.

[1] well, powernv seems to have handles this a little oddly, and now is
on my special watchlist.

  parent reply	other threads:[~2019-05-23  7:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26 12:49 remove dead powernv code Christoph Hellwig
2019-04-26 12:49 ` [PATCH 1/3] powerpc/powernv: remove the unused pnv_pci_set_p2p function Christoph Hellwig
2019-05-06  8:46   ` Frederic Barrat
2019-05-06  9:02     ` Christoph Hellwig
2019-05-23  7:52     ` Christoph Hellwig [this message]
2019-07-09 13:49       ` Max Gurtovoy
2019-07-09 13:59         ` Christoph Hellwig
2019-07-09 14:31           ` Max Gurtovoy
2019-07-09 14:32             ` Christoph Hellwig
2019-07-09 14:37               ` Max Gurtovoy
2019-07-09 14:40                 ` Christoph Hellwig
2019-07-09 15:06                   ` Max Gurtovoy
2019-07-09 15:08                     ` Christoph Hellwig
2019-07-09 20:02                     ` 'gregkh@linuxfoundation.org'
2019-04-26 12:49 ` [PATCH 2/3] powerpc/powernv: remove pnv_pci_{enable,disable}_tunnel Christoph Hellwig
2019-04-26 12:49 ` [PATCH 3/3] powerpc/powernv: remove dead NPU DMA code Christoph Hellwig

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=20190523075253.GA12946@lst.de \
    --to=hch@lst.de \
    --cc=fbarrat@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maxg@mellanox.com \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).