From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Heiko J Schick <schihei@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, openib-general@openib.org,
linuxppc-dev@ozlabs.org, Christoph Raisch <RAISCH@de.ibm.com>,
Hoang-Nam Nguyen <HNGUYEN@de.ibm.com>,
Marcus Eder <MEDER@de.ibm.com>
Subject: Re: [PATCH 13/16] ehca: firmware InfiniBand interface
Date: Thu, 27 Apr 2006 14:37:01 +0200 [thread overview]
Message-ID: <20060427123701.GG32127@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <4450A1C0.3080209@de.ibm.com>
On Thu, 27 April 2006 12:49:36 +0200, Heiko J Schick wrote:
> +u64 hipz_h_alloc_resource_qp(const struct ipz_adapter_handle
> adapter_handle,
> + struct ehca_pfqp *pfqp,
> + const u8 servicetype,
> + const u8 daqp_ctrl,
> + const u8 signalingtype,
> + const u8 ud_av_l_key_ctl,
> + const struct ipz_cq_handle send_cq_handle,
> + const struct ipz_cq_handle receive_cq_handle,
> + const struct ipz_eq_handle async_eq_handle,
> + const u32 qp_token,
> + const struct ipz_pd pd,
> + const u16 max_nr_send_wqes,
> + const u16 max_nr_receive_wqes,
> + const u8 max_nr_send_sges,
> + const u8 max_nr_receive_sges,
> + const u32 ud_av_l_key,
> + struct ipz_qp_handle *qp_handle,
> + u32 * qp_nr,
> + u16 * act_nr_send_wqes,
> + u16 * act_nr_receive_wqes,
> + u8 * act_nr_send_sges,
> + u8 * act_nr_receive_sges,
> + u32 * nr_sq_pages,
> + u32 * nr_rq_pages,
> + struct h_galpas *h_galpas);
25 parameters? If you tell me which drugs were involved in this code,
I know what to stay away from. Might be the current record for any
code ever proposed for inclusion.
The whole patch is full of parameter-happy functions with this one
being the ugly top of the iceberg. I sincerely hope this is not a
defined ABI and can still be changed.
Jörn
--
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
-- Brian W. Kernighan
next prev parent reply other threads:[~2006-04-27 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 10:49 [PATCH 13/16] ehca: firmware InfiniBand interface Heiko J Schick
2006-04-27 12:37 ` Jörn Engel [this message]
2006-04-27 13:42 ` Pekka Enberg
2006-04-27 13:47 ` Jörn Engel
2006-04-27 17:13 ` Kyle Moffett
2006-04-27 22:42 ` Paul Mackerras
2006-05-02 9:30 ` Christoph Raisch
2006-05-03 13:56 ` Christoph Raisch
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=20060427123701.GG32127@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=HNGUYEN@de.ibm.com \
--cc=MEDER@de.ibm.com \
--cc=RAISCH@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=openib-general@openib.org \
--cc=schihei@de.ibm.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;
as well as URLs for NNTP newsgroup(s).