From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Christoph Hellwig <hch@lst.de>,
Ulf Hansson <ulf.hansson@linaro.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Nicolas Pitre <nico@fluxnic.net>,
linux-mmc@vger.kernel.org, Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Ben Dooks <ben-linux@fluff.org>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: remove block layer bounce buffering for MMC
Date: Mon, 14 Jan 2019 17:57:55 +0100 [thread overview]
Message-ID: <20190114165755.GA7456@lst.de> (raw)
In-Reply-To: <5d09d233-8631-2a35-cbcf-ba87b0314b3a@arm.com>
On Mon, Jan 14, 2019 at 04:52:40PM +0000, Robin Murphy wrote:
> One general point for the kmap() conversions - it's not obvious (to me at
> least) whether or how that would work for a segment where sg->length >
> PAGE_SIZE. Or is there some cast-iron guarantee from the MMC mid-layer that
> it will never let the block layer generate such things in the first place?
None of this will with such segments. But yes, I guess the old case
could have worked as long as any physical contigous ranges are also
virtually contigous. So we might have to throw in a page size segment
boundary here.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Nicolas Pitre <nico@fluxnic.net>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
linux-mmc@vger.kernel.org, Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
Ben Dooks <ben-linux@fluff.org>,
linux-omap@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: remove block layer bounce buffering for MMC
Date: Mon, 14 Jan 2019 17:57:55 +0100 [thread overview]
Message-ID: <20190114165755.GA7456@lst.de> (raw)
In-Reply-To: <5d09d233-8631-2a35-cbcf-ba87b0314b3a@arm.com>
On Mon, Jan 14, 2019 at 04:52:40PM +0000, Robin Murphy wrote:
> One general point for the kmap() conversions - it's not obvious (to me at
> least) whether or how that would work for a segment where sg->length >
> PAGE_SIZE. Or is there some cast-iron guarantee from the MMC mid-layer that
> it will never let the block layer generate such things in the first place?
None of this will with such segments. But yes, I guess the old case
could have worked as long as any physical contigous ranges are also
virtually contigous. So we might have to throw in a page size segment
boundary here.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-01-14 16:57 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 9:57 remove block layer bounce buffering for MMC Christoph Hellwig
2019-01-14 9:57 ` Christoph Hellwig
2019-01-14 9:57 ` Christoph Hellwig
2019-01-14 9:57 ` [PATCH 01/11] mmc: davinci: handle highmem pages Christoph Hellwig
2019-01-14 9:57 ` Christoph Hellwig
2019-01-14 9:57 ` [PATCH 02/11] mmc: moxart: " Christoph Hellwig
2019-01-14 9:57 ` Christoph Hellwig
2019-01-14 9:57 ` [PATCH 03/11] mmc: omap: " Christoph Hellwig
2019-01-14 9:57 ` Christoph Hellwig
2019-01-14 9:57 ` [PATCH 04/11] mmc: omap: handle chained sglists Christoph Hellwig
2019-01-14 9:57 ` Christoph Hellwig
2019-01-14 9:57 ` [PATCH 05/11] mmc: s3cmci: handle highmem pages Christoph Hellwig
2019-01-14 9:57 ` Christoph Hellwig
2019-01-30 7:57 ` Ulf Hansson
2019-01-30 7:57 ` Ulf Hansson
2019-01-30 8:04 ` Christoph Hellwig
2019-01-30 8:04 ` Christoph Hellwig
2019-01-30 8:16 ` Ulf Hansson
2019-01-30 8:16 ` Ulf Hansson
2019-01-14 9:57 ` [PATCH 06/11] mmc: s3cmci: handle chained sglists Christoph Hellwig
2019-01-14 9:57 ` Christoph Hellwig
2019-01-14 9:58 ` [PATCH 07/11] mmc: mvsdio: handle highmem pages Christoph Hellwig
2019-01-14 9:58 ` Christoph Hellwig
2019-01-14 16:29 ` Nicolas Pitre
2019-01-14 16:29 ` Nicolas Pitre
2019-01-30 7:55 ` Ulf Hansson
2019-01-30 7:55 ` Ulf Hansson
2019-01-14 9:58 ` [PATCH 08/11] mmc: sh_mmcif: " Christoph Hellwig
2019-01-14 9:58 ` Christoph Hellwig
2019-01-14 9:58 ` [PATCH 09/11] mmc: sh_mmcif: handle chained sglists Christoph Hellwig
2019-01-14 9:58 ` Christoph Hellwig
2019-01-14 9:58 ` [PATCH 10/11] mmc: core: don't use block layer bounce buffers Christoph Hellwig
2019-01-14 9:58 ` Christoph Hellwig
2019-01-14 9:58 ` [PATCH 11/11] dma-mapping: remove dma_max_pfn Christoph Hellwig
2019-01-14 9:58 ` Christoph Hellwig
2019-01-14 10:26 ` remove block layer bounce buffering for MMC Ulf Hansson
2019-01-14 10:26 ` Ulf Hansson
2019-01-16 10:24 ` Arnd Bergmann
2019-01-16 10:24 ` Arnd Bergmann
2019-01-16 13:51 ` Linus Walleij
2019-01-16 13:51 ` Linus Walleij
2019-01-16 13:54 ` Arnd Bergmann
2019-01-16 13:54 ` Arnd Bergmann
2019-01-14 16:52 ` Robin Murphy
2019-01-14 16:52 ` Robin Murphy
2019-01-14 16:57 ` Christoph Hellwig [this message]
2019-01-14 16:57 ` Christoph Hellwig
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=20190114165755.GA7456@lst.de \
--to=hch@lst.de \
--cc=aaro.koskinen@iki.fi \
--cc=ben-linux@fluff.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nico@fluxnic.net \
--cc=robin.murphy@arm.com \
--cc=ulf.hansson@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.