From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 0/4] Finally remove userspace transaction support
Date: Wed, 10 Jan 2018 15:21:13 +0200 [thread overview]
Message-ID: <1515590477-22878-1-git-send-email-nborisov@suse.com> (raw)
Userspace transaction were initially added to he benefit of Ceph, however
in recent times it became clear that btrfs is not suitable for Ceph's workload
and has even been actively discoured. Additionaly, the userspace transaction
mechanism has always been a sort of a hack, which could easily lead to a
deadlock unless care is taken.
All things considered there is no point in keeping the code around. Userspace
transaction interface was deprecated in kernel version 4.14. Now it's time to
completely remove it in 4.17.
The first patch removes the ioctl-related code. Following patches just deal
with unused functions/values following ioctl removal.
Nikolay Borisov (4):
btrfs: Remove userspace transaction ioctls
btrfs: Remove code referencing unused TRANS_USERSPACE
btrfs: Remove transaction handle from btrfs_file_private
btrfs: Remove btrfs_fs_info::open_ioctl_trans
fs/btrfs/ctree.h | 2 --
fs/btrfs/extent-tree.c | 3 +-
fs/btrfs/file.c | 2 --
fs/btrfs/ioctl.c | 95 --------------------------------------------------
fs/btrfs/transaction.c | 36 +++++--------------
fs/btrfs/transaction.h | 5 +--
6 files changed, 11 insertions(+), 132 deletions(-)
--
2.7.4
next reply other threads:[~2018-01-10 13:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 13:21 Nikolay Borisov [this message]
2018-01-10 13:21 ` [PATCH 1/4] btrfs: Remove userspace transaction ioctls Nikolay Borisov
2018-01-10 13:37 ` [PATCH v2] " Nikolay Borisov
2018-01-10 13:40 ` [PATCH v3] " Nikolay Borisov
2018-01-10 13:21 ` [PATCH 2/4] btrfs: Remove code referencing unused TRANS_USERSPACE Nikolay Borisov
2018-01-10 13:21 ` [PATCH 3/4] btrfs: Remove transaction handle from btrfs_file_private Nikolay Borisov
2018-01-10 13:21 ` [PATCH 4/4] btrfs: Remove btrfs_fs_info::open_ioctl_trans Nikolay Borisov
2018-01-10 15:47 ` [PATCH 0/4] Finally remove userspace transaction support Josef Bacik
2018-01-10 16:26 ` David Sterba
2018-01-10 16:32 ` [PATCH RESEND 1/4] btrfs: Remove userspace transaction ioctls Nikolay Borisov
2018-01-10 16:32 ` [PATCH RESEND 2/4] btrfs: Remove code referencing unused TRANS_USERSPACE Nikolay Borisov
2018-02-02 17:40 ` David Sterba
2018-01-10 16:32 ` [PATCH RESEND 3/4] btrfs: Remove transaction handle from btrfs_file_private Nikolay Borisov
2018-02-02 17:40 ` David Sterba
2018-01-10 16:32 ` [PATCH RESEND 4/4] btrfs: Remove btrfs_fs_info::open_ioctl_trans Nikolay Borisov
2018-02-02 17:40 ` David Sterba
2018-02-02 17:39 ` [PATCH RESEND 1/4] btrfs: Remove userspace transaction ioctls David Sterba
2018-02-02 17:45 ` David Sterba
2018-02-05 8:41 ` [PATCH v2 " Nikolay Borisov
2018-02-05 8:41 ` [PATCH v2 2/4] btrfs: Remove btrfs_file_private::trans Nikolay Borisov
2018-02-05 8:41 ` [PATCH v2 3/4] btrfs: Remove code referencing unused TRANS_USERSPACE Nikolay Borisov
2018-02-05 8:41 ` [PATCH v2 4/4] btrfs: Remove btrfs_fs_info::open_ioctl_trans Nikolay Borisov
2018-02-05 8:52 ` [PATCH v2 1/4] btrfs: Remove userspace transaction ioctls Wang Shilong
2018-02-05 13:30 ` David Sterba
2018-02-05 14:27 ` Sage Weil
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=1515590477-22878-1-git-send-email-nborisov@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/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).