[Top] [All Lists]

Re: [PATCH] Add test 248: Check filesystem FITRIM implementation

To: xfs@xxxxxxxxxxx
Subject: Re: [PATCH] Add test 248: Check filesystem FITRIM implementation
From: Phil Karn <karn@xxxxxxxxxxxx>
Date: Tue, 21 Dec 2010 03:03:03 -0800
In-reply-to: <alpine.LFD.2.00.1012211132450.6010@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <1291996407-26251-1-git-send-email-lczerner@xxxxxxxxxx> <20101220174146.GA32680@xxxxxxxxxxxxx> <alpine.LFD.2.00.1012211132450.6010@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: karn@xxxxxxxx
What is the plan for TRIM support in XFS? I don't see any mention in the sources, so I guess the code you guys have been discussing must not be considered stable yet.

How will it eventually work? Will the filesystem automatically issue the commands to the drive whenever a file is deleted, or will it always require some sort of prodding from a userspace program?

And what kind of experiences are people having with XFS on current SSDs? I just put an Intel drive in my newly upgraded box and I'm wondering if this blazing performance will screech to a halt when my cumulative writes exceed its 120 GB capacity. Does anyone have a standalone "drive optimizer" that understands XFS, i.e, that can examine an unmounted file system and issue the appropriate TRIM commands for every block on the free list?

Or is the Intel drive somehow really good at avoiding write amplification even without TRIM help from the file system? I've heard that may be the case, but I don't understand how that can be.


<Prev in Thread] Current Thread [Next in Thread>