linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jaya Kumar <jayakumar.lkml@gmail.com>
To: "Rick L. Vinyard, Jr." <rvinyard@cs.nmsu.edu>
Cc: linux-kernel@vger.kernel.org, npavel@ituner.com,
	tomi.valkeinen@nokia.com, tony@atomide.com,
	florianschandinat@gmx.de, krzysztof.h1@wp.pl,
	akpm@linux-foundation.org, linux-fbdev@vger.kernel.org,
	jkosina@suse.cz, bonbons@linux-vserver.org
Subject: Re: [PATCH] Add sysfs support for fbdefio delay
Date: Wed, 03 Mar 2010 00:11:23 +0000	[thread overview]
Message-ID: <45a44e481003021611g8572667yd5c135f3b3927fb3@mail.gmail.com> (raw)
In-Reply-To: <84774cde4a948cb726db3bfcb463a04c.squirrel@intranet.cs.nmsu.edu>

On Tue, Mar 2, 2010 at 11:36 PM, Rick L. Vinyard, Jr.
<rvinyard@cs.nmsu.edu> wrote:
>
> Jaya Kumar wrote:
>> On Tue, Mar 2, 2010 at 12:10 AM, Rick L. Vinyard, Jr.
>> <rvinyard@cs.nmsu.edu> wrote:
>>> Jaya Kumar wrote:
>>
>> Being concerned about CPU utilization is a good thing. But say for
>> example, your USB ethernet driver or USB audio driver is taking a lot
>> of cpu time packetizing traffic, then would I be correct that your
>> desire is to expose an inter-packetization driver specific sleep time
>> controllable by userspace via sysfs for all ethernet, audio, etc
>> drivers? (by driver specific, I mean the sysfs parameter would be
>> presented by all drivers but the value would be specific to each one,
>> which is the way your current patch would behave for all fb drivers).
>>
>
> I think the answer is yes, whether this were a fb, network, audio, etc. If
> there is a clearly defined parameter at which resource utilization can be
> adjusted in a standard way.

Hi Rick,

Sure, we can find these driver resource utilization choke points, and
maybe even make it sort of standard, but that does not mean that we
should expose all of this to userspace. Adding more userspace tunables
for each driver in order to effect fb, network, audio bus utilization,
is not appealing. So I think we disagree about the fundamentals.

My conclusion is: I'm opposed this patch, because it exposes the defio
delay parameter for _all_ fb drivers, _each_ through a
/sys/class/graphics/fb_driver_name/defio_delay sysfs entry and also
adds a min/max issue. The behaviour and system impact seen by
userspace when changing the parameter is not standard across the
typical range of systems and devices. More importantly, exposing each
driver's defio delay to userspace is not a good way to address the 2
underlying functional goals that were raised during this discussion:
1) being able to control a driver's bus/cpu utilization, and 2)
allowing certain plugins/etc to be able to increase display update
frequency for subregions of the display.

Just to be verbose, please don't let my rejection of this specific
patch affect your other patches as I see those as being very useful
and close to being suitable for merging.

Thanks,
jaya

  reply	other threads:[~2010-03-03  0:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 22:15 [PATCH] Add sysfs support for fbdefio delay Rick L. Vinyard Jr.
2010-02-25 22:32 ` Bruno Prémont
2010-02-25 22:41   ` Rick L. Vinyard, Jr.
2010-02-26  2:30 ` Jaya Kumar
2010-02-26 10:53   ` Bruno Prémont
2010-02-26 11:09     ` Jaya Kumar
2010-02-26 11:37       ` Bruno Prémont
2010-03-01 16:10   ` Rick L. Vinyard, Jr.
2010-03-02  6:49     ` Jaya Kumar
2010-03-02 15:36       ` Rick L. Vinyard, Jr.
2010-03-03  0:11         ` Jaya Kumar [this message]
2010-04-13 15:50           ` Rick L. Vinyard, Jr.
2010-03-02 18:47 ` Rick L. Vinyard Jr.
2010-03-03  0:19   ` Andrew Morton

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=45a44e481003021611g8572667yd5c135f3b3927fb3@mail.gmail.com \
    --to=jayakumar.lkml@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bonbons@linux-vserver.org \
    --cc=florianschandinat@gmx.de \
    --cc=jkosina@suse.cz \
    --cc=krzysztof.h1@wp.pl \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npavel@ituner.com \
    --cc=rvinyard@cs.nmsu.edu \
    --cc=tomi.valkeinen@nokia.com \
    --cc=tony@atomide.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 NNTP newsgroup(s).