From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] too good to pass up
Date: Thu, 27 Apr 2006 23:39:19 -0700 [thread overview]
Message-ID: <3e1162e60604272339q5cb30641tfb67affedbee50ce@mail.gmail.com> (raw)
In-Reply-To: <44514985.8060403@lanl.gov>
I've actually seen worse :) I saw a function in a certain library
with 36 parameters before.
On 4/27/06, Ronald G Minnich <rminnich@lanl.gov> wrote:
>
> this is from the openib mailing list :-)
>
> ron
> ===
> 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.
>
>
>
>
>
next prev parent reply other threads:[~2006-04-28 6:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 22:45 Ronald G Minnich
2006-04-27 22:57 ` Roman Shaposhnick
2006-04-27 22:58 ` Brantley Coile
2006-04-28 0:45 ` Roman Shaposhnick
2006-04-28 1:02 ` geoff
2006-04-28 13:00 ` Brantley Coile
2006-05-02 14:41 ` Aharon Robbins
2006-05-03 1:49 ` geoff
2006-04-27 23:58 ` geoff
2006-04-28 6:39 ` David Leimbach [this message]
2006-04-28 6:59 ` David Leimbach
2006-04-28 7:01 ` David Leimbach
2006-04-28 0:01 erik quanstrom
2006-04-28 13:01 erik quanstrom
2006-04-28 21:57 ` Charles Forsyth
2006-05-02 3:29 Ronald G Minnich
2006-05-02 5:10 ` Noah Evans
2006-05-02 6:11 ` Martin C. Atkins
2006-05-02 23:30 ` David Leimbach
2006-05-02 23:46 ` Skip Tavakkolian
2006-05-02 23:53 dmr
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=3e1162e60604272339q5cb30641tfb67affedbee50ce@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@cse.psu.edu \
/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).