All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher J. Morrone <morrone2@llnl.gov>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] lprocfs Helper Issues
Date: Fri, 02 Oct 2015 17:26:52 -0700	[thread overview]
Message-ID: <560F20CC.3020102@llnl.gov> (raw)
In-Reply-To: <1A2899D5-160B-4BC3-982D-DE6256F3D94B@intel.com>

On 09/30/2015 08:21 PM, Drokin, Oleg wrote:
>
> On Sep 30, 2015, at 8:32 PM, Christopher J. Morrone wrote:
>
>> On 09/30/2015 12:46 PM, Di Natale, Giuseppe wrote:
>>> I looked around to see where the helpers are used. It looks to me that they are always used in proc related functions. I agree with the issues you mentioned at the top of the email as well.
>>
>> Yes, but I meant to say we need to consider future use.  Largely motivated by the effort to upstream the Lustre client into Linux, the /proc interfaces are slowly going away.  So I was just suggesting that we should check that these functions will still be used by the new debugfs/sysfs/whatever interfaces in the future.  Nothing really needed to consider though; they are generic enough to still be used well into the future.
>
> The thing with the upstream kernel is that effectively procfs was split into two parts. The parts that are 1 value per file are in sysfs, the rest is in ldiskfs and resuses huge chunks
> of old code (including the functions mentioned).
> This is not to say we cannot replace them, of course.
> But upstream they want us to explore other avenues for many of our stuff too, like perf code for performance/usage gathering.
>
> Bye,
>      Oleg

Yes, and ultimately they might be opposed to even doing this much 
parsing of user strings in kernel space.  I can see an argument for sys 
files only taking simple integers, and leaving it to lustre libraries 
and command line tools to all niceties like specifying a number with units.

But in the sort term, cleaning up these functions is only a good thing, 
I think.

Chris

  reply	other threads:[~2015-10-03  0:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 20:08 [lustre-devel] lprocfs Helper Issues Di
2015-09-30  2:25 ` Christopher J. Morrone
2015-09-30 19:46   ` Di
2015-10-01  0:32     ` Christopher J. Morrone
2015-10-01  3:21       ` Drokin, Oleg
2015-10-03  0:26         ` Christopher J. Morrone [this message]
2015-10-03  0:29           ` Drokin, Oleg
2015-10-03  0:29       ` Christopher J. Morrone
2015-10-03  9:54         ` Dilger, Andreas
2015-10-05 21:52           ` Christopher J. Morrone
2015-10-05 22:47             ` Di
2015-10-06  4:23             ` Dilger, Andreas
2015-10-09 17:27               ` Di
2015-10-09 23:43                 ` Christopher J. Morrone
2015-10-09 18:38               ` Christopher J. Morrone
2015-09-30 20:06   ` Dilger, Andreas

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=560F20CC.3020102@llnl.gov \
    --to=morrone2@llnl.gov \
    --cc=lustre-devel@lists.lustre.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.