From: Tom Zanussi <zanussi@us.ibm.com>
To: Nathan Scott <nathans@sgi.com>
Cc: Tom Zanussi <zanussi@us.ibm.com>, Jens Axboe <axboe@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blk queue io tracing support
Date: Tue, 30 Aug 2005 23:55:45 -0500 [thread overview]
Message-ID: <17173.14417.324497.140819@tut.ibm.com> (raw)
In-Reply-To: <20050831143309.A4434621@wobbly.melbourne.sgi.com>
Nathan Scott writes:
> Hi Tom,
>
> On Tue, Aug 30, 2005 at 11:19:04PM -0500, Tom Zanussi wrote:
> > You're right, it should be using simple_rmdir rather than
> > simple_unlink for removing directories. Thanks for sending the patch,
>
> No problem.
>
> > which I've modified a bit to avoid splitting the rmdir/unlink cases
> > into separate functions, since they're almost the same except for what
> > they end up calling. relayfs_remove_dir now doesn't do anything but
> > call relayfs_remove (it didn't do much more than that before anyway),
> > but it makes sense to me to keep it, as the counterpart to
> > relayfs_create_dir. Let me know if you see any problems with it.
>
> Looks OK, I'll give it a spin.
>
> On an unrelated note, are there any known issues with using epoll
> on relayfs file descriptors? I'm having a few troubles, and just
> wondering if its me doing something silly, or if its known to not
> work...? Symptoms of the problem are epoll continually reaching
> its timeout with no modified fds found (when I know the inode has
> modified trace buffers attached) ... and the epoll code is a bit
> too hairy for me to go find a quick fix - seems like it should be
> able to work though since relayfs has a ->poll implementation.
Well, the relayfs poll implementation is based on completed
sub-buffers, so you can be writing events into a buffer, but until a
buffer switch happens, you won't be notified that anything's changed.
The reason for the sub-buffer granularity is that relayfs was
originally meant for use only with mmap(), but now that there's a
read(), I'll probably have to make some changes to the poll
implementation as well.
Tom
next prev parent reply other threads:[~2005-08-31 4:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 12:32 Jens Axboe
2005-08-24 1:03 ` Nathan Scott
2005-08-24 7:08 ` Jens Axboe
2005-08-24 7:19 ` Nathan Scott
2005-08-24 7:25 ` Jens Axboe
2005-08-24 9:28 ` Jens Axboe
2005-08-29 4:53 ` Nathan Scott
2005-08-29 5:57 ` Jens Axboe
2005-08-30 23:43 ` Nathan Scott
2005-08-31 7:31 ` Jens Axboe
2005-08-30 23:48 ` Nathan Scott
2005-08-30 23:58 ` Nathan Scott
2005-08-31 4:19 ` Tom Zanussi
2005-08-31 4:33 ` Nathan Scott
2005-08-31 4:53 ` Nathan Scott
2005-08-31 4:55 ` Tom Zanussi [this message]
2005-08-31 7:33 ` Jens Axboe
2005-09-02 11:20 ` Jens Axboe
2005-08-24 6:24 ` Nathan Scott
2005-08-24 7:08 ` Jens Axboe
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=17173.14417.324497.140819@tut.ibm.com \
--to=zanussi@us.ibm.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@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
all inboxes | Powered by JetHome®