diff options
author | Christoph Hellwig <hch@infradead.org> | 2009-09-30 13:52:12 +0200 |
---|---|---|
committer | Jens Axboe <jens.axboe@oracle.com> | 2009-10-01 21:19:30 +0200 |
commit | c15227de132f1295f3db6b7df9079956b1020fd8 (patch) | |
tree | ad06f119f283cf8a6313681055e8132ba2851ddb /kernel/gcov | |
parent | 3bd0f0c763e497c8674b28e3df2732f48683dabd (diff) | |
download | linux-stable-c15227de132f1295f3db6b7df9079956b1020fd8.tar.gz linux-stable-c15227de132f1295f3db6b7df9079956b1020fd8.tar.bz2 linux-stable-c15227de132f1295f3db6b7df9079956b1020fd8.zip |
block: use normal I/O path for discard requests
prepare_discard_fn() was being called in a place where memory allocation
was effectively impossible. This makes it inappropriate for all but
the most trivial translations of Linux's DISCARD operation to the block
command set. Additionally adding a payload there makes the ownership
of the bio backing unclear as it's now allocated by the device driver
and not the submitter as usual.
It is replaced with QUEUE_FLAG_DISCARD which is used to indicate whether
the queue supports discard operations or not. blkdev_issue_discard now
allocates a one-page, sector-length payload which is the right thing
for the common ATA and SCSI implementations.
The mtd implementation of prepare_discard_fn() is replaced with simply
checking for the request being a discard.
Largely based on a previous patch from Matthew Wilcox <matthew@wil.cx>
which did the prepare_discard_fn but not the different payload allocation
yet.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'kernel/gcov')
0 files changed, 0 insertions, 0 deletions