public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Bruno Randolf <br1@einfach.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	randy.dunlap@oracle.com, peterz@infradead.org,
	blp@cs.stanford.edu, linux-kernel@vger.kernel.org,
	Lars_Ericsson@telia.com, kosaki.motohiro@jp.fujitsu.com,
	kevin.granade@gmail.com,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH v6] Add generic exponentially weighted moving average (EWMA) function
Date: Thu, 11 Nov 2010 19:17:34 +0100	[thread overview]
Message-ID: <4CDC333E.4070104@s5r6.in-berlin.de> (raw)
In-Reply-To: <201011111421.49464.br1@einfach.org>

Bruno Randolf wrote:
> On Thu November 11 2010 13:02:31 Andrew Morton wrote:
>> So perhaps it would be best to merge this via the wireless tree, so
>> everything exists in one place and it can be fed into linux-next and
>> into mainline in an orderly fashion.
>>
>> If that sounds like a plan then I can send this patch in John's
>> direction.  Which means that if he merges it into mainline without also
>> merging any of your patches which _use_ this function then we still end
>> up with unused code in mainline, but at least that way it wasn't my fault
>> ;)
>>
>> Let me know your thoughts?
> 
> Sounds like a good plan to me. But let's hear Johns opinion.
> 
> I have a patch or two using this function, which I hope will get merged into 
> wireless-testing soon after, but obviously it's up to John. There are more 
> places in the wireless part which could make use of this function (right now 
> each have their own EWMA implementation), and I'll try to get them all 
> updated, but finally it's the individual maintainers, who decide if they want 
> to make that change or not, I guess.

It seems totally clear-cut to me that code like this is submitted together
with at least one call site, and it is submitted through the tree in which
that call site is maintained.

>> (And it's a bit sad that the function will exist in the base vmlinux
>> even for people who don't ever use it, but that's a problem which we
>> don't really have a good solution for).
> 
> Hmm, should I switch it back to all inlines?

Add a hidden Kconfig variable for it which is SELECTed by those Kconfig
prompts that require it?  That's the good solution that we use for a number of
similar library functions.
$ cat lib/Makefile

> On the other hand, if a generic EWMA function is useful at all I guess it 
> could be used in many places all over the kernel. Unfortunately I don't have 
> time and knowledge to find all these places and update them to use the generic 
> code.

Don't worry.  There are people who specialize in this sort of activity.

Two remarks on your patch:

You use WARN_ON in lib/average.c.  You should include <linux/bug.h>.

Why do ewma_init() and ewma_add() return their first argument?  They look to
me like they can be straight-forward void functions.
-- 
Stefan Richter
-=====-==-=- =-== -=-==
http://arcgraph.de/sr/

  reply	other threads:[~2010-11-11 18:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11  3:47 [PATCH v6] Add generic exponentially weighted moving average (EWMA) function Bruno Randolf
2010-11-11  3:53 ` Andrew Morton
2010-11-11  3:59   ` Bruno Randolf
2010-11-11  4:02 ` Andrew Morton
2010-11-11  5:21   ` Bruno Randolf
2010-11-11 18:17     ` Stefan Richter [this message]
2010-11-12  1:44       ` Bruno Randolf
2010-11-14  5:07         ` KOSAKI Motohiro
2010-11-14  8:51           ` Stefan Richter
2010-11-15  2:10             ` Bruno Randolf
2010-11-15  7:38               ` Stefan Richter
2010-11-15  7:50                 ` Bruno Randolf
2010-11-15  8:46                   ` Peter Zijlstra
  -- strict thread matches above, loose matches on Subject: below --
2010-10-22  1:51 Bruno Randolf

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=4CDC333E.4070104@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=Lars_Ericsson@telia.com \
    --cc=akpm@linux-foundation.org \
    --cc=blp@cs.stanford.edu \
    --cc=br1@einfach.org \
    --cc=kevin.granade@gmail.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=peterz@infradead.org \
    --cc=randy.dunlap@oracle.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