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 06:31:55 -0600 [thread overview]
Message-ID: <20110812123154.GA29309@parisc-linux.org> (raw)
In-Reply-To: <4E451917.6080306@jan-o-sch.net>
On Fri, Aug 12, 2011 at 02:14:15PM +0200, Jan Schmidt wrote:
> (1) Normally, requests to the file system go through ioctls (on the fd
> of the mountpoint) and the result is small enough to be returned when
> the ioctl finishes. That said, I thought of passing a user land fd along
> with this ioctl to the kernel and make it dump the generated bits there.
> Only, I don't see how to turn a fd into a struct file pointer. And I
> don't know if that would be considered really ugly by a lot of people.
struct file *filp = fget(fd);
...
fput(filp);
That said, why not have the ioctl mutate the existing fd?
ie in userspace:
int fd = open("/mnt/btrfs");
ioctl(fd, BTRFS_IOC_STREAM);
while (...) {
read(fd, buf, 4096);
...
}
close(fd);
--
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 12:31 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 [this message]
2011-08-12 12:43 ` Jan Schmidt
2011-08-12 14:41 ` Jan Schmidt
2011-08-12 17:25 ` Matthew Wilcox
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=20110812123154.GA29309@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.