From: Christoph Hellwig <hch@infradead.org>
To: Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>
Cc: Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
Christoph Hellwig <hch@infradead.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Kashyap Desai <kashyap.desai@broadcom.com>,
Sathya Prakash <sathya.prakash@broadcom.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 4/5] mpt3sas: Handle RDPQ DMA allocation in same 4g region
Date: Thu, 19 Mar 2020 06:09:23 -0700 [thread overview]
Message-ID: <20200319130923.GA26476@infradead.org> (raw)
In-Reply-To: <CA+RiK67RquZitjQrh=yGcdunAOZaOhS90xGk3Mco2rm-ZHrEYA@mail.gmail.com>
On Wed, Mar 18, 2020 at 12:21:11PM +0530, Suganath Prabu Subramani wrote:
> Hi Christoph,
>
> We will simplify the logic as below, let us know your comments.
>
> #use one dma pool for RDPQ's, thus removes the logic of using second dma
> pool with align.
> The requirement is, RDPQ memory blocks starting & end address should have
> the same
> higher 32 bit address.
>
> 1) At driver load, set DMA Mask to 64 and allocate memory for RDPQ's.
>
> 2) Check if allocated resources are in the same 4GB range.
>
> 3) If #2 is true, continue with 64 bit DMA and go to #6
>
> 4) If #2 is false, then free all the resources from #1.
>
> 5) Set DMA mask to 32 and allocate RDPQ's.
>
> 6) Proceed with driver loading and other allocations.
Yes, please do.
next prev parent reply other threads:[~2020-03-19 13:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 10:18 [PATCH 0/5] mpt3sas: Fix changing coherent mask after allocation suganath-prabu.subramani
2020-02-11 10:18 ` [PATCH 1/5] mpt3sas: Don't change the dma coherent mask after allocations suganath-prabu.subramani
2020-02-25 18:37 ` Christoph Hellwig
2020-02-11 10:18 ` [PATCH 2/5] mpt3sas: Rename function name is_MSB_are_same suganath-prabu.subramani
2020-02-11 10:18 ` [PATCH 3/5] mpt3sas: Code Refactoring suganath-prabu.subramani
2020-02-11 10:18 ` [PATCH 4/5] mpt3sas: Handle RDPQ DMA allocation in same 4g region suganath-prabu.subramani
2020-02-25 18:42 ` Christoph Hellwig
2020-02-27 12:41 ` Sreekanth Reddy
2020-03-05 9:10 ` Sreekanth Reddy
[not found] ` <CA+RiK67RquZitjQrh=yGcdunAOZaOhS90xGk3Mco2rm-ZHrEYA@mail.gmail.com>
2020-03-18 6:53 ` Suganath Prabu Subramani
2020-03-19 13:09 ` Christoph Hellwig [this message]
2020-03-20 3:30 ` Suganath Prabu Subramani
2020-02-11 10:18 ` [PATCH 5/5] mpt3sas: Update version to 33.101.00.00 suganath-prabu.subramani
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=20200319130923.GA26476@infradead.org \
--to=hch@infradead.org \
--cc=kashyap.desai@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sathya.prakash@broadcom.com \
--cc=sreekanth.reddy@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.com \
/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