From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
neilb@suse.de, agk@sourceware.org, linux-kernel@vger.kernel.org,
dm-devel@redhat.com
Subject: Re: Block integrity patches for 2.6.28
Date: Thu, 02 Oct 2008 09:54:31 -0400 [thread overview]
Message-ID: <yq1wsgrgl0o.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20081002105632.GF19428@kernel.dk> (Jens Axboe's message of "Thu\, 2 Oct 2008 12\:56\:32 +0200")
>>>>> "Jens" == Jens Axboe <jens.axboe@oracle.com> writes:
Jens> As far as I can tell, most of that commit is still fine. You
Jens> want bdev_get_integrity() in blkdev.h, the 3 other moves and the
Jens> unused bdev_get_tag_size() do not look like they are being used
Jens> by this patch set.
bdev_get_integrity() and bdev_get_tag_size() are being used by
stacking drivers and filesystems to prepare I/O. It's correct that
none of the in-tree stuff currently uses bdev_get_tag_size(). That's
coming with the btrfs support. If you want to pull that out for now
and have me put that back later in that's ok. Just adds another
two-stage merge dependency for a later cycle.
bdev_integrity_enabled() and blk_integrity_tuple_size() are only being
used from within bio-integrity.c and can move there. I originally put
them in blkdev.h because they are block device functions and not bio
ditto.
Want me to submit a new patch shuffling bdev_get_integrity() back
where it came from?
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2008-10-02 13:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 7:38 Block integrity patches for 2.6.28 Martin K. Petersen
2008-10-01 7:38 ` [PATCH 1/7] block: Introduce integrity data ownership flag Martin K. Petersen
2008-10-01 7:38 ` [PATCH 2/7] block: Fix double put in blk_integrity_unregister Martin K. Petersen
2008-10-01 7:38 ` [PATCH 3/7] block: Switch blk_integrity_compare from bdev to gendisk Martin K. Petersen
2008-10-01 7:38 ` [PATCH 4/7] block: gendisk integrity wrapper Martin K. Petersen
2008-10-01 7:38 ` [PATCH 5/7] block: Find bio sector offset given idx and offset Martin K. Petersen
2008-10-01 8:10 ` Jens Axboe
2008-10-02 2:42 ` Martin K. Petersen
2008-10-02 17:07 ` Jens Axboe
2008-10-01 7:38 ` [PATCH 6/7] dm: Add support for data integrity to DM Martin K. Petersen
2008-10-01 7:38 ` [PATCH 7/7] md: Add support for data integrity to MD Martin K. Petersen
2008-10-02 10:56 ` Block integrity patches for 2.6.28 Jens Axboe
2008-10-02 13:54 ` Martin K. Petersen [this message]
2008-10-02 16:29 ` Jens Axboe
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=yq1wsgrgl0o.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=agk@sourceware.org \
--cc=dm-devel@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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