From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, NeilBrown <neilb@suse.de>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: 2.6.22-rc1-mm1 - s390 vs. md
Date: Wed, 23 May 2007 10:55:03 +0200 [thread overview]
Message-ID: <1179910503.17849.19.camel@localhost> (raw)
In-Reply-To: <20070523104639.6bc0650e@gondolin.boeblingen.de.ibm.com>
On Wed, 2007-05-23 at 10:46 +0200, Cornelia Huck wrote:
> Taking a quick look at the async_*.c stuff, the functions in question
> basically seem to be of the form
>
> check_if_we_can_do_it_async();
> if (async_ok) {
> /* do async stuff */
> /* that's where the dma mapping creeps in */
> } else {
> /* do it sync */
> /* seems fine for us */
> }
Hmm, on what does the async_ok depend? Is that a runtime check that is
done once or is it something more complicated like the availability of a
dma slot? If it is a simple runtime check then there should be a
operations structure that has indirect function pointers for the
different async_memset_{sync,async}() functions. Instead of doing the
async_ok check just call the function. That would save an if as well.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2007-05-23 8:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 6:36 2.6.22-rc1-mm1 - s390 vs. md Williams, Dan J
2007-05-18 5:39 ` Cornelia Huck
2007-05-18 16:30 ` Williams, Dan J
2007-05-21 7:24 ` Cornelia Huck
2007-05-21 8:52 ` Williams, Dan J
2007-05-23 0:25 ` Williams, Dan J
2007-05-23 8:05 ` Martin Schwidefsky
2007-05-23 8:46 ` Cornelia Huck
2007-05-23 8:55 ` Martin Schwidefsky [this message]
2007-05-24 22:11 ` Williams, Dan J
2007-05-25 6:02 ` Cornelia Huck
-- strict thread matches above, loose matches on Subject: below --
2007-05-16 3:19 2.6.22-rc1-mm1 Andrew Morton
2007-05-16 7:57 ` 2.6.22-rc1-mm1 - s390 vs. md Cornelia Huck
2007-05-16 17:21 ` Williams, Dan J
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=1179910503.17849.19.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cornelia.huck@de.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=neilb@suse.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