From: Thomas Klein <osstklei@de.ibm.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Thomas Klein <tklein@de.ibm.com>,
Jan-Bernd Themann <themann@de.ibm.com>,
netdev@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Christoph Raisch <raisch@de.ibm.com>,
linux-ppc <linuxppc-dev@ozlabs.org>,
Marcus Eder <meder@de.ibm.com>
Subject: Re: [2.6.19 PATCH 1/7] ehea: interface to network stack
Date: Mon, 21 Aug 2006 16:52:38 +0200 [thread overview]
Message-ID: <44E9C8B6.7030701@de.ibm.com> (raw)
In-Reply-To: <20060818144429.GF5201@martell.zuzino.mipt.ru>
Alexey Dobriyan wrote:
> On Fri, Aug 18, 2006 at 01:29:01PM +0200, Jan-Bernd Themann wrote:
>> --- linux-2.6.18-rc4-orig/drivers/net/ehea/ehea_main.c
>> +++ kernel/drivers/net/ehea/ehea_main.c
>
>> +static inline int ehea_refill_rq3_def(struct ehea_port_res *pr, int nr_of_wqes)
>
> This one looks too big to be inlined as well as other similalry named
> functions.
Agreed. Inlining avoided where possible.
>> +static int ehea_clean_port_res(struct ehea_port *port, struct ehea_port_res *pr)
>
> Freeing/deallocating/cleaning functions usually return void. The fact
> that you always return -EINVAL only reaffirmes my belief. ;-)
>
Fixed.
>> +static inline void write_swqe2_data(struct sk_buff *skb,
>> + struct net_device *dev,
>> + struct ehea_swqe *swqe,
>> + u32 lkey)
>
> Way too big.
Function split.
>> +static inline void ehea_xmit2(struct sk_buff *skb,
>> + struct net_device *dev, struct ehea_swqe *swqe,
>> + u32 lkey)
>> +
>> +static inline void ehea_xmit3(struct sk_buff *skb,
>> + struct net_device *dev, struct ehea_swqe *swqe)
>
> Ditto.
These functions are on a performance-critical path and they are called
exactly once - so the object's size isn't affected and having them inline
seems appropriate to me.
>> + if (grp)
>> + memset(cb1->vlan_filter, 0, sizeof(cb1->vlan_filter));
>> + else
>> + memset(cb1->vlan_filter, 1, sizeof(cb1->vlan_filter));
>
> Just to be sure, this should be 1 not 0xff?
>
Will be checked.
>> +void ehea_clean_all_port_res(struct ehea_port *port)
>> +{
>> + int ret;
>> + int i;
>> + for(i = 0; i < port->num_def_qps + port->num_tx_qps; i++)
>> + ehea_clean_port_res(port, &port->port_res[i]);
>> +
>> + ret = ehea_destroy_eq(port->qp_eq);
>> +}
>
> ret is entirely useless.
Correct. It's gone.
>
>> +int __init ehea_module_init(void)
> static
>
>> +{
>> + int ret = -EINVAL;
>> +
>> + printk("IBM eHEA Ethernet Device Driver (Release %s)\n", DRV_VERSION);
>> +
>> + ret = ibmebus_register_driver(&ehea_driver);
>> + if (ret) {
>> + ehea_error("failed registering eHEA device driver on ebus");
>> + return -EINVAL;
>> + }
>> +
>> + return 0;
>> +}
>
> Pass ret to upper layer. Simplest way is:
>
> static int __init ehea_module_init(void)
> {
> return ibmebus_register_driver(&ehea_driver);
> }
Agreed to pass ret to upper layer, but we want to keep the error message.
Code modified accordingly.
Regards
Thomas
next prev parent reply other threads:[~2006-08-21 14:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 11:29 [2.6.19 PATCH 1/7] ehea: interface to network stack Jan-Bernd Themann
2006-08-18 13:47 ` Alexey Dobriyan
2006-08-18 13:56 ` Arjan van de Ven
2006-08-18 14:44 ` Alexey Dobriyan
2006-08-21 12:23 ` Jan-Bernd Themann
2006-08-21 13:18 ` Jörn Engel
2006-08-21 14:52 ` Thomas Klein [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-22 12:51 Jan-Bernd Themann
2006-08-23 8:56 Jan-Bernd Themann
2006-09-04 10:37 Jan-Bernd Themann
2006-09-04 20:16 ` Francois Romieu
2006-09-04 21:11 ` Arnd Bergmann
2006-09-04 21:49 ` Francois Romieu
2006-09-06 15:22 ` Jeff Garzik
2006-09-05 15:09 ` Thomas Klein
2006-09-05 18:58 ` Francois Romieu
2006-09-06 12:53 ` Jan-Bernd Themann
2006-09-06 13:30 Jan-Bernd Themann
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=44E9C8B6.7030701@de.ibm.com \
--to=osstklei@de.ibm.com \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=meder@de.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=raisch@de.ibm.com \
--cc=themann@de.ibm.com \
--cc=tklein@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).