From: Coiby Xu <coiby.xu@gmail.com>
To: Benjamin Poirier <benjamin.poirier@gmail.com>
Cc: linux-staging@lists.linux.dev, netdev@vger.kernel.org
Subject: About improving the qlge Ethernet driver by following drivers/staging/qlge/TODO
Date: Tue, 4 May 2021 21:14:21 +0800 [thread overview]
Message-ID: <20210504131421.mijffwcruql2fupn@Rk> (raw)
Hi Benjamin,
As you have known, I'm working on improving drivers/staging/qlge. I'm
not sure if I correctly understand some TODO items. Since you wrote
the TODO list, could you explain some of the items or comment on the
corresponding fix for me?
> * while in that area, using two 8k buffers to store one 9k frame is a poor
> choice of buffer size.
Currently, LARGE_BUFFER_MAX_SIZE is defined as 8192. How about we simply
changing LARGE_BUFFER_MAX_SIZE to 4096? This is what
drivers/net/ethernet/intel/e1000 does for jumbo frame right now.
> * in the "chain of large buffers" case, the driver uses an skb allocated with
> head room but only puts data in the frags.
Do you suggest implementing the copybreak feature which exists for e1000 for
this driver, i.e., allocing a sk_buff and coping the header buffer into it?
> * fix weird line wrapping (all over, ex. the ql_set_routing_reg() calls in
> qlge_set_multicast_list()).
This issue of weird line wrapping is supposed to be all over. But I can
only find the ql_set_routing_reg() calls in qlge_set_multicast_list have
this problem,
if (qlge_set_routing_reg
(qdev, RT_IDX_PROMISCUOUS_SLOT, RT_IDX_VALID, 1)) {
I can't find other places where functions calls put square and arguments
in the new line. Could you give more hints?
Thanks!
--
Best regards,
Coiby
next reply other threads:[~2021-05-04 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 13:14 Coiby Xu [this message]
2021-05-05 8:59 ` About improving the qlge Ethernet driver by following drivers/staging/qlge/TODO Benjamin Poirier
2021-05-07 1:32 ` Coiby Xu
2021-05-07 12:16 ` Benjamin Poirier
2021-05-07 13:25 ` Coiby Xu
2021-05-08 23:27 ` Coiby Xu
2021-05-09 7:51 ` Benjamin Poirier
2021-05-09 23:54 ` Coiby Xu
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=20210504131421.mijffwcruql2fupn@Rk \
--to=coiby.xu@gmail.com \
--cc=benjamin.poirier@gmail.com \
--cc=linux-staging@lists.linux.dev \
--cc=netdev@vger.kernel.org \
/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