Re: [RFC 2/8] cxgb4: setup pcie memory window 4 and create p2pmem region

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

Subject: Re: [RFC 2/8] cxgb4: setup pcie memory window 4 and create p2pmem region
From: Logan Gunthorpe <logang@xxxxxxxxxxxx>
Date: Tue, 4 Apr 2017 09:56:48 -0600
Cc: linux-pci@xxxxxxxxxxxxxxx, linux-scsi@xxxxxxxxxxxxxxx, linux-nvme@xxxxxxxxxxxxxxxxxxx, linux-rdma@xxxxxxxxxxxxxxx, linux-nvdimm@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <f269d9e1-8dcf-7970-382e-cb0d9a020efc@grimberg.me>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0


On 04/04/17 04:42 AM, Sagi Grimberg wrote:
> This is weird, why even call this if !use_p2pmem?

I personally find it cleaner than:

if (use_p2pmem)
	setup_memwin_p2pmem(...)

I'm not sure why that's so weird.

Logan

References:
- [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory
  - From: Logan Gunthorpe
- [RFC 2/8] cxgb4: setup pcie memory window 4 and create p2pmem region
  - From: Logan Gunthorpe
- Re: [RFC 2/8] cxgb4: setup pcie memory window 4 and create p2pmem region
  - From: Sagi Grimberg

Prev by Date: Re: [RFC 6/8] nvmet: Be careful about using iomem accesses when dealing with p2pmem
Next by Date: Re: [RFC 3/8] nvmet: Use p2pmem in nvme target
Previous by thread: Re: [RFC 2/8] cxgb4: setup pcie memory window 4 and create p2pmem region
Next by thread: RE: [RFC 2/8] cxgb4: setup pcie memory window 4 and create p2pmem region
Index(es):
- Date
- Thread

[Index of Archives] [DMA Engine] [Linux Coverity] [Linux USB] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI] [Greybus]

Powered by Linux