From owner-freebsd-current@FreeBSD.ORG Wed Jul 25 19:46:41 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8BC59106564A; Wed, 25 Jul 2012 19:46:41 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id E4C818FC08; Wed, 25 Jul 2012 19:46:40 +0000 (UTC) Received: by ggnm2 with SMTP id m2so1369831ggn.13 for ; Wed, 25 Jul 2012 12:46:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Wf7PRUOHt/8ame6wHLMaNPcvriEO8/ssoQq6dLt0ko8=; b=Iekdb2Sk1iaLKaBGTqQ94yEeFjwwyQROs3+QaDsc+DmetIc7LObh3t5gjliydBp5+h Go60BRjEidRS7uFiY+ofA7Te5ZeYLQ2KAgsOkPjMQKC9IyuMBnFEelny7aOUjIcJTFIk 0Q7SUUOotnQDd0frqZv9xOIq54yGDWyfE3eOzBFS8NMZ1ApgJ7y9qoDLQQcc/eL4y5AJ Bdm846wLvmSt4M0xlkoBB16mX3w6q9IILRkyQJwX8WeNAitc3Wufm21CPfkCBTRd2Tdw sTM4AgihVx1Z/V7SRdCLDCoD3jo7PcGJPXq75he5oKmdJLb1fE4xG7gWTqbCdrraFkOw 5qug== MIME-Version: 1.0 Received: by 10.60.24.7 with SMTP id q7mr37413149oef.54.1343245600047; Wed, 25 Jul 2012 12:46:40 -0700 (PDT) Received: by 10.76.84.7 with HTTP; Wed, 25 Jul 2012 12:46:39 -0700 (PDT) In-Reply-To: References: <50064FB2.3020409@entel.upc.edu> Date: Wed, 25 Jul 2012 12:46:39 -0700 Message-ID: From: Garrett Cooper To: attilio@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD FS , =?ISO-8859-1?Q?Gustau_P=E9rez_i_Querol?= , Peter Holm , Antony Mawer , George Neville-Neil , freebsd-current@freebsd.org Subject: Re: MPSAFE VFS -- List of upcoming actions X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jul 2012 19:46:41 -0000 On Wed, Jul 25, 2012 at 10:04 AM, Attilio Rao wrote: > On 7/21/12, Antony Mawer wrote: >> On Wed, Jul 18, 2012 at 6:45 PM, Attilio Rao wrote= : >>> 2012/7/18, Gustau P=E9rez i Querol : >>>> >>>> Sorry fo the delay. >>>> >>>> About the ntfs support, I'd go with fuse and leave the most releva= nt >>>> filesystems in kernel space. In fact filesystems not particulary >>>> specific and not tied our kernel would go to userspace; thinks like >>>> smbfs, nwfs, ntfs, ext2 o ext4 for example should be in userspace (the >>>> list is incomplete and I don't really know if all of them are yet >>>> implemenent in userspace) in my opinion. That would make them easier t= o >>>> maintain (changes in the kernel would only affect fuse, once fixed all >>>> the userspace filesystem would work again). >>>> >>>> As a bonus, we would get many working fs based on fuse. In the >>>> server side gluster is a desirable thing; in the desktop things like >>>> gvfs (in the linux world gvfs is used not only by gnome but also by kd= e >>>> or xfce) or truecrypt >>> >>> I'm really concerned also about ntfs and smbfs at the moment. It seems >>> that there is also a FUSE smbfs port, but I never used it and I'm not >>> sure about its state at all. >> >> From what I understand, Apple have done a considerable amount of work >> on the FreeBSD-drived smbfs in the latest versions of OS X, based on >> the existing smbfs in tree: > > I've also found that there are 2 FUSE modules for smbfs but pho@ and > flo@ still haven't tested them. It may make sense to do so before we > commit FUSE to -CURRENT. However, thee is a plan by a $COMPANY to work > on the in-kernel version of smbfs and lock it before 10.0 is shipped. > In the unlikely events this doesn't happen we will came up with a > different plan (assuming we will adopt anyway the FUSE module, if it > proves to work well). > >> http://www.opensource.apple.com/source/smb/smb-552.5/ >> >> I imagine things like the filesystem locking are probably somewhat >> different, but in terms of updating smbfs itself to support newer >> features it may be a good base (licensing permitting). smbfs at the >> moment lacks in some areas such as DFS support, although I do not know >> if the OS X version is any different there (given the consumer focus >> of their OS, probably not). There was also a version spun off by >> OpenSolaris: >> >> http://hub.opensolaris.org/bin/view/Project+smbfs/ >> >> which again was based on the FreeBSD + Apple versions. >> >> I also have a vested interest in NWFS continuing to work - only from a >> legacy point of view where we still interoperate with a number of >> Netware 6 servers through this. While those will likely eventually go >> away, more than likely before we move to 10.x, if there is anyone >> capable of working on it we could supply a test environment. >> Unfortunately the actual locking of the NWFS and NCP modules is >> outside my sphere of knowledge... > > If you have NCP, do you think you can try this netncp I never > committed because lack of testing?: > http://lists.freebsd.org/pipermail/freebsd-fs/2009-January/005617.html > > IIRC, Apple does a similar thing for netsmb (which suffers from a > similar problem as netncp). > Do you know if FUSE can support NWFS in any way? > > Starting providing stress-tests on the current codebase for > NWFS/NetNCP (and report bugs found, preparing a list) could be a good > way to start the locking effort. Interested developers then can look > into such a list and provide necessary insight. 1. The in-kernel smbfs is so far behind the SMB spec that I'm not sure that it's worthwhile maintaining it. It's SMB1.x based, which is pre-Vista; SMB2.1 has been out for a while and 3.0 is rolling around the corner in the next couple years (about the same time Windows XP is going to be EOS). 2. According to reports I have from internal sources, the Apple implementation is suboptimal from a performance perspective, in part because the Apple SMB client doesn't coalesce requests. I concur on the poor performance based on personal experience because NFS beats SMB hands down on OSX (comes close to saturating the physical media with NFS, and putters along at a fraction of the link speed with CIFS on my Macbook Pro with Lion), whereas running a Windows 7 client against samba36 yields performance I would expect (saturates gigabit). YMMV, -Garrett 1. http://windows.microsoft.com/en-us/windows/products/lifecycle