linux-kernel - Re: introduce delayed-leds.h to reduce code duplication

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090311013906.GA8637@khazad-dum.debian.net>
Date:	Tue, 10 Mar 2009 22:39:06 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Pavel Machek <pavel@....cz>
Cc:	kernel list <linux-kernel@...r.kernel.org>, rpurdie@...ys.net
Subject: Re: introduce delayed-leds.h to reduce code duplication

On Sun, 08 Mar 2009, Pavel Machek wrote:
> On Tue 2009-01-20 10:04:00, Henrique de Moraes Holschuh wrote:
> > On Mon, 19 Jan 2009, Pavel Machek wrote:
> > > On Mon 2009-01-12 08:05:01, Henrique de Moraes Holschuh wrote:
> > > > On Sun, 11 Jan 2009, Pavel Machek wrote:
> > > > > What about something like this? 
> > > > > 
> > > > > [Alternatively, I can add a flag to the leds class, and make delayed
> > > > > leds a built-in functionality...]
> > > > > 
> > > > > [Attached is driver that uses new infrastructure for hp_accel, but it
> > > > > does a bit more.]
> > > > 
> > > > FWIW, I am looking over the thinkpad-acpi side of this.  I like the idea,
> > > > but I am not completely sure I agree fully with the changes to
> > > > thinkpad-acpi.
> > > > 
> > > > Which isn't a problem, as long as the thinkpad-acpi hunks are NOT merged to
> > > > any tree before my ACK, please.  I will test and comment on the patch before
> > > > the weekend.
> > > 
> > > Any news?
> > 
> > Sure.  Sorry for not replying earlier.
> > 
> > I don't like the loss of functionality of the private workqueue.  I kicked
> > the thinkpad led handling to a private workqueue in order to never tie up
> > the system-wide one with crap spinning around in the ACPI layer, etc.  In
> > fact, all thinkpad-acpi deferred work is in the private workqueue for this
> > reason.
> 
> Is the private workqueue really required? AFAICT workqueues are not
> exactly cheap, and leds are not toggled that often. Was it problem in
> practice?

Well, the day we can trust the main workqueue not to block or delay
important stuff, I will use it.  Until then, I feel it is best to have
thinkpad-acpi work scheduled independently from the important stuff.

The private workqueue is NOT used just for the LEDs, it is used for
every thinkpad-acpi deferred-work needs.  And I'd rather the thinkpad-acpi
LED work didn't move to the main workqueue.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/