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: "Stephen Bates" <sbates@xxxxxxxxxxxx>
Date: Thu, 20 Apr 2017 20:43:47 +0000
Accept-language: en-CA, en-US
Cc: Logan Gunthorpe <logang@xxxxxxxxxxxx>, Jason Gunthorpe <jgunthorpe@xxxxxxxxxxxxxxxxxxxx>, Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>, Bjorn Helgaas <helgaas@xxxxxxxxxx>, "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>, Max Gurtovoy <maxg@xxxxxxxxxxxx>, Keith Busch <keith.busch@xxxxxxxxx>, "linux-pci@xxxxxxxxxxxxxxx" <linux-pci@xxxxxxxxxxxxxxx>, linux-scsi <linux-scsi@xxxxxxxxxxxxxxx>, "linux-nvme@xxxxxxxxxxxxxxxxxxx" <linux-nvme@xxxxxxxxxxxxxxxxxxx>, "linux-rdma@xxxxxxxxxxxxxxx" <linux-rdma@xxxxxxxxxxxxxxx>, linux-nvdimm <linux-nvdimm@xxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <CAPcyv4gxBgVsbSez7_dZYkZojUWU0X0txs7FxiJ+Z3xsMt6TqQ@mail.gmail.com>
References: <20170418164557.GA7181@obsidianresearch.com> <cce00131-1f28-27b3-40ab-04f8783f1e5a@deltatee.com> <20170418190138.GH7181@obsidianresearch.com> <df1351d8-b86c-2e21-1948-4688ece5dc2b@deltatee.com> <CAPcyv4gScx6A7vG9VEHpNF41GOy1Nxst7QQ3QC3uZ54bWoxbMg@mail.gmail.com> <20170418210339.GA24257@obsidianresearch.com> <1492564806.25766.124.camel@kernel.crashing.org> <20170419155557.GA8497@obsidianresearch.com> <4899b011-bdfb-18d8-ef00-33a1516216a6@deltatee.com> <CAPcyv4iJ9H8Ykwnjqa2R_D1qG6PsSQmi=QxYH-rKLF_ihrsWyw@mail.gmail.com> <20170419173225.GA11255@redhat.com> <CAPcyv4gxBgVsbSez7_dZYkZojUWU0X0txs7FxiJ+Z3xsMt6TqQ@mail.gmail.com>
User-agent: Microsoft-MacOutlook/f.20.0.170309

> Yes, this makes sense I think we really just want to distinguish host
> memory or not in terms of the dev_pagemap type.

I would like to see mutually exclusive flags for host memory (or not) and persistence (or not).

Stephen

��.n��������+%������w��{.n�����{���fk��ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f

Follow-Ups:
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Dan Williams

References:
- 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: Logan Gunthorpe
- 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: 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: 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: Jason Gunthorpe
- 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: Jerome Glisse
- Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Dan Williams

Prev by Date: Re: [PATCH 00/26] InfiniBand-OCRDMA: Fine-tuning for several function implementations
Next by Date: Re: [PATCH net-next 00/16] Mellanox, mlx5 RDMA net device support
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]