public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Nilesh Javali <njavali@marvell.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	"lduncan@suse.com" <lduncan@suse.com>,
	"cleech@redhat.com" <cleech@redhat.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	GR-QLogic-Storage-Upstream
	<GR-QLogic-Storage-Upstream@marvell.com>,
	"jmeneghi@redhat.com" <jmeneghi@redhat.com>
Subject: Re: [EXT] Re: [PATCH] cnic: change __GFP_COMP allocation method
Date: Wed, 20 Dec 2023 22:48:15 -0800	[thread overview]
Message-ID: <ZYPfr5G2j2VWUmfR@infradead.org> (raw)
In-Reply-To: <CO6PR18MB4500F0DCD64925A775A45F2DAF97A@CO6PR18MB4500.namprd18.prod.outlook.com>

On Tue, Dec 19, 2023 at 06:16:38AM +0000, Nilesh Javali wrote:
> If you are referring to the series proposed by Chris Leech, then this had
> objections. And that was the reason to look for an alternative method for
> coherent DMA mapping. 
> 
> [PATCH 0/3] UIO_MEM_DMA_COHERENT for cnic/bnx2/bnx2x

Yes.  Well, Greg (rightly) dislikes what the iscsi drivers have been
doing.  But we're stuck supporting them, so I see no way around that.


  reply	other threads:[~2023-12-21  6:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  5:55 [PATCH] cnic: change __GFP_COMP allocation method Nilesh Javali
2023-12-19  5:58 ` Christoph Hellwig
2023-12-19  6:16   ` [EXT] " Nilesh Javali
2023-12-21  6:48     ` Christoph Hellwig [this message]
2023-12-21 14:33       ` John Meneghini
2023-12-21 17:02         ` Greg KH

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=ZYPfr5G2j2VWUmfR@infradead.org \
    --to=hch@infradead.org \
    --cc=GR-QLogic-Storage-Upstream@marvell.com \
    --cc=cleech@redhat.com \
    --cc=jmeneghi@redhat.com \
    --cc=lduncan@suse.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=njavali@marvell.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