blk: reimplementation of I/O barrier
Subsystems (9)
cover blk: reimplementation of I/O barrier
Hello, Jens, James, Jeff and Bartlomiej.
This is the third posting of blk ordered reimplementation. Changes
since the scond posting are...
* Dispatch queue patchset is reordered in front of this patchset.
* Draining bug fix
* Proper requeueing of requests in an ordered sequence for TAG ordered queues.
* Fallback mechanism stripped out. This also makes -EOPNOTSUPP changes in SCSI and IDE unnecessary.
* TAG ordering request issue fix
* SCSI/libata/IDE patches splitted as requested
* Hopefully, changes to libata and IDE are more acceptable
* Documentation/block/barrier.txt added
This patchset is part of the patch series described in the following mail.
http://marc.theaimsgroup.com/?l=linux-kernel&m=112238377602033&w=2
As all previous patches don't really concern subsystems other than
block layer. They are only sent to Jens and LKML. If they're needed, preceding patches are...
fix-elevator_find:
http://marc.theaimsgroup.com/?l=linux-kernel&m=112238419731035&w=2
fix-cfq_find_next_crq:
http://marc.theaimsgroup.com/?l=linux-kernel&m=112238456712203&w=2
generic-dispatch-queue:
http://marc.theaimsgroup.com/?l=linux-kernel&m=112238633622498&w=2 http://marc.theaimsgroup.com/?l=linux-kernel&m=112238647101632&w=2 http://marc.theaimsgroup.com/?l=linux-kernel&m=112238693809889&w=2 http://marc.theaimsgroup.com/?l=linux-kernel&m=112238675926411&w=2 http://marc.theaimsgroup.com/?l=linux-kernel&m=112238660407245&w=2 http://marc.theaimsgroup.com/?l=linux-kernel&m=112238708918364&w=2
reimplement-elevator-switch:
http://marc.theaimsgroup.com/?l=linux-kernel&m=112238771305863&w=2
For general description please read barrier.txt and the previous posting.
http://marc.theaimsgroup.com/?l=linux-kernel&m=111795127124020&w=2
==== Some excerpts from barrier.txt. ====
* SCSI layer currently can't use TAG ordering even if the drive, controller and driver support it. The problem is that SCSI midlayer request dispatch function is not atomic. It releases queue lock and switch to SCSI host lock during issue and it's possible and likely to happen in time that requests change their relative positions. Once this problem is solved, TAG ordering can be enabled.
* Error handling. Currently, block layer will report error to upper layer if any of requests in an ordered sequence fails. Unfortunately, this doesn't seem to be enough. Look at the following request flow. QUEUE_ORDERED_TAG_FLUSH is in use.
[0] [1] [2] [3] [pre] [barrier] [post] < [4] [5] [6] ... > still in elevator
Let's say request [2], [3] are write requests to update file system metadata (journal or whatever) and [barrier] is used to mark that those updates are valid. Consider the following sequence.
i. Requests [0] ~ [post] leaves the request queue and enters
low-level driver.
ii. After a while, unfortunately, something goes wrong and the
drive fails [2]. Note that any of [0], [1] and [3] could have completed by this time, but [pre] couldn't have been finished as the drive must process it in order and it failed before processing that command.
iii. Error handling kicks in and determines that the error is
unrecoverable and fails [2], and resumes operation.
iv. [pre] [barrier] [post] gets processed.
v. *BOOM* power fails
The problem here is that the barrier request is *supposed* to indicate that filesystem update requests [2] and [3] made it safely to the physical medium and, if the machine crashes after the barrier is written, filesystem recovery code can depend on that. Sadly, that isn't true in this case anymore. IOW, the success of a I/O barrier should also be dependent on success of some of the preceding requests, where only upper layer (filesystem) knows what 'some' is.
This can be solved by implementing a way to tell the block layer which requests affect the success of the following barrier request and making lower lever drivers to resume operation on error only after block layer tells it to do so.
As the probability of this happening is very low and the drive should be faulty, implementing the fix is probably an overkill. But, still, it's there.
[ Start of patch descriptions ]
01_blk_add-uptodate-to-end_that_request_last.patch
: add @uptodate to end_that_request_last() and @error to rq_end_io_fn()
Add @uptodate argument to end_that_request_last() and @error to rq_end_io_fn(). There's no generic way to pass error code to request completion function, making generic error handling of non-fs request difficult (rq->errors is driver-specific and each driver uses it differently). This patch adds @uptodate to end_that_request_last() and @error to rq_end_io_fn().
For fs requests, this doesn't really matter, so just using the same uptodate argument used in the last call to end_that_request_first() should suffice. IMHO, this can also help the generic command-carrying request Jens is working on.
02_blk_implement-init_request_from_bio.patch
: separate out bio init part from __make_request
Separate out bio initialization part from __make_request. It will be used by the following blk_ordered_reimpl.
03_blk_reimplement-ordered.patch
: reimplement handling of barrier request
Reimplement handling of barrier requests.
* Flexible handling to deal with various capabilities of target devices.
* Retry support for falling back.
* Tagged queues which don't support ordered tag can do ordered.
04_blk_scsi-update-ordered.patch
: update SCSI to use new blk_ordered
All ordered request related stuff delegated to HLD. Midlayer now doens't deal with ordered setting or prepare_flush callback. sd.c updated to deal with blk_queue_ordered setting. Currently, ordered tag isn't used as SCSI midlayer cannot guarantee request ordering.
05_blk_scsi-add-fua-support.patch
: add FUA support to SCSI disk
Add FUA support to SCSI disk.
06_blk_libata-update-ordered.patch
: update libata to use new blk_ordered
Reflect changes in SCSI midlayer and updated to use new ordered request implementation
07_blk_libata-add-fua-support.patch
: add FUA support to libata
Add FUA support to libata.
08_blk_ide-update-ordered.patch
: update IDE to use new blk_ordered
Update IDE to use new blk_ordered.
09_blk_ide-add-fua-support.patch
: add FUA support to IDE
Add FUA support to IDE
10_blk_add-barrier-doc.patch
: I/O barrier documentation
I/O barrier documentation
[ End of patch descriptions ]
Thanks.
--
tejun
Re: [PATCH linux-2.6-block:master 10/10] blk: I/O barrier documentation
10_blk_add-barrier-doc.patch
I/O barrier documentation
barrier.txt | 271 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ biodoc.txt | 10 -- 2 files changed, 273 insertions(+), 8 deletions(-)
Documentation/block/barrier.txt new file +271 -0
@@ -0,0 +1,271 @@ +I/O Barriers +============ +Tejun Heo <[email protected]>, July 22 2005 + +I/O barrier requests are used to guarantee ordering around the barrier +requests. Unless you're crazy enough to use disk drives for +implementing synchronization constructs (wow, sounds interesting...), +the ordering is meaningful only for write requests for things like +journal checkpoints. All requests queued before a barrier request +must be finished (made it to the physical medium) before the barrier +request is started, and all requests queued after the barrier request +must be started only after the barrier request is finished (again, +made it to the physical medium). + +In other words, I/O barrier requests have the following two properties. + +1. Request ordering + +Requests cannot pass the barrier request. Preceding requests are +processed before the barrier and following requests after. + +Depending on what features a drive supports, this can be done in one +of the following three ways. + +i. For devices which have queue depth greater than 1 (TCQ devices) and +support ordered tags, block layer can just issue the barrier as an +ordered request and the lower level driver, controller and drive +itself are responsible for making sure that the ordering contraint is +met. Most modern SCSI controllers/drives should support this. + +NOTE: SCSI ordered tag isn't currently used due to limitation in the + SCSI midlayer, see the following random notes section. + +ii. For devices which have queue depth greater than 1 but don't +support ordered tags, block layer ensures that the requests preceding +a barrier request finishes before issuing the barrier request. Also, +it defers requests following the barrier until the barrier request is +finished. Older SCSI controllers/drives and SATA drives fall in this +category. + +iii. Devices which have queue depth of 1. This is a degenerate case +of ii. Just keeping issue order suffices. Ancient SCSI +controllers/drives and IDE drives are in this category. + +2. Forced flushing to physcial medium + +Again, if you're not gonna do synchronization with disk drives (dang, +it sounds even more appealing now!), the reason you use I/O barriers +is mainly to protect filesystem integrity when power failure or some +other events abruptly stop the drive from operating and possibly make +the drive lose data in its cache. So, I/O barriers need to guarantee +that requests actually get written to non-volatile medium in order. + +There are four cases, + +i. No write-back cache. Keeping requests ordered is enough. + +ii. Write-back cache but no flush operation. There's no way to +gurantee physical-medium commit order. This kind of devices can't to +I/O barriers. + +iii. Write-back cache and flush operation but no FUA (forced unit +access). We need two cache flushes - before and after the barrier +request. + +iv. Write-back cache, flush operation and FUA. We still need one +flush to make sure requests preceding a barrier are written to medium, +but post-barrier flush can be avoided by using FUA write on the +barrier itself. + + +How to support barrier requests in drivers +------------------------------------------ + +All barrier handling is done inside block layer proper. All low level +drivers have to are implementing its prepare_flush_fn and using one +the following two functions to indicate what barrier type it supports +and how to prepare flush requests. Note that the term 'ordered' is +used to indicate the whole sequence of performing barrier requests +including draining and flushing. + +typedef void (prepare_flush_fn)(request_queue_t *q, struct request *rq); + +int blk_queue_ordered(request_queue_t *q, unsigned ordered, + prepare_flush_fn *prepare_flush_fn, + unsigned gfp_mask); + +int blk_queue_ordered_locked(request_queue_t *q, unsigned ordered, + prepare_flush_fn *prepare_flush_fn, + unsigned gfp_mask); + +The only difference between the two functions is whether or not the +caller is holding q->queue_lock on entry. The latter expects the +caller is holding the lock. + +@q : the queue in question +@ordered : the ordered mode the driver/device supports +@prepare_flush_fn : this function should prepare @rq such that it + flushes cache to physical medium when executed +@gfp_mask : gfp_mask used when allocating data structures + for ordered processing + +For example, SCSI disk driver's prepare_flush_fn looks like the +following. + +static void sd_prepare_flush(request_queue_t *q, struct request *rq) +{ + memset(rq->cmd, 0, sizeof(rq->cmd)); + rq->flags |= REQ_BLOCK_PC; + rq->timeout = SD_TIMEOUT; + rq->cmd[0] = SYNCHRONIZE_CACHE; +} + +The following seven ordered modes are supported. The following table +shows which mode should be used depending on what features a +device/driver supports. In the leftmost column of table, +QUEUE_ORDERED_ prefix is omitted from the mode names to save space. + +The table is followed by description of each mode. Note that in the +descriptions of QUEUE_ORDERED_DRAIN*, '=>' is used whereas '->' is +used for QUEUE_ORDERED_TAG* descriptions. '=>' indicates that the +preceding step must be complete before proceeding to the next step. +'->' indicates that the next step can start as soon as the previous +step is issued. + + write-back cache ordered tag flush FUA +----------------------------------------------------------------------- +NONE yes/no N/A no N/A +DRAIN no no N/A N/A +DRAIN_FLUSH yes no yes no +DRAIN_FUA yes no yes yes +TAG no yes N/A N/A +TAG_FLUSH yes yes yes no +TAG_FUA yes yes yes yes + + +QUEUE_ORDERED_NONE + I/O barriers are not needed and/or supported. + + Sequence: N/A + +QUEUE_ORDERED_DRAIN + Requests are ordered by draining the request queue and cache + flushing isn't needed. + + Sequence: drain => barrier + +QUEUE_ORDERED_DRAIN_FLUSH + Requests are ordered by draining the request queue and both + pre-barrier and post-barrier cache flushings are needed. + + Sequence: drain => preflush => barrier => postflush + +QUEUE_ORDERED_DRAIN_FUA + Requests are ordered by draining the request queue and + pre-barrier cache flushing is needed. By using FUA on barrier + request, post-barrier flushing can be skipped. + + Sequence: drain => preflush => barrier + +QUEUE_ORDERED_TAG + Requests are ordered by ordered tag and cache flushing isn't + needed. + + Sequence: barrier + +QUEUE_ORDERED_TAG_FLUSH + Requests are ordered by ordered tag and both pre-barrier and + post-barrier cache flushings are needed. + + Sequence: preflush -> barrier -> postflush + +QUEUE_ORDERED_TAG_FUA + Requests are ordered by ordered tag and pre-barrier cache + flushing is needed. By using FUA on barrier request, + post-barrier flushing can be skipped. + + Sequence: preflush -> barrier + + +Random notes/caveats +-------------------- + +* SCSI layer currently can't use TAG ordering even if the drive, +controller and driver support it. The problem is that SCSI midlayer +request dispatch function is not atomic. It releases queue lock and +switch to SCSI host lock during issue and it's possible and likely to +happen in time that requests change their relative positions. Once +this problem is solved, TAG ordering can be enabled. + +* Currently, no matter which ordered mode is used, there can be only +one barrier request in progress. All I/O barriers are held off by +block layer until the previous I/O barrier is complete. This doesn't +make any difference for DRAIN ordered devices, but, for TAG ordered +devices with very high command latency, passing multiple I/O barriers +to low level *might* be helpful if they are very frequent. Well, this +certainly is a non-issue. I'm writing this just to make clear that no +two I/O barrier is ever passed to low-level driver. + +* Completion order. Requests in ordered sequence are issued in order +but not required to finish in order. Barrier implementation can +handle out-of-order completion of ordered sequence. IOW, the requests +MUST be processed in order but the hardware/software completion paths +are allowed to reorder completion notifications - eg. current SCSI +midlayer doesn't preserve completion order during error handling. + +* Requeueing order. Low-level drivers are free to requeue any request +after they removed it from the request queue with +blkdev_dequeue_request(). As barrier sequence should be kept in order +when requeued, generic elevator code takes care of putting requests in +order around barrier. See blk_ordered_req_seq() and +ELEVATOR_INSERT_REQUEUE handling in __elv_add_request() for details. + +Note that block drivers must not requeue preceding requests while +completing latter requests in an ordered sequence. Currently, no +error checking is done against this. + +* Error handling. Currently, block layer will report error to upper +layer if any of requests in an ordered sequence fails. Unfortunately, +this doesn't seem to be enough. Look at the following request flow. +QUEUE_ORDERED_TAG_FLUSH is in use. + + [0] [1] [2] [3] [pre] [barrier] [post] < [4] [5] [6] ... > + still in elevator + +Let's say request [2], [3] are write requests to update file system +metadata (journal or whatever) and [barrier] is used to mark that +those updates are valid. Consider the following sequence. + + i. Requests [0] ~ [post] leaves the request queue and enters + low-level driver. + ii. After a while, unfortunately, something goes wrong and the + drive fails [2]. Note that any of [0], [1] and [3] could have + completed by this time, but [pre] couldn't have been finished + as the drive must process it in order and it failed before + processing that command. + iii. Error handling kicks in and determines that the error is + unrecoverable and fails [2], and resumes operation. + iv. [pre] [barrier] [post] gets processed. + v. *BOOM* power fails + +The problem here is that the barrier request is *supposed* to indicate +that filesystem update requests [2] and [3] made it safely to the +physical medium and, if the machine crashes after the barrier is +written, filesystem recovery code can depend on that. Sadly, that +isn't true in this case anymore. IOW, the success of a I/O barrier +should also be dependent on success of some of the preceding requests, +where only upper layer (filesystem) knows what 'some' is. + +This can be solved by implementing a way to tell the block layer which +requests affect the success of the following barrier request and +making lower lever drivers to resume operation on error only after +block layer tells it to do so. + +As the probability of this happening is very low and the drive should +be faulty, implementing the fix is probably an overkill. But, still, +it's there. + +* In previous drafts of barrier implementation, there was fallback +mechanism such that, if FUA or ordered TAG fails, less fancy ordered +mode can be selected and the failed barrier request is retried +automatically. The rationale for this feature was that as FUA is +pretty new in ATA world and ordered tag was never used widely, there +could be devices which report to support those features but choke when +actually given such requests. + + This was removed for two reasons 1. it's an overkill 2. it's +impossible to implement properly when TAG ordering is used as low +level drivers resume after an error automatically. If it's ever +needed adding it back and modifying low level drivers accordingly +shouldn't be difficult.
Documentation/block/biodoc.txt +2 -8
@@ -263,14 +263,8 @@ A flag in the bio structure, BIO_BARRIER The generic i/o scheduler would make sure that it places the barrier request and all other requests coming after it after all the previous requests in the queue. Barriers may be implemented in different ways depending on the -driver. A SCSI driver for example could make use of ordered tags to -preserve the necessary ordering with a lower impact on throughput. For IDE -this might be two sync cache flush: a pre and post flush when encountering -a barrier write. - -There is a provision for queues to indicate what kind of barriers they -can provide. This is as of yet unmerged, details will be added here once it -is in the kernel. +driver. For more details regarding I/O barriers, please read barrier.txt +in this directory. 1.2.2 Request Priority/Latency
Re: [PATCH linux-2.6-block:master 02/10] blk: separate out bio init part from __make_request
In reply to Tejun Heo02_blk_implement-init_request_from_bio.patch
Separate out bio initialization part from __make_request. It will be used by the following blk_ordered_reimpl.
ll_rw_blk.c | 59 ++++++++++++++++++++++++++++++++--------------------------- 1 files changed, 32 insertions(+), 27 deletions(-)
drivers/block/ll_rw_blk.c +32 -27
@@ -36,6 +36,8 @@static void blk_unplug_work (void *data);static void blk_unplug_timeout (unsigned long data); +static void init_request_from_bio (struct request *req,struct bio *bio); +static int __make_request (request_queue_t *q,struct bio *bio);/* * For the allocated request tables
@@ -1655,8 +1657,6 @@ static int blk_init_free_list(request_qureturn 0 ; } -static int __make_request (request_queue_t *,struct bio *); -request_queue_t *blk_alloc_queue (int gfp_mask) {request_queue_t *q =kmem_cache_alloc (requestq_cachep, gfp_mask);
@@ -2555,6 +2555,35 @@ void blk_attempt_remerge(request_queue_tEXPORT_SYMBOL (blk_attempt_remerge); +static void init_request_from_bio (struct request *req,struct bio *bio) +{ + req->flags |=REQ_CMD ; + +/* +* inherit FAILFAST from bio (for read-ahead, and explicit FAILFAST) +*/ +if (bio_rw_ahead (bio) ||bio_failfast (bio)) + req->flags |=REQ_FAILFAST ; + +/* +* REQ_BARRIER implies no merging, but lets make it explicit +*/ +if (unlikely (bio_barrier (bio))) + req->flags |= (REQ_HARDBARRIER |REQ_NOMERGE ); + + req->errors =0 ; + req->hard_sector = req->sector = bio->bi_sector; + req->hard_nr_sectors = req->nr_sectors =bio_sectors (bio); + req->current_nr_sectors = req->hard_cur_sectors =bio_cur_sectors (bio); + req->nr_phys_segments =bio_phys_segments (req->q, bio); + req->nr_hw_segments =bio_hw_segments (req->q, bio); + req->buffer =bio_data (bio);/* see ->buffer comment above */ + req->waiting =NULL ; + req->bio = req->biotail = bio; + req->rq_disk = bio->bi_bdev->bd_disk; + req->start_time = jiffies; +} +/* * Non-locking blk_attempt_remerge variant. */
@@ -2678,31 +2707,7 @@ get_rq: goto again; } - req->flags |=REQ_CMD ; - -/* -* inherit FAILFAST from bio (for read-ahead, and explicit FAILFAST) -*/ -if (bio_rw_ahead (bio) ||bio_failfast (bio)) - req->flags |=REQ_FAILFAST ; - -/* -* REQ_BARRIER implies no merging, but lets make it explicit -*/ -if (barrier) - req->flags |= (REQ_HARDBARRIER |REQ_NOMERGE ); - - req->errors =0 ; - req->hard_sector = req->sector = sector; - req->hard_nr_sectors = req->nr_sectors = nr_sectors; - req->current_nr_sectors = req->hard_cur_sectors = cur_nr_sectors; - req->nr_phys_segments =bio_phys_segments (q, bio); - req->nr_hw_segments =bio_hw_segments (q, bio); - req->buffer =bio_data (bio);/* see ->buffer comment above */ - req->waiting =NULL ; - req->bio = req->biotail = bio; - req->rq_disk = bio->bi_bdev->bd_disk; - req->start_time = jiffies; +init_request_from_bio (req, bio);add_request (q, req); out:
Re: [PATCH linux-2.6-block:master 01/10] blk: add @uptodate to end_that_request_last() and @error to rq_end_io_fn()
In reply to Tejun Heo01_blk_add-uptodate-to-end_that_request_last.patch
Add @uptodate argument to end_that_request_last() and @error to rq_end_io_fn(). There's no generic way to pass error code to request completion function, making generic error handling of non-fs request difficult (rq->errors is driver-specific and each driver uses it differently). This patch adds @uptodate to end_that_request_last() and @error to rq_end_io_fn().
For fs requests, this doesn't really matter, so just using the same uptodate argument used in the last call to end_that_request_first() should suffice. IMHO, this can also help the generic command-carrying request Jens is working on.
drivers/block/DAC960.c | 2 +- drivers/block/cciss.c | 2 +- drivers/block/cpqarray.c | 2 +- drivers/block/elevator.c | 2 +- drivers/block/floppy.c | 2 +- drivers/block/ll_rw_blk.c | 20 ++++++++++++++------ drivers/block/nbd.c | 2 +- drivers/block/sx8.c | 2 +- drivers/block/ub.c | 2 +- drivers/block/viodasd.c | 2 +- drivers/cdrom/cdu31a.c | 2 +- drivers/ide/ide-cd.c | 4 ++-- drivers/ide/ide-io.c | 6 +++--- drivers/message/i2o/i2o_block.c | 6 +++--- drivers/mmc/mmc_block.c | 4 ++-- drivers/s390/block/dasd.c | 2 +- drivers/s390/char/tape_block.c | 2 +- drivers/scsi/ide-scsi.c | 4 ++-- drivers/scsi/scsi_lib.c | 8 ++++---- drivers/scsi/sd.c | 2 +- include/linux/blkdev.h | 6 +++--- 21 files changed, 46 insertions(+), 38 deletions(-)
drivers/block/DAC960.c +1 -1
@@ -3480,7 +3480,7 @@ static inline boolean DAC960_ProcessCompif (!end_that_request_first (Request, UpToDate, Command->BlockCount)) { -end_that_request_last (Request); +end_that_request_last (Request, UpToDate);if (Command->Completion) {complete (Command->Completion);
drivers/block/cciss.c +1 -1
@@ -2071,7 +2071,7 @@ static inline void complete_command( ctlprintk ("Done with %p\n" , cmd->rq);#endif /* CCISS_DEBUG */ -end_that_request_last (cmd->rq); +end_that_request_last (cmd->rq, status ?1 : -EIO );cmd_free (h,cmd,1 ); }
drivers/block/cpqarray.c +1 -1
@@ -1036,7 +1036,7 @@ static inline void complete_command(cmdlcomplete_buffers (cmd->rq->bio, ok); DBGPX(printk("Done with %p\n", cmd->rq);); -end_that_request_last (cmd->rq); +end_that_request_last (cmd->rq, ok ?1 : -EIO ); }/*
drivers/block/elevator.c +1 -1
@@ -502,7 +502,7 @@ struct request *elv_next_request(requestblkdev_dequeue_request (rq); rq->flags |=REQ_QUIET ;end_that_request_chunk (rq,0 , nr_bytes); -end_that_request_last (rq); +end_that_request_last (rq,0 ); }else {printk (KERN_ERR "%s: bad return=%d\n" , __FUNCTION__, ret);
drivers/block/floppy.c +1 -1
@@ -2299,7 +2299,7 @@ static void floppy_end_request(struct readd_disk_randomness (req->rq_disk);floppy_off ((long )req->rq_disk->private_data);blkdev_dequeue_request (req); -end_that_request_last (req); +end_that_request_last (req, uptodate);/* We're done with the request */ current_req =NULL ;
drivers/block/ll_rw_blk.c +14 -6
@@ -342,7 +342,7 @@ EXPORT_SYMBOL(blk_queue_issue_flush_fn);/* * Cache flushing for ordered writes handling */ -static void blk_pre_flush_end_io (struct request *flush_rq) +static void blk_pre_flush_end_io (struct request *flush_rq,int error) {struct request *rq = flush_rq->end_io_data;request_queue_t *q = rq->q;
@@ -360,7 +360,7 @@ static void blk_pre_flush_end_io(struct } } -static void blk_post_flush_end_io (struct request *flush_rq) +static void blk_post_flush_end_io (struct request *flush_rq,int error) {struct request *rq = flush_rq->end_io_data;request_queue_t *q = rq->q;
@@ -2419,7 +2419,7 @@ EXPORT_SYMBOL(blk_put_request);* blk_end_sync_rq - executes a completion event on a request * @rq: request to complete */ -void blk_end_sync_rq (struct request *rq) +void blk_end_sync_rq (struct request *rq,int error) {struct completion *waiting = rq->waiting;
@@ -3104,9 +3104,17 @@ EXPORT_SYMBOL(end_that_request_chunk);/* * queue lock must be held */ -void end_that_request_last (struct request *req) +void end_that_request_last (struct request *req,int uptodate) {struct gendisk *disk = req->rq_disk; +int error; + +/* +* extend uptodate bool to allow < 0 value to be direct io error +*/ + error =0 ; +if (end_io_error (uptodate)) + error = !uptodate ? -EIO : uptodate;if (unlikely (laptop_mode) &&blk_fs_request (req))laptop_io_completion ();
@@ -3127,7 +3135,7 @@ void end_that_request_last(struct reques disk->in_flight--; }if (req->end_io) - req->end_io (req); + req->end_io (req, error);else __blk_put_request (req->q, req); }
@@ -3139,7 +3147,7 @@ void end_request(struct request *req, inif (!end_that_request_first (req, uptodate, req->hard_cur_sectors)) {add_disk_randomness (req->rq_disk);blkdev_dequeue_request (req); -end_that_request_last (req); +end_that_request_last (req, uptodate); } }
drivers/block/nbd.c +1 -1
@@ -136,7 +136,7 @@ static void nbd_end_request(struct requespin_lock_irqsave (q->queue_lock, flags);if (!end_that_request_first (req, uptodate, req->nr_sectors)) { -end_that_request_last (req); +end_that_request_last (req, uptodate); }spin_unlock_irqrestore (q->queue_lock, flags); }
drivers/block/sx8.c +1 -1
@@ -746,7 +746,7 @@ static inline void carm_end_request_queu rc =end_that_request_first (req, uptodate, req->hard_nr_sectors);assert (rc ==0 ); -end_that_request_last (req); +end_that_request_last (req, uptodate); rc =carm_put_request (host, crq);assert (rc ==0 );
drivers/block/ub.c +1 -1
@@ -875,7 +875,7 @@ static void ub_end_rq(struct request *rq rc =end_that_request_first (rq, uptodate, rq->hard_nr_sectors);// assert(rc == 0); -end_that_request_last (rq); +end_that_request_last (rq, uptodate); }/*
drivers/block/viodasd.c +1 -1
@@ -305,7 +305,7 @@ static void viodasd_end_request(struct rif (end_that_request_first (req, uptodate, num_sectors))return ;add_disk_randomness (req->rq_disk); -end_that_request_last (req); +end_that_request_last (req, uptodate); }/*
drivers/cdrom/cdu31a.c +1 -1
@@ -1402,7 +1402,7 @@ static void do_cdu31a_request(request_quif (!end_that_request_first (req,1 , nblock)) {spin_lock_irq (q->queue_lock);blkdev_dequeue_request (req); -end_that_request_last (req); +end_that_request_last (req,1 );spin_unlock_irq (q->queue_lock); }continue ;
drivers/ide/ide-cd.c +2 -2
@@ -616,7 +616,7 @@ static void cdrom_end_request (ide_drive*/ spin_lock_irqsave (&ide_lock, flags);end_that_request_chunk (failed,0 , failed->data_len); -end_that_request_last (failed); +end_that_request_last (failed,0 );spin_unlock_irqrestore (&ide_lock, flags); }
@@ -1741,7 +1741,7 @@ end_request:spin_lock_irqsave (&ide_lock, flags);blkdev_dequeue_request (rq); -end_that_request_last (rq); +end_that_request_last (rq,1 );HWGROUP (drive)->rq =NULL ;spin_unlock_irqrestore (&ide_lock, flags);return ide_stopped;
drivers/ide/ide-io.c +3 -3
@@ -89,7 +89,7 @@ int __ide_end_request(ide_drive_t *driveblkdev_dequeue_request (rq);HWGROUP (drive)->rq =NULL ; -end_that_request_last (rq); +end_that_request_last (rq, uptodate); ret =0 ; }return ret;
@@ -247,7 +247,7 @@ static void ide_complete_pm_request (ide }blkdev_dequeue_request (rq);HWGROUP (drive)->rq =NULL ; -end_that_request_last (rq); +end_that_request_last (rq,1 );spin_unlock_irqrestore (&ide_lock, flags); }
@@ -379,7 +379,7 @@ void ide_end_drive_cmd (ide_drive_t *driblkdev_dequeue_request (rq);HWGROUP (drive)->rq =NULL ; rq->errors = err; -end_that_request_last (rq); +end_that_request_last (rq, !rq->errors);spin_unlock_irqrestore (&ide_lock, flags); }
drivers/message/i2o/i2o_block.c +3 -3
@@ -452,7 +452,7 @@ static int i2o_block_reply(struct i2o_cowhile (end_that_request_chunk (req, !req->errors,le32_to_cpu (pmsg->body[1 ]))) ; -end_that_request_last (req); +end_that_request_last (req, !req->errors); dev->open_queue_depth--;list_del (&ireq->queue);
@@ -489,7 +489,7 @@ static int i2o_block_reply(struct i2o_cospin_lock_irqsave (q->queue_lock, flags);while (end_that_request_chunk (req, !req->errors,le32_to_cpu (msg->body[1 ]))) ; -end_that_request_last (req); +end_that_request_last (req, !req->errors); dev->open_queue_depth--;list_del (&ireq->queue);
@@ -554,7 +554,7 @@ static int i2o_block_reply(struct i2o_coadd_disk_randomness (req->rq_disk);spin_lock_irqsave (q->queue_lock, flags); -end_that_request_last (req); +end_that_request_last (req, !req->errors); dev->open_queue_depth--;list_del (&ireq->queue);
drivers/mmc/mmc_block.c +2 -2
@@ -254,7 +254,7 @@ static int mmc_blk_issue_rq(struct mmc_q*/ add_disk_randomness (req->rq_disk);blkdev_dequeue_request (req); -end_that_request_last (req); +end_that_request_last (req,1 ); }spin_unlock_irq (&md->lock); }while (ret);
@@ -280,7 +280,7 @@ static int mmc_blk_issue_rq(struct mmc_qadd_disk_randomness (req->rq_disk);blkdev_dequeue_request (req); -end_that_request_last (req); +end_that_request_last (req,0 );spin_unlock_irq (&md->lock);return 0 ;
drivers/s390/block/dasd.c +1 -1
@@ -1039,7 +1039,7 @@ dasd_end_request(struct request *req, inif (end_that_request_first (req, uptodate, req->hard_nr_sectors))BUG ();add_disk_randomness (req->rq_disk); -end_that_request_last (req); +end_that_request_last (req, uptodate); }/*
drivers/s390/char/tape_block.c +1 -1
@@ -78,7 +78,7 @@ tapeblock_end_request(struct request *re {if (end_that_request_first (req, uptodate, req->hard_nr_sectors))BUG (); -end_that_request_last (req); +end_that_request_last (req, uptodate); } static void
drivers/scsi/ide-scsi.c +2 -2
@@ -1039,7 +1039,7 @@ static int idescsi_eh_reset (struct scsi/* kill current request */ blkdev_dequeue_request (req); -end_that_request_last (req); +end_that_request_last (req,0 );if (req->flags &REQ_SENSE )kfree (scsi->pc->buffer);kfree (scsi->pc);
@@ -1049,7 +1049,7 @@ static int idescsi_eh_reset (struct scsi/* now nuke the drive queue */ while ((req =elv_next_request (drive->queue))) {blkdev_dequeue_request (req); -end_that_request_last (req); +end_that_request_last (req,0 ); }HWGROUP (drive)->rq =NULL ;
drivers/scsi/scsi_lib.c +4 -4
@@ -258,7 +258,7 @@ static void scsi_wait_done(struct scsi_c/* This is the end routine we get to if a command was never attached * to the request. Simply complete the request without changing * rq_status; this will cause a DRIVER_ERROR. */ -static void scsi_wait_req_end_io (struct request *req) +static void scsi_wait_req_end_io (struct request *req,int error) {BUG_ON (!req->waiting);
@@ -574,7 +574,7 @@ static struct scsi_cmnd *scsi_end_requesspin_lock_irqsave (q->queue_lock, flags);if (blk_rq_tagged (req))blk_queue_end_tag (q, req); -end_that_request_last (req); +end_that_request_last (req, uptodate);spin_unlock_irqrestore (q->queue_lock, flags);/*
@@ -1259,7 +1259,7 @@ static void scsi_kill_requests(request_q req->flags |=REQ_QUIET ;while (end_that_request_first (req,0 , req->nr_sectors)) ; -end_that_request_last (req); +end_that_request_last (req,0 ); } }
@@ -1314,7 +1314,7 @@ static void scsi_request_fn(struct reque req->flags |=REQ_QUIET ;while (end_that_request_first (req,0 , req->nr_sectors)) ; -end_that_request_last (req); +end_that_request_last (req,0 );continue ; }
drivers/scsi/sd.c +1 -1
@@ -758,7 +758,7 @@ static void sd_end_flush(request_queue_t* force journal abort of barriers */ end_that_request_first (rq, -EOPNOTSUPP , rq->hard_nr_sectors); -end_that_request_last (rq); +end_that_request_last (rq, -EOPNOTSUPP ); } }
include/linux/blkdev.h +3 -3
@@ -94,7 +94,7 @@ void copy_io_context(struct io_context *void swap_io_context (struct io_context **ioc1,struct io_context **ioc2);struct request ; -typedef void (rq_end_io_fn )(struct request *); +typedef void (rq_end_io_fn )(struct request *,int );struct request_list {int count[2 ];
@@ -550,7 +550,7 @@ extern void blk_unregister_queue(structextern void register_disk (struct gendisk *dev);extern void generic_make_request (struct bio *bio);extern void blk_put_request (struct request *); -extern void blk_end_sync_rq (struct request *rq); +extern void blk_end_sync_rq (struct request *rq,int error);extern void blk_attempt_remerge (request_queue_t *,struct request *);extern void __blk_attempt_remerge (request_queue_t *,struct request *);extern struct request *blk_get_request (request_queue_t *,int ,int );
@@ -601,7 +601,7 @@ static inline void blk_run_address_space*/ extern int end_that_request_first (struct request *,int ,int );extern int end_that_request_chunk (struct request *,int ,int ); -extern void end_that_request_last (struct request *); +extern void end_that_request_last (struct request *,int );extern void end_request (struct request *req,int uptodate);/*
Re: [PATCH linux-2.6-block:master 05/10] blk: add FUA support to SCSI disk
In reply to Tejun Heo05_blk_scsi-add-fua-support.patch
Add FUA support to SCSI disk.
sd.c | 29 ++++++++++++++++++++++++++--- 1 files changed, 26 insertions(+), 3 deletions(-)
drivers/scsi/sd.c +26 -3
@@ -103,6 +103,7 @@ struct scsi_disk {u8 write_prot; unsigned WCE : 1; /* state of disk WCE bit */ unsigned RCD : 1; /* state of disk RCD bit, unused */ + unsigned DPOFUA : 1; /* state of disk DPOFUA bit */ };static DEFINE_IDR (sd_index_idr);
@@ -343,6 +344,7 @@ static int sd_init_command(struct scsi_cif (block >0xffffffff ) { SCpnt->cmnd[0 ] +=READ_16 -READ_6 ; + SCpnt->cmnd[1 ] |=blk_fua_rq (rq) ?0x8 :0 ; SCpnt->cmnd[2 ] =sizeof (block) >4 ? (unsigned char ) (block >>56 ) &0xff :0 ; SCpnt->cmnd[3 ] =sizeof (block) >4 ? (unsigned char ) (block >>48 ) &0xff :0 ; SCpnt->cmnd[4 ] =sizeof (block) >4 ? (unsigned char ) (block >>40 ) &0xff :0 ;
@@ -362,6 +364,7 @@ static int sd_init_command(struct scsi_c this_count =0xffff ; SCpnt->cmnd[0 ] +=READ_10 -READ_6 ; + SCpnt->cmnd[1 ] |=blk_fua_rq (rq) ?0x8 :0 ; SCpnt->cmnd[2 ] = (unsigned char ) (block >>24 ) &0xff ; SCpnt->cmnd[3 ] = (unsigned char ) (block >>16 ) &0xff ; SCpnt->cmnd[4 ] = (unsigned char ) (block >>8 ) &0xff ;
@@ -370,6 +373,17 @@ static int sd_init_command(struct scsi_c SCpnt->cmnd[7 ] = (unsigned char ) (this_count >>8 ) &0xff ; SCpnt->cmnd[8 ] = (unsigned char ) this_count &0xff ; }else { +if (unlikely (blk_fua_rq (rq))) { +/* +* This happens only if this drive failed +* 10byte rw command with ILLEGAL_REQUEST +* during operation and thus turned off +* use_10_for_rw. +*/ +printk (KERN_ERR "sd: FUA write on READ/WRITE(6) drive\n" ); +return 0 ; + } +if (this_count >0xff ) this_count =0xff ;
@@ -1399,10 +1413,18 @@ sd_read_cache_type(struct scsi_disk *sdk sdkp->RCD =0 ; } + sdkp->DPOFUA = (data.device_specific &0x10 ) !=0 ; +if (sdkp->DPOFUA && !sdkp->device->use_10_for_rw) { +printk (KERN_NOTICE "SCSI device %s: uses " +"READ/WRITE(6), disabling FUA\n" , diskname); + sdkp->DPOFUA =0 ; + } + ct = sdkp->RCD +2 *sdkp->WCE; -printk (KERN_NOTICE "SCSI device %s: drive cache: %s\n" , - diskname, types[ct]); +printk (KERN_NOTICE "SCSI device %s: drive cache: %s%s\n" , + diskname, types[ct], + sdkp->DPOFUA ?" w/ FUA" :"" );return ; }
@@ -1489,7 +1511,8 @@ static int sd_revalidate_disk(struct gen* QUEUE_ORDERED_TAG_* even when ordered tag is supported. */ if (sdkp->WCE) - ordered =QUEUE_ORDERED_DRAIN_FLUSH ; + ordered = sdkp->DPOFUA + ?QUEUE_ORDERED_DRAIN_FUA :QUEUE_ORDERED_DRAIN_FLUSH ;else ordered =QUEUE_ORDERED_DRAIN ;
Re: [PATCH linux-2.6-block:master 05/10] blk: add FUA support to SCSI disk
Quoted 3 lines · Tejun Heo
05_blk_scsi-add-fua-support.patch
Add FUA support to SCSI disk.
ACK
Re: [PATCH linux-2.6-block:master 06/10] blk: update libata to use new blk_ordered
In reply to Tejun Heo06_blk_libata-update-ordered.patch
Reflect changes in SCSI midlayer and updated to use new ordered request implementation
ahci.c | 1 - ata_piix.c | 1 - sata_nv.c | 1 - sata_promise.c | 1 - sata_sil.c | 1 - sata_sis.c | 1 - sata_svw.c | 1 - sata_sx4.c | 1 - sata_uli.c | 1 - sata_via.c | 1 - sata_vsc.c | 1 - 11 files changed, 11 deletions(-)
drivers/scsi/ahci.c +0 -1
@@ -206,7 +206,6 @@ static Scsi_Host_Template ahci_sht = { .dma_boundary = AHCI_DMA_BOUNDARY, .slave_configure = ata_scsi_slave_config, .bios_param = ata_std_bios_param, - .ordered_flush = 1, };static struct ata_port_operations ahci_ops = {
drivers/scsi/ata_piix.c +0 -1
@@ -123,7 +123,6 @@ static Scsi_Host_Template piix_sht = { .dma_boundary = ATA_DMA_BOUNDARY, .slave_configure = ata_scsi_slave_config, .bios_param = ata_std_bios_param, - .ordered_flush = 1, };static struct ata_port_operations piix_pata_ops = {
drivers/scsi/sata_nv.c +0 -1
@@ -206,7 +206,6 @@ static Scsi_Host_Template nv_sht = { .dma_boundary = ATA_DMA_BOUNDARY, .slave_configure = ata_scsi_slave_config, .bios_param = ata_std_bios_param, - .ordered_flush = 1, };static struct ata_port_operations nv_ops = {
drivers/scsi/sata_promise.c +0 -1
@@ -103,7 +103,6 @@ static Scsi_Host_Template pdc_ata_sht = .dma_boundary = ATA_DMA_BOUNDARY, .slave_configure = ata_scsi_slave_config, .bios_param = ata_std_bios_param, - .ordered_flush = 1, };static struct ata_port_operations pdc_ata_ops = {
drivers/scsi/sata_sil.c +0 -1
@@ -135,7 +135,6 @@ static Scsi_Host_Template sil_sht = { .dma_boundary = ATA_DMA_BOUNDARY, .slave_configure = ata_scsi_slave_config, .bios_param = ata_std_bios_param, - .ordered_flush = 1, };static struct ata_port_operations sil_ops = {
drivers/scsi/sata_sis.c +0 -1
@@ -90,7 +90,6 @@ static Scsi_Host_Template sis_sht = { .dma_boundary = ATA_DMA_BOUNDARY, .slave_configure = ata_scsi_slave_config, .bios_param = ata_std_bios_param, - .ordered_flush = 1, };static struct ata_port_operations sis_ops = {
drivers/scsi/sata_svw.c +0 -1
@@ -288,7 +288,6 @@ static Scsi_Host_Template k2_sata_sht = .proc_info = k2_sata_proc_info, #endif .bios_param = ata_std_bios_param, - .ordered_flush = 1, };
drivers/scsi/sata_sx4.c +0 -1
@@ -188,7 +188,6 @@ static Scsi_Host_Template pdc_sata_sht = .dma_boundary = ATA_DMA_BOUNDARY, .slave_configure = ata_scsi_slave_config, .bios_param = ata_std_bios_param, - .ordered_flush = 1, };static struct ata_port_operations pdc_20621_ops = {
drivers/scsi/sata_uli.c +0 -1
@@ -82,7 +82,6 @@ static Scsi_Host_Template uli_sht = { .dma_boundary = ATA_DMA_BOUNDARY, .slave_configure = ata_scsi_slave_config, .bios_param = ata_std_bios_param, - .ordered_flush = 1, };static struct ata_port_operations uli_ops = {
drivers/scsi/sata_via.c +0 -1
@@ -102,7 +102,6 @@ static Scsi_Host_Template svia_sht = { .dma_boundary = ATA_DMA_BOUNDARY, .slave_configure = ata_scsi_slave_config, .bios_param = ata_std_bios_param, - .ordered_flush = 1, };static struct ata_port_operations svia_sata_ops = {
drivers/scsi/sata_vsc.c +0 -1
@@ -206,7 +206,6 @@ static Scsi_Host_Template vsc_sata_sht = .dma_boundary = ATA_DMA_BOUNDARY, .slave_configure = ata_scsi_slave_config, .bios_param = ata_std_bios_param, - .ordered_flush = 1, };
Re: [PATCH linux-2.6-block:master 06/10] blk: update libata to use new blk_ordered
Quoted 4 lines · Tejun Heo
06_blk_libata-update-ordered.patch
Reflect changes in SCSI midlayer and updated to use new ordered request implementation
ACK
Re: [PATCH linux-2.6-block:master 07/10] blk: add FUA support to libata
In reply to Tejun Heo07_blk_libata-add-fua-support.patch
Add FUA support to libata.
drivers/scsi/libata-core.c | 14 +++++++++----- drivers/scsi/libata-scsi.c | 26 ++++++++++++++++++++++++-- include/linux/ata.h | 4 +++- include/linux/libata.h | 1 + 4 files changed, 37 insertions(+), 8 deletions(-)
drivers/scsi/libata-core.c +9 -5
@@ -602,19 +602,21 @@ void ata_tf_from_fis(u8 *fis, struct ata }/** -* ata_prot_to_cmd - determine which read/write opcodes to use +* ata_prot_to_cmd - determine which read/write/fua-write opcodes to use * @protocol: ATA_PROT_xxx taskfile protocol * @lba48: true is lba48 is present * -* Given necessary input, determine which read/write commands -* to use to transfer data. +* Given necessary input, determine which read/write/fua-write +* commands to use to transfer data. Note that we only support +* fua-writes on DMA LBA48 protocol. In other cases, we simply +* return 0 which is NOP. * * LOCKING: * None. */ static int ata_prot_to_cmd (int protocol,int lba48) { -int rcmd =0 , wcmd =0 ; +int rcmd =0 , wcmd =0 , wfua =0 ;switch (protocol) {case ATA_PROT_PIO :
@@ -631,6 +633,7 @@ static int ata_prot_to_cmd(int protocol,if (lba48) { rcmd =ATA_CMD_READ_EXT ; wcmd =ATA_CMD_WRITE_EXT ; + wfua =ATA_CMD_WRITE_FUA_EXT ; }else { rcmd =ATA_CMD_READ ; wcmd =ATA_CMD_WRITE ;
@@ -641,7 +644,7 @@ static int ata_prot_to_cmd(int protocol,return -1 ; } -return rcmd | (wcmd <<8 ); +return rcmd | (wcmd <<8 ) | (wfua <<16 ); }/**
@@ -674,6 +677,7 @@ static void ata_dev_set_protocol(struct dev->read_cmd = cmd &0xff ; dev->write_cmd = (cmd >>8 ) &0xff ; + dev->write_fua_cmd = (cmd >>16 ) &0xff ; }static const char * xfer_mode_str[] = {
include/linux/ata.h +3 -1
@@ -117,6 +117,7 @@ enum {ATA_CMD_READ_EXT =0x25 ,ATA_CMD_WRITE =0xCA ,ATA_CMD_WRITE_EXT =0x35 , +ATA_CMD_WRITE_FUA_EXT =0x3D ,ATA_CMD_PIO_READ =0x20 ,ATA_CMD_PIO_READ_EXT =0x24 , ATA_CMD_PIO_WRITE = 0x30,
@@ -227,7 +228,8 @@ struct ata_taskfile {#define ata_id_is_sata (id) ((id)[93] == 0)#define ata_id_rahead_enabled (id) ((id)[85] & (1 << 6))#define ata_id_wcache_enabled (id) ((id)[85] & (1 << 5)) -#define ata_id_has_flush (id) ((id)[83] & (1 << 12)) +#define ata_id_has_fua (id) ((id)[84] & (1 << 6)) +#define ata_id_has_flush (id) ((id)[83] & (1 << 12))#define ata_id_has_flush_ext (id) ((id)[83] & (1 << 13))#define ata_id_has_lba48 (id) ((id)[83] & (1 << 10))#define ata_id_has_wcache (id) ((id)[82] & (1 << 5))
include/linux/libata.h +1 -0
@@ -278,6 +278,7 @@ struct ata_device {u8 xfer_protocol;/* taskfile xfer protocol */ u8 read_cmd;/* opcode to use on read */ u8 write_cmd;/* opcode to use on write */ +u8 write_fua_cmd;/* opcode to use on FUA write */ };struct ata_port {
drivers/scsi/libata-scsi.c +24 -2
@@ -537,6 +537,7 @@ static unsigned int ata_scsi_rw_xlat(str {struct ata_taskfile *tf = &qc->tf;unsigned int lba48 = tf->flags &ATA_TFLAG_LBA48 ; +int fua = scsicmd[1 ] & (1 <<3 ); tf->flags |=ATA_TFLAG_ISADDR |ATA_TFLAG_DEVICE ; tf->protocol = qc->dev->xfer_protocol;
@@ -544,9 +545,28 @@ static unsigned int ata_scsi_rw_xlat(strif (scsicmd[0 ] ==READ_10 || scsicmd[0 ] ==READ_6 || scsicmd[0 ] ==READ_16 ) { - tf->command = qc->dev->read_cmd; +if (!fua) { + tf->command = qc->dev->read_cmd; + }else { +printk (KERN_WARNING +"ata%u(%u): WARNING: FUA READ unsupported\n" , + qc->ap->id, qc->dev->devno); +return 1 ; + } }else { - tf->command = qc->dev->write_cmd; +if (!fua) { + tf->command = qc->dev->write_cmd; + }else { +if (qc->dev->write_fua_cmd ==0 || !lba48) { +printk (KERN_WARNING +"ata%u(%u): WARNING: FUA WRITE " +"unsupported with the current " +"protocol/addressing\n" , + qc->ap->id, qc->dev->devno); +return 1 ; + } + tf->command = qc->dev->write_fua_cmd; + } tf->flags |=ATA_TFLAG_WRITE ; }
@@ -1141,10 +1161,12 @@ unsigned int ata_scsiop_mode_sense(strucif (six_byte) { output_len--; rbuf[0 ] = output_len; + rbuf[2 ] |=ata_id_has_fua (args->id) ?1 <<4 :0 ; }else { output_len -=2 ; rbuf[0 ] = output_len >>8 ; rbuf[1 ] = output_len; + rbuf[3 ] |=ata_id_has_fua (args->id) ?1 <<4 :0 ; }return 0 ;
Jeff Garzik
NAKRe: [PATCH linux-2.6-block:master 07/10] blk: add FUA support to libata
Quoted 3 lines · Tejun Heo
07_blk_libata-add-fua-support.patch
Add FUA support to libata.
NAK -- doesn't appear to take into account that read/write(6) don't support FUA.
Correct me if I'm wrong.
Otherwise, looks OK.
Re: [PATCH linux-2.6-block:master 07/10] blk: add FUA support to libata
Quoted 12 lines · Jeff Garzik
Quoted 3 lines · Tejun Heo
07_blk_libata-add-fua-support.patch
Add FUA support to libata.
NAK -- doesn't appear to take into account that read/write(6) don't support FUA.
Correct me if I'm wrong.
Otherwise, looks OK.
Hello, Jeff.
I'm sorry. It's my bad. Here's the corrected one. Thanks for
pointing out.
As this patch is the last one which modifies libata, this changes
does not affect other patches in this patchset. Just ignoring the original one and applying this one should suffice.
drivers/scsi/libata-core.c +9 -5
@@ -602,19 +602,21 @@ void ata_tf_from_fis(u8 *fis, struct ata }/** -* ata_prot_to_cmd - determine which read/write opcodes to use +* ata_prot_to_cmd - determine which read/write/fua-write opcodes to use * @protocol: ATA_PROT_xxx taskfile protocol * @lba48: true is lba48 is present * -* Given necessary input, determine which read/write commands -* to use to transfer data. +* Given necessary input, determine which read/write/fua-write +* commands to use to transfer data. Note that we only support +* fua-writes on DMA LBA48 protocol. In other cases, we simply +* return 0 which is NOP. * * LOCKING: * None. */ static int ata_prot_to_cmd (int protocol,int lba48) { -int rcmd =0 , wcmd =0 ; +int rcmd =0 , wcmd =0 , wfua =0 ;switch (protocol) {case ATA_PROT_PIO :
@@ -631,6 +633,7 @@ static int ata_prot_to_cmd(int protocol,if (lba48) { rcmd =ATA_CMD_READ_EXT ; wcmd =ATA_CMD_WRITE_EXT ; + wfua =ATA_CMD_WRITE_FUA_EXT ; }else { rcmd =ATA_CMD_READ ; wcmd =ATA_CMD_WRITE ;
@@ -641,7 +644,7 @@ static int ata_prot_to_cmd(int protocol,return -1 ; } -return rcmd | (wcmd <<8 ); +return rcmd | (wcmd <<8 ) | (wfua <<16 ); }/**
@@ -674,6 +677,7 @@ static void ata_dev_set_protocol(struct dev->read_cmd = cmd &0xff ; dev->write_cmd = (cmd >>8 ) &0xff ; + dev->write_fua_cmd = (cmd >>16 ) &0xff ; }static const char * xfer_mode_str[] = {
include/linux/ata.h +3 -1
@@ -117,6 +117,7 @@ enum {ATA_CMD_READ_EXT =0x25 ,ATA_CMD_WRITE =0xCA ,ATA_CMD_WRITE_EXT =0x35 , +ATA_CMD_WRITE_FUA_EXT =0x3D ,ATA_CMD_PIO_READ =0x20 ,ATA_CMD_PIO_READ_EXT =0x24 , ATA_CMD_PIO_WRITE = 0x30,
@@ -227,7 +228,8 @@ struct ata_taskfile {#define ata_id_is_sata (id) ((id)[93] == 0)#define ata_id_rahead_enabled (id) ((id)[85] & (1 << 6))#define ata_id_wcache_enabled (id) ((id)[85] & (1 << 5)) -#define ata_id_has_flush (id) ((id)[83] & (1 << 12)) +#define ata_id_has_fua (id) ((id)[84] & (1 << 6)) +#define ata_id_has_flush (id) ((id)[83] & (1 << 12))#define ata_id_has_flush_ext (id) ((id)[83] & (1 << 13))#define ata_id_has_lba48 (id) ((id)[83] & (1 << 10))#define ata_id_has_wcache (id) ((id)[82] & (1 << 5))
include/linux/libata.h +1 -0
@@ -278,6 +278,7 @@ struct ata_device {u8 xfer_protocol;/* taskfile xfer protocol */ u8 read_cmd;/* opcode to use on read */ u8 write_cmd;/* opcode to use on write */ +u8 write_fua_cmd;/* opcode to use on FUA write */ };struct ata_port {
drivers/scsi/libata-scsi.c +33 -3
@@ -542,12 +542,40 @@ static unsigned int ata_scsi_rw_xlat(str tf->protocol = qc->dev->xfer_protocol; tf->device |=ATA_LBA ; -if (scsicmd[0 ] ==READ_10 || scsicmd[0 ] ==READ_6 || - scsicmd[0 ] ==READ_16 ) { +switch (scsicmd[0 ]) { +case READ_10 : +case READ_16 : +if (unlikely (scsicmd[1 ] & (1 <<3 ))) { +printk (KERN_WARNING +"ata%u(%u): WARNING: FUA READ unsupported\n" , + qc->ap->id, qc->dev->devno); +return 1 ; + } +/* fall through */ +case READ_6 : tf->command = qc->dev->read_cmd; - }else { +break ; + +case WRITE_10 : +case WRITE_16 : +if (unlikely (scsicmd[1 ] & (1 <<3 ))) { +if (qc->dev->write_fua_cmd ==0 || !lba48) { +printk (KERN_WARNING +"ata%u(%u): WARNING: FUA WRITE " +"unsupported with the current " +"protocol/addressing\n" , + qc->ap->id, qc->dev->devno); +return 1 ; + } + tf->command = qc->dev->write_fua_cmd; + tf->flags |=ATA_TFLAG_WRITE ; +break ; + } +/* fall through */ +case WRITE_6 : tf->command = qc->dev->write_cmd; tf->flags |=ATA_TFLAG_WRITE ; +break ; }if (scsicmd[0 ] ==READ_10 || scsicmd[0 ] ==WRITE_10 ) {
@@ -1141,10 +1169,12 @@ unsigned int ata_scsiop_mode_sense(strucif (six_byte) { output_len--; rbuf[0 ] = output_len; + rbuf[2 ] |=ata_id_has_fua (args->id) ?1 <<4 :0 ; }else { output_len -=2 ; rbuf[0 ] = output_len >>8 ; rbuf[1 ] = output_len; + rbuf[3 ] |=ata_id_has_fua (args->id) ?1 <<4 :0 ; }return 0 ;
Re: [PATCH linux-2.6-block:master 03/10] blk: reimplement handling of barrier request
In reply to Tejun Heo03_blk_reimplement-ordered.patch
Reimplement handling of barrier requests.
* Flexible handling to deal with various capabilities of target devices.
* Retry support for falling back.
* Tagged queues which don't support ordered tag can do ordered.
drivers/block/elevator.c | 83 +++++--- drivers/block/ll_rw_blk.c | 468 ++++++++++++++++++++++++++++++++-------------- include/linux/blkdev.h | 83 +++++--- include/linux/elevator.h | 1 4 files changed, 443 insertions(+), 192 deletions(-)
drivers/block/elevator.c +57 -26
@@ -326,22 +326,24 @@ void elv_requeue_request(request_queue_t rq->flags &= ~REQ_STARTED ; -/* -* if this is the flush, requeue the original instead and drop the flush -*/ -if (rq->flags &REQ_BAR_FLUSH ) { -clear_bit (QUEUE_FLAG_FLUSH , &q->queue_flags); - rq = rq->end_io_data; - } - -__elv_add_request (q, rq,ELEVATOR_INSERT_FRONT ,0 ); +__elv_add_request (q, rq,ELEVATOR_INSERT_REQUEUE ,0 ); }void __elv_add_request (request_queue_t *q,struct request *rq,int where,int plug) { +struct list_head *pos; +unsigned ordseq; + + rq->flags |= q->ordcolor ?REQ_ORDERED_COLOR :0 ; +if (rq->flags & (REQ_SOFTBARRIER |REQ_HARDBARRIER )) {/* +* toggle ordered color +*/ + q->ordcolor ^=1 ; + +/* * barriers implicitly indicate back insertion */ if (where ==ELEVATOR_INSERT_SORT )
@@ -397,6 +399,30 @@ void __elv_add_request(request_queue_t * q->last_merge = rq;break ; +case ELEVATOR_INSERT_REQUEUE : +/* +* If ordered flush isn't in progress, we do front +* insertion; otherwise, requests should be requeued +* in ordseq order. +*/ + rq->flags |=REQ_SOFTBARRIER ; + +if (q->ordseq ==0 ) { +list_add (&rq->queuelist, &q->queue_head); +break ; + } + + ordseq =blk_ordered_req_seq (rq); + +list_for_each (pos, &q->queue_head) { +struct request *pos_rq =list_entry_rq (pos); +if (ordseq <=blk_ordered_req_seq (pos_rq)) +break ; + } + +list_add_tail (&rq->queuelist, pos); +break ; +default :printk (KERN_ERR "%s: bad insertion point %d\n" , __FUNCTION__, where);
@@ -426,25 +452,16 @@ static inline struct request *__elv_next {struct request *rq; -if (unlikely (list_empty (&q->queue_head) && - !q->elevator->ops->elevator_dispatch_fn (q,0 ))) -return NULL ; - - rq =list_entry_rq (q->queue_head.next); - -/* -* if this is a barrier write and the device has to issue a -* flush sequence to support it, check how far we are -*/ -if (blk_fs_request (rq) &&blk_barrier_rq (rq)) { -BUG_ON (q->ordered ==QUEUE_ORDERED_NONE ); +while (1 ) { +while (!list_empty (&q->queue_head)) { + rq =list_entry_rq (q->queue_head.next); +if (blk_do_ordered (q, &rq)) +return rq; + } -if (q->ordered ==QUEUE_ORDERED_FLUSH && - !blk_barrier_preflush (rq)) - rq =blk_start_pre_flush (q, rq); +if (!q->elevator->ops->elevator_dispatch_fn (q,0 )) +return NULL ; } - -return rq; }struct request *elv_next_request (request_queue_t *q)
@@ -610,7 +627,21 @@ void elv_completed_request(request_queue* request is released from the driver, io must be done */ if (blk_account_rq (rq)) { +struct request *first_rq =list_entry_rq (q->queue_head.next); + q->in_flight--; + +/* +* Check if the queue is waiting for fs requests to be +* drained for flush sequence. +*/ +if (q->ordseq && q->in_flight ==0 && +blk_ordered_cur_seq (q) ==QUEUE_ORDSEQ_DRAIN && +blk_ordered_req_seq (first_rq) >QUEUE_ORDSEQ_DRAIN ) { +blk_ordered_complete_seq (q,QUEUE_ORDSEQ_DRAIN ,0 ); + q->request_fn (q); + } +if (blk_sorted_rq (rq) && e->ops->elevator_completed_req_fn) e->ops->elevator_completed_req_fn (q, rq); }
drivers/block/ll_rw_blk.c +327 -141
569 lines not on this page · raw message
include/linux/blkdev.h +58 -25
149 lines not on this page · raw message
include/linux/elevator.h +1 -0
@@ -130,6 +130,7 @@ extern int elv_try_last_merge(request_qu#define ELEVATOR_INSERT_FRONT 1#define ELEVATOR_INSERT_BACK 2#define ELEVATOR_INSERT_SORT 3 +#define ELEVATOR_INSERT_REQUEUE 4/* * return values from elevator_may_queue_fn
Re: [PATCH linux-2.6-block:master 04/10] blk: update SCSI to use new blk_ordered
In reply to Tejun Heo04_blk_scsi-update-ordered.patch
All ordered request related stuff delegated to HLD. Midlayer now doens't deal with ordered setting or prepare_flush callback. sd.c updated to deal with blk_queue_ordered setting. Currently, ordered tag isn't used as SCSI midlayer cannot guarantee request ordering.
drivers/scsi/hosts.c | 9 ------ drivers/scsi/scsi_lib.c | 46 ------------------------------- drivers/scsi/sd.c | 66 ++++++++++++++++----------------------------- include/scsi/scsi_driver.h | 1 include/scsi/scsi_host.h | 1 5 files changed, 24 insertions(+), 99 deletions(-)
drivers/scsi/hosts.c +0 -9
@@ -264,17 +264,8 @@ struct Scsi_Host *scsi_host_alloc(struct shost->cmd_per_lun = sht->cmd_per_lun; shost->unchecked_isa_dma = sht->unchecked_isa_dma; shost->use_clustering = sht->use_clustering; - shost->ordered_flush = sht->ordered_flush; shost->ordered_tag = sht->ordered_tag; -/* -* hosts/devices that do queueing must support ordered tags -*/ -if (shost->can_queue >1 && shost->ordered_flush) { -printk (KERN_ERR "scsi: ordered flushes don't support queueing\n" ); - shost->ordered_flush =0 ; - } -if (sht->max_host_blocked) shost->max_host_blocked = sht->max_host_blocked;else
drivers/scsi/scsi_lib.c +0 -46
64 lines not on this page · raw message
drivers/scsi/sd.c +24 -42
115 lines not on this page · raw message
include/scsi/scsi_driver.h +0 -1
@@ -15,7 +15,6 @@ struct scsi_driver {void (*rescan)(struct device *);int (*issue_flush)(struct device *,sector_t *);int (*prepare_flush)(struct request_queue *,struct request *); -void (*end_flush)(struct request_queue *,struct request *); };#define to_scsi_driver (drv) \ container_of((drv), struct scsi_driver, gendrv)
include/scsi/scsi_host.h +0 -1
@@ -391,7 +391,6 @@ struct scsi_host_template {/* * ordered write support */ - unsigned ordered_flush:1; unsigned ordered_tag:1;/*
Re: [PATCH linux-2.6-block:master 08/10] blk: update IDE to use new blk_ordered
In reply to Tejun Heo08_blk_ide-update-ordered.patch
Update IDE to use new blk_ordered.
ide-disk.c | 57 +++++++++------------------------------------------------ ide-io.c | 5 +---- 2 files changed, 10 insertions(+), 52 deletions(-)
drivers/ide/ide-disk.c +9 -48
@@ -677,50 +677,9 @@ static ide_proc_entry_t idedisk_proc[] =#endif /* CONFIG_PROC_FS */ -static void idedisk_end_flush (request_queue_t *q,struct request *flush_rq) +static void idedisk_prepare_flush (request_queue_t *q,struct request *rq) {ide_drive_t *drive = q->queuedata; -struct request *rq = flush_rq->end_io_data; -int good_sectors = rq->hard_nr_sectors; -int bad_sectors; -sector_t sector; - -if (flush_rq->errors &ABRT_ERR ) { -printk (KERN_ERR "%s: barrier support doesn't work\n" , drive->name); -blk_queue_ordered (drive->queue,QUEUE_ORDERED_NONE ); -blk_queue_issue_flush_fn (drive->queue,NULL ); - good_sectors =0 ; - }else if (flush_rq->errors) { - good_sectors =0 ; -if (blk_barrier_preflush (rq)) { - sector =ide_get_error_location (drive,flush_rq->buffer); -if ((sector >= rq->hard_sector) && - (sector < rq->hard_sector + rq->hard_nr_sectors)) - good_sectors = sector - rq->hard_sector; - } - } - -if (flush_rq->errors) -printk (KERN_ERR "%s: failed barrier write: " -"sector=%Lx(good=%d/bad=%d)\n" , - drive->name, (unsigned long long )rq->sector, - good_sectors, - (int ) (rq->hard_nr_sectors-good_sectors)); - - bad_sectors = rq->hard_nr_sectors - good_sectors; - -if (good_sectors) -__ide_end_request (drive, rq,1 , good_sectors); -if (bad_sectors) -__ide_end_request (drive, rq,0 , bad_sectors); -} - -static int idedisk_prepare_flush (request_queue_t *q,struct request *rq) -{ -ide_drive_t *drive = q->queuedata; - -if (!drive->wcache) -return 0 ;memset (rq->cmd,0 ,sizeof (rq->cmd));
@@ -731,9 +690,8 @@ static int idedisk_prepare_flush(request rq->cmd[0 ] =WIN_FLUSH_CACHE ; - rq->flags |=REQ_DRIVE_TASK |REQ_SOFTBARRIER ; + rq->flags |=REQ_DRIVE_TASK ; rq->buffer = rq->cmd; -return 1 ; } static int idedisk_issue_flush(request_queue_t *q, struct gendisk *disk,
@@ -1008,11 +966,12 @@ static void idedisk_setup (ide_drive_t *printk (KERN_INFO "%s: cache flushes %ssupported\n" , drive->name, barrier ?"" :"not " );if (barrier) { -blk_queue_ordered (drive->queue,QUEUE_ORDERED_FLUSH ); - drive->queue->prepare_flush_fn = idedisk_prepare_flush; - drive->queue->end_flush_fn = idedisk_end_flush; +blk_queue_ordered (drive->queue,QUEUE_ORDERED_DRAIN_FLUSH , + idedisk_prepare_flush,GFP_KERNEL );blk_queue_issue_flush_fn (drive->queue, idedisk_issue_flush); - } + }else if (!drive->wcache) +blk_queue_ordered (drive->queue,QUEUE_ORDERED_DRAIN , +NULL ,GFP_KERNEL ); }static void ide_cacheflush_p (ide_drive_t *drive)
@@ -1030,6 +989,8 @@ static int ide_disk_remove(struct devicestruct ide_disk_obj *idkp = drive->driver_data;struct gendisk *g = idkp->disk; +blk_queue_ordered (drive->queue,QUEUE_ORDERED_NONE ,NULL ,0 ); +ide_cacheflush_p (drive);ide_unregister_subdriver (drive, idkp->driver);
drivers/ide/ide-io.c +1 -4
@@ -119,10 +119,7 @@ int ide_end_request (ide_drive_t *drive,if (!nr_sectors) nr_sectors = rq->hard_cur_sectors; -if (blk_complete_barrier_rq_locked (drive->queue, rq, nr_sectors)) - ret = rq->nr_sectors !=0 ; -else - ret =__ide_end_request (drive, rq, uptodate, nr_sectors); + ret =__ide_end_request (drive, rq, uptodate, nr_sectors);spin_unlock_irqrestore (&ide_lock, flags);return ret;
Re: [PATCH linux-2.6-block:master 09/10] blk: add FUA support to IDE
In reply to Tejun Heo09_blk_ide-add-fua-support.patch
Add FUA support to IDE
drivers/ide/ide-disk.c | 57 +++++++++++++++++++++++++++++++++++++++++-------- include/linux/ata.h | 1 include/linux/hdreg.h | 16 ++++++++++++- include/linux/ide.h | 3 ++ 4 files changed, 66 insertions(+), 11 deletions(-)
drivers/ide/ide-disk.c +48 -9
@@ -160,13 +160,14 @@ static ide_startstop_t __ide_do_rw_disk(ide_hwif_t *hwif =HWIF (drive);unsigned int dma = drive->using_dma;u8 lba48 = (drive->addressing ==1 ) ?1 :0 ; +int fua =blk_fua_rq (rq);task_ioreg_t command =WIN_NOP ;ata_nsector_t nsectors; nsectors.all = (u16 ) rq->nr_sectors;if (hwif->no_lba48_dma && lba48 && dma) { -if (block + rq->nr_sectors >1ULL <<28 ) +if (block + rq->nr_sectors >1ULL <<28 || fua) dma =0 ;else lba48 =0 ;
@@ -222,6 +223,16 @@ static ide_startstop_t __ide_do_rw_disk( hwif->OUTB (tasklets[6 ],IDE_HCYL_REG ); hwif->OUTB (0x00 |drive->select.all,IDE_SELECT_REG ); }else { +if (unlikely (fua)) { +/* +* This happens if LBA48 addressing is +* turned off during operation. +*/ +printk (KERN_ERR "%s: FUA write but LBA48 off\n" , + drive->name); + goto fail; + } + hwif->OUTB (0x00 ,IDE_FEATURE_REG ); hwif->OUTB (nsectors.b.low,IDE_NSECTOR_REG ); hwif->OUTB (block,IDE_SECTOR_REG );
@@ -249,9 +260,12 @@ static ide_startstop_t __ide_do_rw_disk(if (dma) {if (!hwif->dma_setup (drive)) {if (rq_data_dir (rq)) { - command = lba48 ?WIN_WRITEDMA_EXT :WIN_WRITEDMA ; -if (drive->vdma) - command = lba48 ?WIN_WRITE_EXT :WIN_WRITE ; +if (!fua) { + command = lba48 ?WIN_WRITEDMA_EXT :WIN_WRITEDMA ; +if (drive->vdma) + command = lba48 ?WIN_WRITE_EXT :WIN_WRITE ; + }else + command =ATA_CMD_WRITE_FUA_EXT ; }else { command = lba48 ?WIN_READDMA_EXT :WIN_READDMA ;if (drive->vdma)
@@ -280,8 +294,20 @@ static ide_startstop_t __ide_do_rw_disk( }else {if (drive->mult_count) { hwif->data_phase =TASKFILE_MULTI_OUT ; - command = lba48 ?WIN_MULTWRITE_EXT :WIN_MULTWRITE ; +if (!fua) + command = lba48 ?WIN_MULTWRITE_EXT :WIN_MULTWRITE ; +else + command =ATA_CMD_MULT_WRITE_FUA_EXT ; }else { +if (unlikely (fua)) { +/* +* This happens if multisector PIO is +* turned off during operation. +*/ +printk (KERN_ERR "%s: FUA write but in single " +"sector PIO mode\n" , drive->name); + goto fail; + } hwif->data_phase =TASKFILE_OUT ; command = lba48 ?WIN_WRITE_EXT :WIN_WRITE ; }
@@ -291,6 +317,10 @@ static ide_startstop_t __ide_do_rw_disk(return pre_task_out_intr (drive, rq); } + + fail: +ide_end_request (drive,0 ,0 ); +return ide_stopped; }/*
@@ -842,7 +872,7 @@ static void idedisk_setup (ide_drive_t * {struct hd_driveid *id = drive->id;unsigned long long capacity; -int barrier; +int barrier, fua;idedisk_add_settings (drive);
@@ -963,10 +993,19 @@ static void idedisk_setup (ide_drive_t * barrier =0 ; } -printk (KERN_INFO "%s: cache flushes %ssupported\n" , - drive->name, barrier ?"" :"not " ); + fua = barrier &&idedisk_supports_lba48 (id) &&ide_id_has_fua (id); +/* When using PIO, FUA needs multisector. */ +if ((!drive->using_dma || drive->hwif->no_lba48_dma) && + drive->mult_count ==0 ) + fua =0 ; + +printk (KERN_INFO "%s: cache flushes %ssupported%s\n" , + drive->name, barrier ?"" :"not " , + fua ?" w/ FUA" :"" );if (barrier) { -blk_queue_ordered (drive->queue,QUEUE_ORDERED_DRAIN_FLUSH , +unsigned ordered = fua ?QUEUE_ORDERED_DRAIN_FUA + :QUEUE_ORDERED_DRAIN_FLUSH ; +blk_queue_ordered (drive->queue, ordered, idedisk_prepare_flush,GFP_KERNEL );blk_queue_issue_flush_fn (drive->queue, idedisk_issue_flush); }else if (!drive->wcache)
include/linux/ata.h +1 -0
@@ -122,6 +122,7 @@ enum {ATA_CMD_PIO_READ_EXT =0x24 ,ATA_CMD_PIO_WRITE =0x30 ,ATA_CMD_PIO_WRITE_EXT =0x34 , +ATA_CMD_MULT_WRITE_FUA_EXT =0xCE ,ATA_CMD_SET_FEATURES =0xEF ,ATA_CMD_PACKET =0xA0 , ATA_CMD_VERIFY = 0x40,
include/linux/hdreg.h +14 -2
@@ -550,7 +550,13 @@ struct hd_driveid {* cmd set-feature supported extensions * 15: Shall be ZERO * 14: Shall be ONE -* 13:6 reserved +* 13: IDLE IMMEDIATE w/ UNLOAD FEATURE +* 12:11 reserved for technical report +* 10: URG for WRITE STREAM +* 9: URG for READ STREAM +* 8: 64-bit World wide name +* 7: WRITE DMA QUEUED FUA EXT +* 6: WRITE DMA/MULTIPLE FUA EXT * 5: General Purpose Logging * 4: Streaming Feature Set * 3: Media Card Pass Through
@@ -600,7 +606,13 @@ struct hd_driveid {* command set-feature default * 15: Shall be ZERO * 14: Shall be ONE -* 13:6 reserved +* 13: IDLE IMMEDIATE w/ UNLOAD FEATURE +* 12:11 reserved for technical report +* 10: URG for WRITE STREAM +* 9: URG for READ STREAM +* 8: 64-bit World wide name +* 7: WRITE DMA QUEUED FUA EXT +* 6: WRITE DMA/MULTIPLE FUA EXT * 5: General Purpose Logging enabled * 4: Valid CONFIGURE STREAM executed * 3: Media Card Pass Through enabled
include/linux/ide.h +3 -0
@@ -1497,6 +1497,9 @@ extern struct bus_type ide_bus_type;/* check if CACHE FLUSH (EXT) command is supported (bits defined in ATA-6) */ #define ide_id_has_flush_cache (id) ((id)->cfs_enable_2 & 0x3000) +/* check if WRITE DMA FUA EXT command is supported (defined in ATA-8) */ +#define ide_id_has_fua (id) ((id)->cfsse & 0x0040) +/* some Maxtor disks have bit 13 defined incorrectly so check bit 10 too */ #define ide_id_has_flush_cache_ext (id) \ (((id)->cfs_enable_2 & 0x2400) == 0x2400)