From: Al Viro <viro@ZenIV.linux.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: optimize inline symlink handling
Date: Sun, 3 May 2015 10:18:29 +0100 [thread overview]
Message-ID: <20150503091829.GR889@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1430644433-26658-1-git-send-email-hch@lst.de>
On Sun, May 03, 2015 at 11:13:48AM +0200, Christoph Hellwig wrote:
> This series allows XFS to return a pointer to the inline symlink
> inside to the VFS instead of needing a kmalloc'ed copy.
Take a look at vfs.git#link_path_walk...
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-05-03 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 9:13 optimize inline symlink handling Christoph Hellwig
2015-05-03 9:13 ` [PATCH 2/5] xfs: factor out a helper to initialize a local format inode fork Christoph Hellwig
2015-05-03 9:13 ` [PATCH 3/5] xfs: set up inode operation vectors later Christoph Hellwig
2015-05-03 9:13 ` [PATCH 4/5] xfs: use ->readlink to implement the readlink_by_handle ioctl Christoph Hellwig
2015-05-03 9:13 ` [PATCH 5/5] xfs: optimize inline symlinks Christoph Hellwig
2015-05-03 9:18 ` Al Viro [this message]
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=20150503091829.GR889@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hch@lst.de \
--cc=xfs@oss.sgi.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