[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <C97001BC43954D438ACB059713BA5CDFA47DDAD93D@USEA-EXCH7.na.uis.unisys.com>
Date: Mon, 19 May 2014 09:42:22 -0500
From: "Romer, Benjamin M" <Benjamin.Romer@...sys.com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: *S-Par-Maintainer <SParMaintainer@...sys.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jkc@...hat.com" <jkc@...hat.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>
Subject: Re: [PATCH 2/7] staging: unisys: move uislib/platform proc entry to
debugfs
On Sun, 2014-05-18 at 09:49 -0700, Greg KH wrote:
> There's no need to keep this dentry around, you can just remove all the
> debugfs files in your directory recursively when you exit. That will
> save you code and logic overall.
Ah, thanks! I wasn't aware that I could do that. That's an easy fix. :)
> I'll leave this for now, you can clean that up in a future patch.
Thanks! I'll do that. :)
> Also, why are these entries moving to debugfs at all? Why are they
> needed? Who will use them? Are tools relying on them to be there?
The tuning entries are sometimes used to help adjust the behavior of our
IO service partitions for better performance. I'm not sure about the
platform entry, but I'll find out if anyone still uses it. If not, I'll
send another patch to remove it entirely.
> thanks,
>
> greg k-h
--
Ben Romer | Software Engineer |
Virtual Systems Development
Unisys Corporation | 2476
Swedesford Rd | Malvern, PA 19355
| 610-648-7140
Powered by blists - more mailing lists