From: Robert White <rwhite@pobox.com>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Austin S Hemmelgarn <ahferroin7@gmail.com>,
Richard Sharpe <realrichardsharpe@gmail.com>,
Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Can BTRFS handle XATTRs larger than 4K?
Date: Mon, 22 Dec 2014 15:55:39 -0800 [thread overview]
Message-ID: <5498AF7B.2020002@pobox.com> (raw)
In-Reply-To: <CAN05THTqyoVK6sH2JR9CTE77eHu_-um963r4M6jXJEUSWk7DJA@mail.gmail.com>
So I'll ask again...
On 12/22/2014 03:15 PM, ronnie sahlberg wrote:
>On Mon, Dec 22, 2014 at 2:52 PM, Robert White <rwhite@pobox.com> wrote:
>> So skipping the full ADS, what's the current demand/payoff for large XATTR
>> space?
^^^^^^^^^^^^
So skipping the full ADS, what is the current demand/payoff for large
XATTR space?
next prev parent reply other threads:[~2014-12-22 23:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 2:07 Can BTRFS handle XATTRs larger than 4K? Richard Sharpe
2014-12-20 8:38 ` Chris Murphy
2014-12-22 11:38 ` Chris Samuel
2014-12-22 11:41 ` Chris Samuel
2014-12-22 14:28 ` Austin S Hemmelgarn
2014-12-22 17:27 ` Richard Sharpe
2014-12-22 18:09 ` Austin S Hemmelgarn
2014-12-22 18:43 ` Chris Murphy
2014-12-22 19:56 ` Austin S Hemmelgarn
2014-12-22 20:06 ` Richard Sharpe
2014-12-22 20:44 ` Austin S Hemmelgarn
2014-12-22 20:50 ` Richard Sharpe
2014-12-22 22:52 ` Robert White
2014-12-22 22:55 ` Richard Sharpe
2014-12-23 0:08 ` Robert White
2014-12-23 1:16 ` Richard Sharpe
2014-12-23 12:37 ` Austin S Hemmelgarn
2014-12-22 23:15 ` ronnie sahlberg
2014-12-22 23:55 ` Robert White [this message]
2014-12-22 23:58 ` Richard Sharpe
2014-12-23 0:11 ` Robert White
2014-12-22 20:04 ` Richard Sharpe
2014-12-22 20:33 ` Austin S Hemmelgarn
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=5498AF7B.2020002@pobox.com \
--to=rwhite@pobox.com \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=realrichardsharpe@gmail.com \
--cc=ronniesahlberg@gmail.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).