linux-ext4 - Re: discard + LVM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 08 Mar 2010 14:46:12 -0500
From:	"Martin K. Petersen" <martin.petersen@...cle.com>
To:	Mike Snitzer <snitzer@...hat.com>
Cc:	"Martin K. Petersen" <martin.petersen@...cle.com>,
	Eric Sandeen <sandeen@...hat.com>,
	Andreas Sundstrom <sunkan@...pa.cx>,
	linux-ext4@...r.kernel.org, dm-devel@...hat.com,
	linux-raid@...r.kernel.org, Christoph Hellwig <hch@...radead.org>
Subject: Re: discard + LVM

>>>>> "Mike" == Mike Snitzer <snitzer@...hat.com> writes:

Mike> We've been scoping the work associated with adding discard support
Mike> to DM (afaik MD would need comparable infrastructure, e.g.:
Mike> spliting discard requests).

Mike> There is a fair amount of complexity associated with this work.
Mike> Especially when you look to support discards for some of the more
Mike> advanced DM targets.  Discard support for the 'linear' target is
Mike> the relatively low hanging fruit.  The 'striped' target gets more
Mike> interesting (having to split the discard into multiple discards to
Mike> submit to the appropriate underlying devices in the striped
Mike> volume).

Mike> One thought was we might have a block layer hook along the lines
Mike> of the q->merge_bvec_fn (similar but hopefully less
Mike> problematic/controversial).  Christoph removed a hook that was
Mike> vaguely like this, but posed allocation problems, with linux-2.6
Mike> commit: c15227de132f

This is a work in progress and something that turned out to be much
harder than I anticipated.  Discard is not the only problem child here.
The other one is write same.  In both cases we'll have to split things
that cover an area bigger than the corresponding bio_vec payload.

At first I took the blk_pc splitting approach but it got really hairy
and had lots of special casing.  So what I'm working on right now is to
make write same and discard requests first class citizens so they can be
split and merged like regular write requests.  There are lots of
assumptions in our stack about things being either read or write so it's
a pretty invasive change.  But at this point it looks like it'll be
nicer than my first attempt.  Still plugging away at it though...

-- 
Martin K. Petersen	Oracle Linux Engineering
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html