Date: Wed, 6 Jun 2007 11:03:28 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Roman Divacky <rdivacky@freebsd.org> Cc: Eric Lemar <eric.lemar@isilon.com>, arch@freebsd.org Subject: Re: *at family of syscalls in FreeBSD Message-ID: <20070606080328.GZ2268@deviant.kiev.zoral.com.ua> In-Reply-To: <20070606074429.GA42032@freebsd.org> References: <20070604162430.GA76813@freebsd.org> <896DB1FBFFD5A145833D9DA08CA12A85051A7F@seaxch07.desktop.isilon.com> <20070606074429.GA42032@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--8f0Rp8CLSOFvlIcd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 06, 2007 at 09:44:29AM +0200, Roman Divacky wrote: > On Tue, Jun 05, 2007 at 06:17:40PM -0700, Eric Lemar wrote: > > I'm definitely a fan of this API. Aside from the general thread-related > > utility of this API, it provides a reasonable API for accessing > > windows-style ADS streams (subfiles) on a filesystem that supports them > > and is becoming reasonably cross-platform. This lets you handle things > > like ADS hanging off directories in a comparatively sane manner. > >=20 > > We've actually implemented a subset of these syscalls in-house (Isilon) > > for use with our filesystem, largely for the ADS-related functionality. > > Generally speaking, in our tree most of the traditional non-'at' syscal= ls > > are just small kernel wrappers around the 'at' interfaces. Overall ends > > up looking fairly clean and we've ended up using them even in places > > where we don't need the ADS functionality just because they are so > > convenient. > >=20 > > If you're interested in implementing this API I'd be happy to talk about > > our implementation and see whether the relevant parts of our implementa= tion > > would be useful for the general community. >=20 > my current patch is at: www.vlakno.cz/~rdivacky/linux_at.patch >=20 > it does not implement the native fbsd syscalls, only the linuxulator ones > but adding those is a matter of minutes. I asked for a review by pjd and/= or > rwatson and hopefully this will get commited soon.. I think it would be very useful to look at Isilon implementation, and possi= bly merge your and their patch. In particular, it could give an insight of what real uses for the API/KPI are. --8f0Rp8CLSOFvlIcd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGZmpQC3+MBN1Mb4gRAr7vAJ9uMZ8xkaYgtGoSUb0s/nZ/e2N3sgCcCBsD Pv+Ch7hZhNSLbIArrYrPFZM= =YU8C -----END PGP SIGNATURE----- --8f0Rp8CLSOFvlIcd--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070606080328.GZ2268>