From: Matthew Wilcox <matthew@wil.cx>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>, linux-fsdevel@vger.kernel.org
Subject: Re: Getting a lot of fs-generated information to user space
Date: Fri, 12 Aug 2011 11:25:08 -0600 [thread overview]
Message-ID: <20110812172508.GB29309@parisc-linux.org> (raw)
In-Reply-To: <4E453BA5.4090403@jan-o-sch.net>
On Fri, Aug 12, 2011 at 04:41:41PM +0200, Jan Schmidt wrote:
> After thinking twice, this has a drawback: I'd have to track state
> between two read(2) calls, waiting for userspace to "pull" more data.
That should be OK. You've got filp->private_data to store your state in,
though you'll have to coordinate with btrfs' other use of ->private_data.
Not hard, just a little bit of work.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2011-08-12 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 12:14 Getting a lot of fs-generated information to user space Jan Schmidt
2011-08-12 12:31 ` Matthew Wilcox
2011-08-12 12:43 ` Jan Schmidt
2011-08-12 14:41 ` Jan Schmidt
2011-08-12 17:25 ` Matthew Wilcox [this message]
2011-08-14 2:43 ` Andi Kleen
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=20110812172508.GB29309@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.