public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Tom Zanussi <zanussi@us.ibm.com>
To: systemtap@sources.redhat.com
Subject: proposed relayfs changes and systemtap
Date: Tue, 21 Feb 2006 14:57:00 -0000	[thread overview]
Message-ID: <17403.14343.905016.261081@tut.ibm.com> (raw)

Hi,

Someone over the weekend posted a patch to remove the filesystem part
of relayfs and instead have applications' relayfs files live in other
filesytems instead:

http://marc.theaimsgroup.com/?l=linux-kernel&m=114036950922176&w=2

It looks like there's support for making this change (this idea has
come up multiple times before and I thought it made sense then too,
but it's never really gotten legs until now).

Anyway, in case anyone was worrying about how it would affect
systemtap, not much.  The poster of the patches has concentrated on
using sysfs to house relay files, but since systemtap already uses
/proc, it would seem to make sense for systemtap to move its relay
files there instead.

So, assuming we want move things over to procfs, the changes that
would need to be made for systemtap would be:

1) runtime/transport/relayfs.c - add file creation/removal relayfs
   callback handlers.  These will create/remove the proc files to
   represent the relayfs buffers.

2) runtime/transport/relayfs.c - change the relayfs_create_dir() and
   relayfs_remove_dir() calls to their procfs counterparts.

3) runtime/stpd/stpd.c - change "/mnt/relay" to "/proc" in main()

So that's it - the changes would be pretty minimal, and of course I'll
be happy to make them.

Tom


             reply	other threads:[~2006-02-21 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 14:57 Tom Zanussi [this message]
2006-02-21 15:06 ` Tom Zanussi
2006-03-16 15:16   ` William Cohen
2006-03-16 15:22     ` Tom Zanussi
2006-03-16 15:39       ` William Cohen

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=17403.14343.905016.261081@tut.ibm.com \
    --to=zanussi@us.ibm.com \
    --cc=systemtap@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).