From: Lukas Czerner <lczerner@redhat.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: Lukas Czerner <lczerner@redhat.com>,
linux-ext4@vger.kernel.org, jmoyer@redhat.com,
rwheeler@redhat.com, eshishki@redhat.com, sandeen@redhat.com,
jack@suse.cz, tytso@mit.edu
Subject: Re: [PATCH 1/3] Add ioctl FITRIM.
Date: Wed, 4 Aug 2010 17:13:01 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1008041704420.2932@localhost> (raw)
In-Reply-To: <8762zq8lxv.fsf@dmon-lap.sw.ru>
On Wed, 4 Aug 2010, Dmitry Monakhov wrote:
> Lukas Czerner <lczerner@redhat.com> writes:
>
> > Adds an filesystem independent ioctl to allow implementation of file
> > system batched discard support.
> >
> > Signed-off-by: Lukas Czerner <lczerner@redhat.com>
> > ---
> > fs/ioctl.c | 31 +++++++++++++++++++++++++++++++
> > include/linux/fs.h | 2 ++
> > 2 files changed, 33 insertions(+), 0 deletions(-)
> >
> > diff --git a/fs/ioctl.c b/fs/ioctl.c
> > index 2d140a7..6c01c3c 100644
> > --- a/fs/ioctl.c
> > +++ b/fs/ioctl.c
> > @@ -540,6 +540,33 @@ static int ioctl_fsthaw(struct file *filp)
> > return thaw_super(sb);
> > }
> >
> > +static int ioctl_fstrim(struct file *filp, unsigned long arg)
> BTW why do we have to trim fs in one shot ?
> IMHO it is much suitable to provide start,len parameters as we
> do in most functions(truncate, bdevdiscard, getdents).
> It allow userspace caller to implement a fancy looking progress bars.
Hi,
do you think it is really needed when even with todays SSD's it takes
just a couple of seconds ? And I suppose it will improve in future. But
generally I think we can do that..I would like to hear some more
opinions before I start looking at this.
Thanks.
-Lukas.
> > +{
> > + struct super_block *sb = filp->f_path.dentry->d_inode->i_sb;
> > + unsigned int minlen;
> > + int err;
> > +
> > + if (!capable(CAP_SYS_ADMIN))
> > + return -EPERM;
> > +
> > + /* If filesystem doesn't support trim feature, return. */
> > + if (sb->s_op->trim_fs == NULL)
> > + return -EOPNOTSUPP;
> > +
> > + /* If a blockdevice-backed filesystem isn't specified, return EINVAL. */
> > + if (sb->s_bdev == NULL)
> > + return -EINVAL;
> > +
> > + err = get_user(minlen, (unsigned int __user *) arg);
> > + if (err)
> > + return err;
> > +
> > + err = sb->s_op->trim_fs(minlen, sb);
> > + if (err)
> > + return err;
> > + return 0;
> > +}
> > +
> > /*
> > * When you add any new common ioctls to the switches above and below
> > * please update compat_sys_ioctl() too.
> > @@ -590,6 +617,10 @@ int do_vfs_ioctl(struct file *filp, unsigned int fd, unsigned int cmd,
> > error = ioctl_fsthaw(filp);
> > break;
> >
> > + case FITRIM:
> > + error = ioctl_fstrim(filp, arg);
> > + break;
> > +
> > case FS_IOC_FIEMAP:
> > return ioctl_fiemap(filp, arg);
> >
> > diff --git a/include/linux/fs.h b/include/linux/fs.h
> > index 68ca1b0..01632e4 100644
> > --- a/include/linux/fs.h
> > +++ b/include/linux/fs.h
> > @@ -315,6 +315,7 @@ struct inodes_stat_t {
> > #define FIGETBSZ _IO(0x00,2) /* get the block size used for bmap */
> > #define FIFREEZE _IOWR('X', 119, int) /* Freeze */
> > #define FITHAW _IOWR('X', 120, int) /* Thaw */
> > +#define FITRIM _IOWR('X', 121, int) /* Trim */
> >
> > #define FS_IOC_GETFLAGS _IOR('f', 1, long)
> > #define FS_IOC_SETFLAGS _IOW('f', 2, long)
> > @@ -1580,6 +1581,7 @@ struct super_operations {
> > ssize_t (*quota_write)(struct super_block *, int, const char *, size_t, loff_t);
> > #endif
> > int (*bdev_try_to_free_page)(struct super_block*, struct page*, gfp_t);
> > + int (*trim_fs) (unsigned int, struct super_block *);
> > };
> >
> > /*
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-08-04 15:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 13:44 [PATCH 1/3] Add ioctl FITRIM Lukas Czerner
2010-08-04 13:44 ` [PATCH 2/3] Add batched discard support for ext3 Lukas Czerner
2010-08-04 14:03 ` Jan Kara
2010-08-04 14:32 ` Lukas Czerner
2010-08-04 19:39 ` Andreas Dilger
2010-08-05 14:00 ` Lukas Czerner
2010-08-04 13:44 ` [PATCH 3/3] Add batched discard support for ext4 Lukas Czerner
2010-08-04 14:17 ` Jan Kara
2010-08-04 14:57 ` [PATCH 1/3] Add ioctl FITRIM Dmitry Monakhov
2010-08-04 15:13 ` Lukas Czerner [this message]
2010-08-04 15:26 ` Greg Freemyer
2010-08-05 0:28 ` Ted Ts'o
2010-08-05 6:51 ` Dmitry Monakhov
2010-08-05 15:47 ` Andreas Dilger
2010-08-05 7:00 ` Dmitry Monakhov
2010-08-05 8:36 ` Lukas Czerner
-- strict thread matches above, loose matches on Subject: below --
2010-09-24 15:35 [PATCH 0/3 v. 8] Ext3/Ext4 Batched discard support Lukas Czerner
2010-09-24 15:35 ` [PATCH 1/3] Add ioctl FITRIM Lukas Czerner
2010-09-24 17:03 ` Andreas Dilger
2010-09-27 9:20 ` Lukas Czerner
2010-08-10 14:19 [PATCH 0/3 ver. 7] Ext3/Ext4 Batched discard support Lukas Czerner
2010-08-10 14:19 ` [PATCH 1/3] Add ioctl FITRIM Lukas Czerner
2010-08-06 11:31 [PATCH 0/3] Batched discard support Lukas Czerner
2010-08-06 11:31 ` [PATCH 1/3] Add ioctl FITRIM Lukas Czerner
2010-07-27 12:41 [PATCH 0/3 v3] Batched discard support for Ext3/Ext4 Lukas Czerner
2010-07-27 12:41 ` [PATCH 1/3] Add ioctl FITRIM Lukas Czerner
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=alpine.LFD.2.00.1008041704420.2932@localhost \
--to=lczerner@redhat.com \
--cc=dmonakhov@openvz.org \
--cc=eshishki@redhat.com \
--cc=jack@suse.cz \
--cc=jmoyer@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=rwheeler@redhat.com \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).