Re: sensors fun..

Quoting Poul-Henning Kamp <phk@xxxxxxxxxxxxxx> (from Fri, 19 Oct 2007 13:20:33 +0000):

In message <20071019151426.ttkynf788c0g8s4k@xxxxxxxxxxxxxxxxxxxxx>, Alexander L
eidinger writes:

Alexander,

I'm getting pretty tired of this game of yours.

I'm asking questions to understand what is going on.

Either you're not paying attention to what I write, or you are so
totally blinded by rage that you don't try to understand it.

I'm not in rage and I was not in rage.

This is my last email to you on this subject.

That's sad.

As far as I can tell, you have nothing to do with the actual code,

We're talking about architecture here in this thread on arch, not about any specific commits to the CVS.

apart from committing it without proper review and discussion, so

I was willing to discuss this with you and others long ago, but you stopped talking without any notification why. Then you stomped in saying that you don't like the _idea_ of the framework without pointing to technical flaws (you mentioned you didn't even looked at the architecture). Now you tell me that you don't want to discuss architectural things with me. Could you please tell me what I did to you that you don't want to talk with me?

why don't you step out of the loop, and leave Constantine, who,
quite frankly, seems to have a better grasp of the subject than
you, participate instead ?

You don't care to explain where my point of view of monitoring is wrong?

What to do with sensors which aren't event based or don't have a
predefined polling interval (e.g., temperature and humidity)? What do
you think will the ratio be between the amount of sensors with and
without something like this?

They poll at whatever rate the application ask them to, (using an
ioctl ?)

So you want to put the polling interval (=3D the polling policy) into =20
the kernel (with e.g, an ioctl)?

No, the "polling policy" does not end up in the kernel if the
application calls an ioctl that says "poll every 5 seconds".

Look up the meaning of the word policy if you don't belive me.

According to dict.leo.org:
english german
policy especially [comp.] die Richtlinie

If you say "poll every 5 seconds" you give the kernel "die Richtlinie" to look every 5 seconds for the sensor data and to provide it to the application. Looks good to me in my language. As you don't like it: feel free to replace every ocurence of "polling policy" with "polling interval" in my questions. If you think those questions are not worth being answered, I would like to know why.

Bye,
Alexander.

--
I've got a COUSIN who works in the GARMENT DISTRICT ...

http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • [PATCH 13/45] KVM: s390: API documentation
    ... user interface that are unique to s390 architecture. ... +This Documentation describes the unique ioctl calls to /dev/kvm, ... +Floating interrupts may be delivered to any virtual cpu in the configuration. ...
    (Linux-Kernel)
  • Re: [PATCH 13/45] KVM: s390: API documentation
    ... user interface that are unique to s390 architecture. ... +This Documentation describes the unique ioctl calls to /dev/kvm, ... +Floating interrupts may be delivered to any virtual cpu in the configuration. ...
    (Linux-Kernel)
  • Re: [JANITOR PROPOSAL] Switch ioctl functions to ->unlocked_ioctl
    ... Andy, it would be good if checkpatch.pl complained about .ioctl = ... Also perhaps if a whole new file_operations with a ioctl is added ... complain about missing compat_ioctl as a low prioritity warning? ... (might be ok if it's architecture specific on architectures without ...
    (Linux-Kernel)