Re: [PATCH 2/4] xfs: improve handling of busy extents in the low-level allocator

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Feb 06, 2017 at 11:47:50AM -0500, Brian Foster wrote:
> That said, that limitation should be noted somewhere. Can we add a
> comment in xfs_extent_busy_clear() right above the hunk where we do the
> SKIP_DISCARD wake? E.g., something that points out the gen number for
> any particular extent could be bumped in such a situation.. (or
> something along those lines)?

I could add a comment, but given that the tree tracks busy extents
and is not in any way specific to discard I think it's more confusing
than not having it.
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux