public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: sw.prabhu6@gmail.com
Cc: James.Bottomley@HansenPartnership.com,
	martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org, mcgrof@kernel.org,
	pankaj.raghav@linux.dev, bvanassche@acm.org, dlemoal@kernel.org,
	Swarna Prabhu <s.prabhu@samsung.com>,
	Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: [PATCH 1/2] scsi: sd: enable sector size > PAGE_SIZE in scsi sd driver
Date: Sat, 28 Feb 2026 20:49:42 -0500	[thread overview]
Message-ID: <yq1ikbg1fq6.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20260219043741.276729-2-sw.prabhu6@gmail.com> (sw's message of "Wed, 18 Feb 2026 20:37:42 -0800")


> The WRITE SAME(16) and WRITE SAME(10) scsi commands uses a page from a
> dedicated mempool('sd_page_pool') for its payload. This pool was
> initialized to allocate single pages, which was sufficient as long as
> the device sector size did not exceed the PAGE_SIZE.

Applied to 7.1/scsi-staging, thanks!

-- 
Martin K. Petersen

  reply	other threads:[~2026-03-01  1:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19  4:37 [PATCH v4 0/2] enable sector size > PAGE_SIZE for scsi sw.prabhu6
2026-02-19  4:37 ` [PATCH 1/2] scsi: sd: enable sector size > PAGE_SIZE in scsi sd driver sw.prabhu6
2026-03-01  1:49   ` Martin K. Petersen [this message]
2026-02-19  4:37 ` [PATCH 2/2] scsi: scsi_debug: enable sdebug_sector_size > PAGE_SIZE sw.prabhu6
2026-02-27  8:35   ` John Garry
2026-03-02 12:27     ` Swarna Prabhu
2026-03-02 12:37       ` John Garry
2026-02-27  3:09 ` [PATCH v4 0/2] enable sector size > PAGE_SIZE for scsi Swarna Prabhu
2026-03-11  2:06 ` (subset) " Martin K. Petersen

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=yq1ikbg1fq6.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bvanassche@acm.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=pankaj.raghav@linux.dev \
    --cc=s.prabhu@samsung.com \
    --cc=sw.prabhu6@gmail.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