mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: "Philip J. Kelleher" <pjk1939@us.ibm.com>
Cc: axboe@kernel.dk, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, brking@linux.vnet.ibm.com
Subject: Re: [PATCH] block: IBM RamSan 70/80 device driver.
Date: Fri, 25 Jan 2013 15:10:47 -0500	[thread overview]
Message-ID: <x494ni5uipk.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20130125194050.GA28313@oc6784271780.ibm.com> (Philip J. Kelleher's message of "Fri, 25 Jan 2013 13:40:50 -0600")

"Philip J. Kelleher" <pjk1939@us.ibm.com> writes:

> From: Joshua H Morris <josh.h.morris@us.ibm.com>
> 	Philip J Kelleher <pjk1939@us.ibm.com>
>
> This patch includes the device driver for the IBM RamSan family
> of PCI SSD flash storage cards. This driver will inlcude support for the
> RamSan 70 and 80. The driver presents a block device for device I/O.

Hi,

Your driver does not handle REQ_FLUSH.  Does that mean that the
supported cards do not have a volatile write-back cache?

> +	blk_size = rsxx_get_logical_block_size(card);
> +
> +	blk_queue_make_request(card->queue, rsxx_make_request);
> +	blk_queue_bounce_limit(card->queue, BLK_BOUNCE_ANY);
> +	blk_queue_dma_alignment(card->queue, blk_size - 1);
> +	blk_queue_max_hw_sectors(card->queue, blkdev_max_hw_sectors);
> +	blk_queue_logical_block_size(card->queue, blk_size);
> +	blk_queue_physical_block_size(card->queue, RSXX_HW_BLK_SIZE);
> +	blk_queue_max_discard_sectors(card->queue, RSXX_HW_BLK_SIZE >> 9);

Did you mean to set max_discard_sectors inside the below for loop?
Either way, do you really only support a single hardware sector discard?

> +	queue_flag_set_unlocked(QUEUE_FLAG_NONROT, card->queue);
> +	if (rsxx_discard_supported(card)) {
> +		queue_flag_set_unlocked(QUEUE_FLAG_DISCARD, card->queue);
> +		card->queue->limits.discard_granularity = RSXX_HW_BLK_SIZE;
> +		card->queue->limits.discard_alignment   = RSXX_HW_BLK_SIZE;
> +		card->queue->limits.discard_zeroes_data = 1;
> +	}

Cheers,
Jeff

      reply	other threads:[~2013-01-25 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-25 19:40 Philip J. Kelleher
2013-01-25 20:10 ` Jeff Moyer [this message]

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=x494ni5uipk.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=brking@linux.vnet.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pjk1939@us.ibm.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

all inboxes | Powered by JetHome®