From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boaz Harrosh Subject: Re: size limit of extended attributes Date: Thu, 30 Apr 2015 17:46:16 +0300 Message-ID: <55424038.7000109@plexistor.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Linux FS-devel Mailing List To: =?UTF-8?B?QmrDtnJuIEpBQ0tF?= , Trond Myklebust Return-path: Received: from mail-wi0-f171.google.com ([209.85.212.171]:38433 "EHLO mail-wi0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751535AbbD3OqU (ORCPT ); Thu, 30 Apr 2015 10:46:20 -0400 Received: by wiun10 with SMTP id n10so20751227wiu.1 for ; Thu, 30 Apr 2015 07:46:18 -0700 (PDT) In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On 04/30/2015 04:57 PM, Bj=C3=B6rn JACKE wrote: >=20 > Can we get rid of the 64k size limit for EAs? The API on AIX is the s= ame as on > Linux. But there is a huge size limit - which would help us already = a lot. >=20 If memory serves me correctly the xattr is always written in one shot from offset0..xattr_size. At least it is so on the VFS API side. That said I think there are also two mem-copies on the way to the FS from the user buffer. How will you reliably write something bigger than CONST-X in one call? On all arches. Same goes for read. > Bj=C3=B6rn >=20 The hacks need not be so ugly and they can be well documented and pobli= shed as a public STD. ./foo-with-streams (With xatters info) ./.foo-with-streams.__STREAMES__/ (backpointer xattrs-info) ./.foo-with-streams.__STREAMES__/SA ./.foo-with-streams.__STREAMES__/SB ... And some special mod bits on the .foo-with-streams.__STREAMES__ direc= tory The smb read-dir parser removes those hidden directories Cheers Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html