From: James Smart <jsmart2021@gmail.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: linux-scsi@vger.kernel.org,
Dick Kennedy <dick.kennedy@broadcom.com>,
James Smart <james.smart@broadcom.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Mark Rutland <mark.rutland@arm.com>James Smart
<james.smart@broadcom.com>
Subject: Re: [PATCH v2 04/13] lpfc: Add push-to-adapter support to sli4
Date: Wed, 7 Feb 2018 07:42:27 -0800 [thread overview]
Message-ID: <d10b5cc0-b1b6-7f36-37fb-e9e40a77ba6d@gmail.com> (raw)
In-Reply-To: <20180207102759.qzzqleujqhxnenna@linux-x5ow.site>
On 2/7/2018 2:27 AM, Johannes Thumshirn wrote:
> On Wed, Feb 07, 2018 at 10:51:57AM +0100, Johannes Thumshirn wrote:
>>> + /* Enable combined writes for DPP aperture */
>>> + pg_addr = (unsigned long)(wq->dpp_regaddr) & PAGE_MASK;
>>> +#ifdef CONFIG_X86
>>> + rc = set_memory_wc(pg_addr, 1);
>>> + if (rc) {
>>> + lpfc_printf_log(phba, KERN_ERR, LOG_INIT,
>>> + "3272 Cannot setup Combined "
>>> + "Write on WQ[%d] - disable DPP\n",
>>> + wq->queue_id);
>>> + phba->cfg_enable_dpp = 0;
>>> + }
>>> +#else
>>> + phba->cfg_enable_dpp = 0;
>>> +#endif
>>> + } else
>>> + wq->db_regaddr = phba->sli4_hba.WQDBregaddr;
>>
>> I don't really like the set_memory_wc() call here. Neither do I like the ifdef
>> CONFIG_X86 special casing.
>>
>> If you really need write combining, can't you at least use ioremap_wc()?
>
> Coming back to this again (after talking to our ARM/POWER folks internally).
> Is this really x86 specific here? I know there are servers with other architectures
> using lpfcs out there.
>
> I _think_ write combining should be possible on other architectures (that have
> PCIe and aren't dead) as well.
>
> The ioremap_wc() I suggested is probably wrong.
>
> So can you please revisit this? I CCed Mark and Michael, maybe they can help
> here.
yes - we really are looking for write combining. We were following the
lead of a couple of other entities in the kernel and hadn't found the
right combination for something other than X86. We figured we would come
back and add the non-86 enablements later when we found the right options.
-- james
next prev parent reply other threads:[~2018-02-07 15:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 2:28 [PATCH v2 00/13] lpfc new hardware patches for 12.0.0.0 James Smart
2018-02-07 2:28 ` [PATCH v2 01/13] lpfc: Rework lpfc to allow different sli4 cq and eq handlers James Smart
2018-02-07 9:01 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 02/13] lpfc: Rework sli4 doorbell infrastructure James Smart
2018-02-07 9:13 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 03/13] lpfc: Add SLI-4 if_type=6 support to the code base James Smart
2018-02-07 9:17 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 04/13] lpfc: Add push-to-adapter support to sli4 James Smart
2018-02-07 9:51 ` Johannes Thumshirn
2018-02-07 10:27 ` Johannes Thumshirn
2018-02-07 15:42 ` James Smart [this message]
2018-02-13 5:59 ` Michael Ellerman
2018-02-13 17:37 ` James Smart
2018-02-07 2:28 ` [PATCH v2 05/13] lpfc: Add PCI Ids for if_type=6 hardware James Smart
2018-02-07 9:52 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 06/13] lpfc: Add 64G link speed support James Smart
2018-02-07 9:58 ` Johannes Thumshirn
2018-02-07 15:38 ` James Smart
2018-02-07 15:40 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 07/13] lpfc: Add if_type=6 support for cycling valid bits James Smart
2018-02-07 10:01 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 08/13] lpfc: Enable fw download on if_type=6 devices James Smart
2018-02-07 10:03 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 09/13] lpfc: Add embedded data pointers for enhanced performance James Smart
2018-02-07 10:17 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 10/13] lpfc: Fix nvme embedded io length on new hardware James Smart
2018-02-07 10:32 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 11/13] lpfc: Work around NVME cmd iu SGL type James Smart
2018-02-07 10:39 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 12/13] lpfc: update driver version to 12.0.0.0 James Smart
2018-02-07 10:39 ` Johannes Thumshirn
2018-02-07 2:28 ` [PATCH v2 13/13] lpfc: Update 12.0.0.0 modified files for 2018 Copyright James Smart
2018-02-07 10:50 ` Johannes Thumshirn
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=d10b5cc0-b1b6-7f36-37fb-e9e40a77ba6d@gmail.com \
--to=jsmart2021@gmail.com \
--cc=dick.kennedy@broadcom.com \
--cc=james.smart@broadcom.com \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mpe@ellerman.id.au \
/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).