From: Eric Biggers <ebiggers@kernel.org>
To: Szabolcs Szakacsits <szaka@tuxera.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Theodore Ts'o <tytso@mit.edu>,
Matthew Wilcox <willy@infradead.org>,
"Leonidas P. Papadakos" <papadakospan@gmail.com>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
zajec5@gmail.com, "Darrick J. Wong" <djwong@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hans de Goede <hdegoede@redhat.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: NTFS testing (was: [GIT PULL] vboxsf fixes for 5.14-1
Date: Fri, 3 Sep 2021 10:48:18 -0700 [thread overview]
Message-ID: <YTJf4lBjnliqhI4D@sol.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.20.2109030047330.23375@tuxera.com>
On Fri, Sep 03, 2021 at 01:09:40AM +0300, Szabolcs Szakacsits wrote:
> User space drivers can have major disadvantages for certain workloads
> however how relevant are those for NTFS users? Most people use NTFS for
> file transfers in which case ntfs-3g read and write speed is about 15-20%
> less compared to ext4. For example in some quick tests ext4 read was
> 3.4 GB/s versus ntfs-3g 2.8 GB/s, and write was 1.3 GB/s versus 1.1 GB/s.
Your company's own advertising materials promoting your proprietary NTFS driver
(https://www.tuxera.com/products/tuxera-ntfs-embedded) claim that NTFS-3G is
much slower than ext4:
Read:
NTFS-3G: 63.4 MB/s
ext4: 113.8 MB/s
"Microsoft NTFS by Tuxera": 116 MB/s
Write:
NTFS-3G: 16.3 MB/s
ext4: 92.4 MB/s
"Microsoft NTFS by Tuxera": 113.3 MB/s
I'm not sure why anything you say should have any credibility when it
contradicts what your company says elsewhere, and your company has a vested
interest in not having proper NTFS support upstreamed to compete with their
proprietary driver. (Note that Tuxera doesn't provide much support for NTFS-3G;
most of their efforts are focused on their proprietary driver.)
- Eric
next prev parent reply other threads:[~2021-09-03 17:48 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 10:45 [GIT PULL] vboxsf fixes for 5.14-1 Hans de Goede
2021-07-13 19:15 ` Linus Torvalds
2021-07-13 20:14 ` Al Viro
2021-07-13 20:18 ` Al Viro
2021-07-13 20:24 ` Randy Dunlap
2021-07-13 20:32 ` Al Viro
2021-07-13 21:43 ` Randy Dunlap
2021-07-14 10:50 ` Rafał Miłecki
2021-07-14 14:13 ` Christoph Hellwig
2021-07-14 14:51 ` Greg KH
2021-07-14 15:59 ` Rafał Miłecki
2021-07-14 16:05 ` Matthew Wilcox
2021-07-14 16:18 ` Rafał Miłecki
2021-07-15 21:50 ` Neal Gompa
2021-07-16 11:46 ` Leonidas P. Papadakos
2021-07-16 18:07 ` Linus Torvalds
2021-07-30 15:55 ` Konstantin Komarov
2021-07-30 17:23 ` Paragon NTFSv3 (was Re: [GIT PULL] vboxsf fixes for 5.14-1) Linus Torvalds
2021-08-13 16:11 ` Konstantin Komarov
2021-08-15 20:32 ` Stephen Rothwell
2021-08-16 3:00 ` Kari Argillander
2021-09-02 21:55 ` Linus Torvalds
2021-08-03 22:48 ` [GIT PULL] vboxsf fixes for 5.14-1 Theodore Ts'o
2021-08-03 23:44 ` Matthew Wilcox
2021-08-04 0:04 ` Theodore Ts'o
2021-08-04 0:10 ` Linus Torvalds
2021-08-04 0:49 ` Theodore Ts'o
2021-08-04 1:03 ` Darrick J. Wong
2021-08-04 6:38 ` Kari Argillander
2021-08-04 16:30 ` Theodore Ts'o
2021-08-05 15:48 ` Konstantin Komarov
2021-08-10 7:02 ` Darrick J. Wong
2021-09-02 22:09 ` NTFS testing (was: " Szabolcs Szakacsits
2021-09-03 17:48 ` Eric Biggers [this message]
2021-09-03 21:17 ` Szabolcs Szakacsits
2021-07-17 16:47 ` Pali Rohár
2021-07-14 16:13 ` Darrick J. Wong
2021-07-14 16:18 ` Christoph Hellwig
2021-07-14 16:38 ` Gao Xiang
2021-07-14 20:03 ` Eric W. Biederman
2021-07-15 22:14 ` Darrick J. Wong
2021-07-13 19:17 ` pr-tracker-bot
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=YTJf4lBjnliqhI4D@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=djwong@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=papadakospan@gmail.com \
--cc=szaka@tuxera.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=zajec5@gmail.com \
/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).