linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: jaxboe@fusionio.com, jbottomley@parallels.com
Cc: linux-scsi@vger.kernel.org
Subject: Write same support v4
Date: Fri, 16 Mar 2012 14:43:12 -0400	[thread overview]
Message-ID: <1331923399-30987-1-git-send-email-martin.petersen@oracle.com> (raw)


Changes since v3:

 - Document that the REQ_NOMERGE_FLAGS is used for both bio and request
   merging.

 - Do size accounting correctly so we don't have to use
   blk_add_request_payload(). This also fixes an issue discovered by
   Mike: When running over a flaky iSCSI connection we would end up
   completing one block and subsequently fail trying to redrive the
   remainder of the I/O. An unfortunate side effect of the discrepancy
   between the DMA transfer size and the logical block range affected by
   the command.

I put a writesame4 branch on:

   git://git.kernel.org/pub/scm/linux/kernel/git/mkp/linux.git

-- 
Martin K. Petersen	Oracle Linux Engineering


             reply	other threads:[~2012-03-16 18:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 18:43 Martin K. Petersen [this message]
2012-03-16 18:43 ` [PATCH 1/7] block: Clean up discard handling logic Martin K. Petersen
2012-03-16 18:43 ` [PATCH 2/7] block: Implement support for WRITE SAME Martin K. Petersen
2012-03-16 18:43 ` [PATCH 3/7] block: Make blkdev_issue_zeroout use " Martin K. Petersen
2012-03-16 18:43 ` [PATCH 4/7] block: ioctl to zero block ranges Martin K. Petersen
2012-03-16 18:43 ` [PATCH 5/7] scsi: Add a report opcode helper Martin K. Petersen
2012-03-16 18:43 ` [PATCH 6/7] sd: Implement support for WRITE SAME Martin K. Petersen
2012-03-16 18:43 ` [PATCH 7/7] sd: Use sd_ prefix for flush and discard functions 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=1331923399-30987-1-git-send-email-martin.petersen@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=jaxboe@fusionio.com \
    --cc=jbottomley@parallels.com \
    --cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).