Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

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

Subject: Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
From: Logan Gunthorpe <logang@xxxxxxxxxxxx>
Date: Sat, 15 Apr 2017 22:46:25 -0600
Cc: Bjorn Helgaas <helgaas@xxxxxxxxxx>, Jason Gunthorpe <jgunthorpe@xxxxxxxxxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>, Sagi Grimberg <sagi@xxxxxxxxxxx>, "James E.J. Bottomley" <jejb@xxxxxxxxxxxxxxxxxx>, "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>, Jens Axboe <axboe@xxxxxxxxx>, Steve Wise <swise@xxxxxxxxxxxxxxxxxxxxx>, Stephen Bates <sbates@xxxxxxxxxxxx>, Max Gurtovoy <maxg@xxxxxxxxxxxx>, Keith Busch <keith.busch@xxxxxxxxx>, linux-pci@xxxxxxxxxxxxxxx, linux-scsi <linux-scsi@xxxxxxxxxxxxxxx>, linux-nvme@xxxxxxxxxxxxxxxxxxx, linux-rdma@xxxxxxxxxxxxxxx, linux-nvdimm <linux-nvdimm@xxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Jerome Glisse <jglisse@xxxxxxxxxx>
In-reply-to: <1492311719.25766.37.camel@kernel.crashing.org>
References: <1490911959-5146-1-git-send-email-logang@deltatee.com> <1491974532.7236.43.camel@kernel.crashing.org> <5ac22496-56ec-025d-f153-140001d2a7f9@deltatee.com> <1492034124.7236.77.camel@kernel.crashing.org> <81888a1e-eb0d-cbbc-dc66-0a09c32e4ea2@deltatee.com> <20170413232631.GB24910@bhelgaas-glaptop.roam.corp.google.com> <20170414041656.GA30694@obsidianresearch.com> <1492169849.25766.3.camel@kernel.crashing.org> <630c1c63-ff17-1116-e069-2b8f93e50fa2@deltatee.com> <20170414190452.GA15679@bhelgaas-glaptop.roam.corp.google.com> <1492207643.25766.18.camel@kernel.crashing.org> <bff1e503-95a9-e19f-bfd9-0ff962c63a81@deltatee.com> <CAPcyv4jUeKzKDARp6Z35kdPLKnP-M6aF8X5KpOx55CLyjnj4dA@mail.gmail.com> <1492311719.25766.37.camel@kernel.crashing.org>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0

On 15/04/17 09:01 PM, Benjamin Herrenschmidt wrote:
> Are ZONE_DEVICE pages identifiable based on the struct page alone ? (a
> flag ?)

Well you can't use ZONE_DEVICE as an indicator. They may be regular RAM,
(eg. pmem). It would need a separate flag indicating it is backed by iomem.

Logan
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

References:
- [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Logan Gunthorpe
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Benjamin Herrenschmidt
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Logan Gunthorpe
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Benjamin Herrenschmidt
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Logan Gunthorpe
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Bjorn Helgaas
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Jason Gunthorpe
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Benjamin Herrenschmidt
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Logan Gunthorpe
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Bjorn Helgaas
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Benjamin Herrenschmidt
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Logan Gunthorpe
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Dan Williams
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Benjamin Herrenschmidt

Prev by Date: [PATCH rdma-next] IB/cma: Send MRA for reply messages
Next by Date: Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
Previous by thread: Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
Next by thread: Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
Index(es):
- Date
- Thread

[Index of Archives] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Photo] [Yosemite News] [Yosemite Photos] [Linux Kernel] [Linux SCSI] [XFree86]