From: Tejun Heo <tj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Chris Metcalf <cmetcalf@tilera.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>,
Cody P Schafer <cody@linux.vnet.ibm.com>
Subject: Re: [PATCH v4 2/2] mm: make lru_add_drain_all() selective
Date: Tue, 13 Aug 2013 18:07:00 -0400 [thread overview]
Message-ID: <20130813220700.GC28996@mtj.dyndns.org> (raw)
In-Reply-To: <20130813141621.3f1c3415901d4236942ee736@linux-foundation.org>
Hello,
On Tue, Aug 13, 2013 at 02:16:21PM -0700, Andrew Morton wrote:
> I've yet to see any evidence that callback APIs have been abused and
> I've yet to see any reasoning which makes me believe that this one will
> be abused.
Well, off the top of my head.
* In general, it's clunkier. Callbacks become artificial boundaries
across which context has to be carried over explicitly. It often
involves packing data into a temporary struct. The artificial
barrier also generally makes the logic more difficult to follow.
This is pretty general problem with callback based interface and why
many programming languages / conventions prefer iterator style
interface over callback based ones. It makes the code a lot easier
to organize around the looping construct. Here, it isn't as
pronounced because the thing naturally requires a callback anyway.
* From the API itself, it often isn't clear what restrictions the
context the callback is called under would have. It sure is partly
documentation problem but is pretty easy to get wrong inadvertantly
as the code evolves and can be difficult to spot as the context
isn't apparent.
Moving away from callbacks started with higher level languages but the
kernel sure is on the boat too where possible. This one is muddier as
the interface is async in nature but still it's at least partially
applicable.
> > It feels a bit silly to me to push the API
> > that way when doing so doesn't even solve the allocation problem.
>
> It removes the need to perform a cpumask allocation in
> lru_add_drain_all().
But that doesn't really solve anything, does it?
> > It doesn't really buy us much while making the interface more complex.
>
> It's a superior interface.
It is more flexible but at the same time clunkier. I wouldn't call it
superior and the flexibility doesn't buy us much here.
Thanks.
--
tejun
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-08-13 22:07 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 20:22 [PATCH] mm: make lru_add_drain_all() selective Chris Metcalf
2013-08-06 20:22 ` [PATCH v2] " Chris Metcalf
2013-08-07 20:45 ` Tejun Heo
2013-08-07 20:49 ` [PATCH v3 1/2] workqueue: add new schedule_on_cpu_mask() API Chris Metcalf
2013-08-07 20:52 ` [PATCH v3 2/2] mm: make lru_add_drain_all() selective Chris Metcalf
2013-08-07 22:48 ` [PATCH v2] " Cody P Schafer
2013-08-07 20:49 ` [PATCH v4 1/2] workqueue: add new schedule_on_cpu_mask() API Chris Metcalf
2013-08-09 15:02 ` Tejun Heo
2013-08-09 16:12 ` Chris Metcalf
2013-08-09 16:30 ` Tejun Heo
2013-08-07 20:49 ` [PATCH v5 " Chris Metcalf
2013-08-09 17:40 ` Tejun Heo
2013-08-09 17:49 ` [PATCH v6 " Chris Metcalf
2013-08-09 17:52 ` [PATCH v6 2/2] mm: make lru_add_drain_all() selective Chris Metcalf
2013-08-07 20:52 ` [PATCH v5 " Chris Metcalf
2013-08-07 20:52 ` [PATCH v4 " Chris Metcalf
2013-08-12 21:05 ` Andrew Morton
2013-08-13 1:53 ` Chris Metcalf
2013-08-13 19:35 ` Andrew Morton
2013-08-13 20:19 ` Tejun Heo
2013-08-13 20:31 ` Andrew Morton
2013-08-13 20:59 ` Chris Metcalf
2013-08-13 21:13 ` Andrew Morton
2013-08-13 22:13 ` Chris Metcalf
2013-08-13 22:26 ` Andrew Morton
2013-08-13 23:04 ` Chris Metcalf
2013-08-13 22:51 ` [PATCH v7 1/2] workqueue: add schedule_on_each_cpu_cond Chris Metcalf
2013-08-13 22:53 ` [PATCH v7 2/2] mm: make lru_add_drain_all() selective Chris Metcalf
2013-08-13 23:29 ` Tejun Heo
2013-08-13 23:32 ` Chris Metcalf
2013-08-14 6:46 ` Andrew Morton
2013-08-14 13:05 ` Tejun Heo
2013-08-14 16:03 ` Chris Metcalf
2013-08-14 16:57 ` Tejun Heo
2013-08-14 17:18 ` Chris Metcalf
2013-08-14 20:07 ` Tejun Heo
2013-08-14 20:22 ` [PATCH v8] " Chris Metcalf
2013-08-14 20:44 ` Andrew Morton
2013-08-14 20:50 ` Tejun Heo
2013-08-14 21:03 ` Andrew Morton
2013-08-14 21:07 ` Andrew Morton
2013-08-14 21:12 ` Andrew Morton
2013-08-14 21:23 ` Chris Metcalf
2013-08-13 23:44 ` [PATCH v7 2/2] " Chris Metcalf
2013-08-13 23:51 ` Tejun Heo
2013-08-13 21:07 ` [PATCH v4 " Tejun Heo
2013-08-13 21:16 ` Andrew Morton
2013-08-13 22:07 ` Tejun Heo [this message]
2013-08-13 22:18 ` Andrew Morton
2013-08-13 22:33 ` Tejun Heo
2013-08-13 22:47 ` Andrew Morton
2013-08-13 23:03 ` Tejun Heo
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=20130813220700.GC28996@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cmetcalf@tilera.com \
--cc=cody@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tglx@linutronix.de \
/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).