linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <boaz@plexistor.com>
To: "Björn JACKE" <bj@sernet.de>,
	"Trond Myklebust" <trond.myklebust@primarydata.com>
Cc: Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>
Subject: Re: size limit of extended attributes
Date: Thu, 30 Apr 2015 17:46:16 +0300	[thread overview]
Message-ID: <55424038.7000109@plexistor.com> (raw)
In-Reply-To: <E1Ynoyu-001UTN-EI@intern.SerNet.DE>

On 04/30/2015 04:57 PM, Björn JACKE wrote:
> 
> Can we get rid of the 64k size limit for EAs? The API on AIX is the same as on
> Linux.  But there is a huge size limit - which would help us already a lot.
> 

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örn
> 

The hacks need not be so ugly and they can be well documented and poblished
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__ directory

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

  parent reply	other threads:[~2015-04-30 14:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 11:33 size limit of extended attributes Björn JACKE
2015-04-30 12:38 ` Trond Myklebust
2015-04-30 13:57   ` Björn JACKE
2015-04-30 14:35     ` Theodore Ts'o
2015-04-30 14:46     ` Boaz Harrosh [this message]
2015-04-30 16:06       ` Björn JACKE
2015-04-30 16:56         ` Boaz Harrosh
2015-05-05 13:34           ` Björn JACKE
2015-05-01 15:43     ` Dave Chinner
2015-05-05 13:38       ` Björn JACKE
2015-05-05 15:43         ` Jan Kara
2015-05-06  1:31           ` Dave Chinner

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=55424038.7000109@plexistor.com \
    --to=boaz@plexistor.com \
    --cc=bj@sernet.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=trond.myklebust@primarydata.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).