All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] Moving lustre procfs stuff to sysfs & questions.
Date: Sun, 03 May 2015 18:15:33 +0000	[thread overview]
Message-ID: <20150503181533.GD24370@kroah.com> (raw)
In-Reply-To: <1430622608-30402-1-git-send-email-green@linuxhacker.ru>

On Sat, May 02, 2015 at 11:10:05PM -0400, green@linuxhacker.ru wrote:
> From: Oleg Drokin <green@linuxhacker.ru>
> 
> Greg, I wonder if you can take at least a brief look and tell me if this
> is the direction you were envisioning wrt this particular cleanup.
> 
> It's not all-inclusive, but I have a long flight tomorrow so
> if the direction is right, I can convert more of this stuff.
> 
> This does not touch some of the multi-value stuff that would probably
> need to move to debugfs or other places, that would be a next step.
> 
> Additionally some questions:
> I know sysfs is supposedly 1 file 1 value, though I see some exceptions, e.g.:
> # cat /sys/kernel/vmcoreinfo 
> 2b57500 1024
> 
> So we have this /proc/fs/lustre/devices that prints status of all
> "lustre internal devices (or obd for short)" like this:
> # cat /proc/fs/lustre/devices 
>   0 UP mgc MGC192.168.10.226@tcp d6815182-b36d-c4ba-6aa6-065aeb9e9769 5
>   1 UP lov lustre-clilov-ffff8800bd617800 32be3f55-891e-ed82-cae9-6add0770d503 4
> ...
> 
> Obviously I cannot retain it as a single file, but do I really need to
> create a tree that would look like:
> /sys/fs/lustre/obd/[1...]/{status,name,type,uuid,refcount}
> (or possibly even /sys/devices/virtual/lustre_obd/... )
> or can I get away with just
> /sys/fs/lustre/obd/[1...] files where there's one line per obd like:
>   0 UP mgc MGC192.168.10.226@tcp d6815182-b36d-c4ba-6aa6-065aeb9e9769 5
> (frankly, I have not figured out yet how to dynamically add files
> to sysfs dir).

Either make a tree of kobjects, or individual files, but not one big
file, that's not acceptable for sysfs, sorry.

> What about /proc/sys stuff - /proc/sys/lustre and /proc/sys/lnet?
> Hopefully it's ok to leave those where they are?

Nope, please remove.  If you aren't a process value, you can't add new
proc files.

> Also I found that cgroup does calls into kernfs directly, gaining
> ability to register seq_file files and otherwise do all sorts of
> stuff that would be cool to do from lustre too ;)

If you want to make lustrefs, be my guest, you can do whatever you want
in that, using kernfs, but that's not ok for sysfs, sorry.

thanks,

greg k-h

  reply	other threads:[~2015-05-03 18:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-03  3:10 [RFC PATCH 0/3] Moving lustre procfs stuff to sysfs & questions green
2015-05-03 18:15 ` Greg Kroah-Hartman [this message]
2015-05-03 19:43 ` Oleg Drokin

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=20150503181533.GD24370@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    /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.