From: Anton Altaparmakov <aia21@cam.ac.uk>
To: tridge@samba.org
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: performance of filesystem xattrs with Samba4
Date: Fri, 19 Nov 2004 12:03:53 +0000 [thread overview]
Message-ID: <1100865833.6443.17.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <16797.41728.984065.479474@samba.org>
On Fri, 2004-11-19 at 18:38 +1100, tridge@samba.org wrote:
> I've been developing the posix backend for Samba4 over the last few
> months. It has now reached the stage where it is passing most of the
> test suites, so its time to start some performance testing.
>
> The biggest change from the kernels point of view is that Samba4 makes
> extensive use of filesystem xattrs. Almost every file with have a
> user.DosAttrib xattr containing file attributes and additional
> timestamp fields. A lot of files will also have a system.NTACL
> attribute containing a NT ACL, and many files will have a
> user.DosStreams xattr for NT alternate data streams. Some rare files
> will have a user.DosEAs xattr for DOS extended attribute
> support. Files with streams will also have separate xattrs for each NT
> stream.
[snip]
> Soon we'll be starting to integrate the xattr support with a LSM
> module, to allow the kernel to interpret the NT ACLs directly to avoid
> races, make things a little more efficient (using a xattr cache
> holding unpacked ACLs), and allowing for the possibility of non-Samba
> file access to obey the NT ACLs.
Note, that NTFS supports all those things natively on the file system,
so it may be worth keeping in mind when designing your APIs. It would
be nice if one day when ntfs write support is finished, when running
Samba on an NTFS partition on Linux, Samba can directly access all those
things directly from NTFS. I guess a good way would be if your
interface is sufficiently abstracted so that it can use xattrs as a
backend or a native backend which NTFS could provide for you or Samba
could provide for NTFS. For example NTFS stores the 4 different times
in NT format in each inode (base Mft record) so you would not have to
take an xattr performance hit there.
Anyway, just thought I would mention this, I am not expecting you to do
anything about it, especially since full NTFS read-write support is
still a long way away...
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/, http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2004-11-19 12:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16759.16648.459393.752417@samba.org>
2004-10-21 18:32 ` [PATCH] Re: idr in Samba4 Jim Houston
2004-10-22 6:17 ` tridge
2004-11-19 7:38 ` performance of filesystem xattrs with Samba4 tridge
2004-11-19 8:08 ` James Morris
2004-11-19 10:16 ` Andreas Dilger
2004-11-19 11:43 ` tridge
2004-11-19 22:28 ` Andreas Dilger
2004-11-22 13:02 ` tridge
2004-11-22 21:40 ` Andreas Dilger
2004-11-19 12:03 ` Anton Altaparmakov [this message]
2004-11-19 12:43 ` tridge
2004-11-19 14:11 ` Anton Altaparmakov
2004-11-20 10:44 ` tridge
2004-11-20 16:20 ` Hans Reiser
2004-11-20 23:29 ` tridge
2004-11-19 15:34 ` Hans Reiser
2004-11-19 15:58 ` Jan Engelhardt
2004-11-19 22:03 ` tridge
2004-11-20 4:51 ` Hans Reiser
2004-11-19 23:01 ` tridge
2004-11-20 0:26 ` Andrew Morton
2004-11-21 1:14 ` tridge
2004-11-21 2:12 ` tridge
2004-11-21 23:53 ` tridge
2004-11-23 9:37 ` tridge
2004-11-23 17:55 ` Andreas Dilger
2004-11-24 7:53 ` tridge
2004-11-20 4:40 ` Hans Reiser
2004-11-20 6:47 ` tridge
2004-11-20 16:13 ` Hans Reiser
2004-11-20 23:16 ` tridge
2004-11-21 2:36 ` Hans Reiser
2004-11-21 0:21 ` tridge
2004-11-21 2:41 ` Hans Reiser
2004-11-21 1:53 ` tridge
2004-11-21 2:48 ` Hans Reiser
2004-11-21 3:19 ` tridge
2004-11-21 6:11 ` Hans Reiser
2004-11-21 22:21 ` Nathan Scott
2004-11-21 23:43 ` tridge
2004-12-03 17:49 Steve French
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=1100865833.6443.17.camel@imp.csi.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tridge@samba.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
all inboxes | Powered by JetHome®