linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* led block trigger patch
@ 2020-07-28 18:47 truart
  2020-08-05 21:57 ` Pavel Machek
       [not found] ` <50db75e2-d53c-ce8b-bd00-1099be0e2e74@ifi.lmu.de>
  0 siblings, 2 replies; 5+ messages in thread
From: truart @ 2020-07-28 18:47 UTC (permalink / raw)
  To: linux-leds

Hej hej,

I already asked on the linux-block list, but that was likely the wrong place, so I try here.

All our new thinkpads are missing a hard disk led, and when trying to use some keyboard led it turned out that this is not really working. The LED is either just blinking or showing nothing. When googling we found https://www.spinics.net/lists/linux-scsi/msg132286.html
All the laptops have nvme disks, so this is exactly what we need. But it seems to be missing in the latest kernel.

So may I ask what happened to this patch? Is it scheduled for being added? It's definitely needed as every new notebook I'm aware of doesn't have hard disk leds while nvme disks are default for most new notebooks now. So linux should be able to show disk traffic not only for ide and sata but also for up-to-date disk technologies. Any chance we get that patch? Is there a place to vote for a patch?

Thanks!
Michael

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: led block trigger patch
  2020-07-28 18:47 led block trigger patch truart
@ 2020-08-05 21:57 ` Pavel Machek
       [not found] ` <50db75e2-d53c-ce8b-bd00-1099be0e2e74@ifi.lmu.de>
  1 sibling, 0 replies; 5+ messages in thread
From: Pavel Machek @ 2020-08-05 21:57 UTC (permalink / raw)
  To: truart; +Cc: linux-leds

[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]

On Tue 2020-07-28 20:47:32, truart@gmx.de wrote:
> Hej hej,
> 
> I already asked on the linux-block list, but that was likely the wrong place, so I try here.
> 
> All our new thinkpads are missing a hard disk led, and when trying to use some keyboard led it turned out that this is not really working. The LED is either just blinking or showing nothing. When googling we found https://www.spinics.net/lists/linux-scsi/msg132286.html
> All the laptops have nvme disks, so this is exactly what we need. But it seems to be missing in the latest kernel.
>

> So may I ask what happened to this patch? Is it scheduled for being added? It's definitely needed as every new notebook I'm aware of doesn't have hard disk leds while nvme disks are default for most new notebooks now. So linux should be able to show disk traffic not only for ide and sata but also for up-to-date disk technologies. Any chance we get that patch? Is there a place to vote for a patch?
> 

Not scheduled. And we don't do voting.

Find out what is wrong with the patch, fix it, resubmit it.

Oh. It appears to register trigger per block device. That's no-no.

Are you willing to seriously work on that?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: led block trigger patch
       [not found] ` <50db75e2-d53c-ce8b-bd00-1099be0e2e74@ifi.lmu.de>
@ 2020-08-10  6:48   ` truart
  2020-08-10  7:33     ` Pavel Machek
  0 siblings, 1 reply; 5+ messages in thread
From: truart @ 2020-08-10  6:48 UTC (permalink / raw)
  To: linux-leds

Pavel Machek wrote:

> Find out what is wrong with the patch, fix it, resubmit it.

I would like to, but unfortunately, I've no skills in programming so I'm not able to do that.

> Oh. It appears to register trigger per block device. That's no-no.

Hmm, why is that a no-no? It seems it works that way for CPUs already. I can see triggers from cpu0 to cpu39 on our servers with two CPUs, 10 cores and 2 threads per core. So we even have one trigger for every cpu thread.

I've never seen a host with 40 nvme disks, so why is this problematic if having 40 cpu triggers is not? Or does "trigger per block device" mean sth. else?

Michael



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: led block trigger patch
  2020-08-10  6:48   ` truart
@ 2020-08-10  7:33     ` Pavel Machek
  2020-08-10  7:53       ` Aw: " truart
  0 siblings, 1 reply; 5+ messages in thread
From: Pavel Machek @ 2020-08-10  7:33 UTC (permalink / raw)
  To: truart; +Cc: linux-leds

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

Hi!

> > Find out what is wrong with the patch, fix it, resubmit it.
> 
> I would like to, but unfortunately, I've no skills in programming so I'm not able to do that.
> 

You can learn, or find someone to do the work for you.

What was the point of me reviewing the old patch when you are not
going to fix it? That was not very constructive.

> > Oh. It appears to register trigger per block device. That's no-no.
> 
> Hmm, why is that a no-no? It seems it works that way for CPUs already. I can see triggers from cpu0 to cpu39 on our servers with two CPUs, 10 cores and 2 threads per core. So we even have one trigger for every cpu thread.
> 
> I've never seen a host with 40 nvme disks, so why is this problematic if having 40 cpu triggers is not? Or does "trigger per block device" mean sth. else?

We made a mistake with cpu triggers. Not doing it again. 

								Pavel
								
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Aw: Re: led block trigger patch
  2020-08-10  7:33     ` Pavel Machek
@ 2020-08-10  7:53       ` truart
  0 siblings, 0 replies; 5+ messages in thread
From: truart @ 2020-08-10  7:53 UTC (permalink / raw)
  To: Pavel Machek; +Cc: linux-leds

> What was the point of me reviewing the old patch when you are not
> going to fix it? That was not very constructive.

I'm sorry :( I really didn't mean to cause unneccessary work for anyone!
Michael

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2020-08-10  7:53 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-07-28 18:47 led block trigger patch truart
2020-08-05 21:57 ` Pavel Machek
     [not found] ` <50db75e2-d53c-ce8b-bd00-1099be0e2e74@ifi.lmu.de>
2020-08-10  6:48   ` truart
2020-08-10  7:33     ` Pavel Machek
2020-08-10  7:53       ` Aw: " truart

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).