On Fri, Jun 10, 2011 at 01:40:31PM +0800, Li Dongyang wrote:
otherwise the patch looks good (and matches my view how to do it). I
will test it eventually.
Thanks a lot, I'll resend this this a proper name.
JFYI, tested in the previous scenario, ie. all devices without trim
support, does not
With discard flag in btrfs_device, we will only push trim request to the
devices support that.
Now we don't return EOPNOTSUPP to the caller, so we won't trigger BUG_ONs
in the walk_log_tree functions if we mount a drive without DISCARD
using -o discard, but it is still possible if we get errors
On Thu, Jun 09, 2011 at 03:28:09PM +0800, Li Dongyang wrote:
--- a/fs/btrfs/volumes.h
+++ b/fs/btrfs/volumes.h
@@ -45,6 +45,7 @@ struct btrfs_device {
int running_pending;
u64 generation;
+ int discard;
can you pick a better name? this does not describe that it's the
On Friday, June 10, 2011 08:00:17 AM David Sterba wrote:
On Thu, Jun 09, 2011 at 03:28:09PM +0800, Li Dongyang wrote:
--- a/fs/btrfs/volumes.h
+++ b/fs/btrfs/volumes.h
@@ -45,6 +45,7 @@ struct btrfs_device {
int running_pending;
u64 generation;
+ int discard;
can you