public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: "yohan.joung@sk.com" <yohan.joung@sk.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Avri Altman <avri.altman@wdc.com>, Bean Huo <beanhuo@micron.com>,
	Stanley Chu <stanley.chu@mediatek.com>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH v3] scsi: ufs: Increase the maximum data buffer size
Date: Thu, 4 Aug 2022 10:48:01 -0700	[thread overview]
Message-ID: <7a6499c6-4e98-072e-ce09-ddda7179b93e@acm.org> (raw)
In-Reply-To: <d8945bdf320240b2bdf6ee411eff6c8a@sk.com>

On 8/3/22 18:50, yohan.joung@sk.com wrote:
> In block layer, max_segment_size is obtained from get_max_segment_size.
> seg_boundary_mask is set to PAGE_SIZE - 1 in the ufs driver.
> The segment size is the PAGE size, and the max buffer size is
> segment size * max segment count ( PAGE SIZE * 128 ) = 512 KiB  in block layer
> Right?

Thanks for having reported this. I had overlooked that the UFS host 
controller driver sets the dma_boundary member of the host_template 
field. Is my understanding correct that UFS host controllers should 
support DMA segments that consist of multiple physical pages?

Thanks,

Bart.

  reply	other threads:[~2022-08-04 17:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 22:52 [PATCH v3] scsi: ufs: Increase the maximum data buffer size Bart Van Assche
2022-07-27  5:06 ` Avri Altman
2022-08-01 23:28 ` Martin K. Petersen
2022-08-02 23:40 ` 정요한(JOUNG YOHAN) Mobile SE
2022-08-03 16:23   ` Bart Van Assche
2022-08-04  1:50     ` 정요한(JOUNG YOHAN) Mobile SE
2022-08-04 17:48       ` Bart Van Assche [this message]
2022-08-05  1:54         ` 정요한(JOUNG YOHAN) Mobile SE
2022-09-02 14:52     ` Bean Huo
2022-09-06 18:04       ` Bart Van Assche
2022-09-15 10:56         ` Bean Huo

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=7a6499c6-4e98-072e-ce09-ddda7179b93e@acm.org \
    --to=bvanassche@acm.org \
    --cc=adrian.hunter@intel.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=jaegeuk@kernel.org \
    --cc=jejb@linux.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=matthias.bgg@gmail.com \
    --cc=stanley.chu@mediatek.com \
    --cc=yohan.joung@sk.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