From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
Cc: linuxppc-dev@ozlabs.org, leoli@freescale.com, netdev@vger.kernel.org
Subject: Re: [PATCH] ucc_geth: Rework the TX logic.
Date: Thu, 26 Mar 2009 21:03:54 +0300 [thread overview]
Message-ID: <20090326180354.GA31732@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <1238089445-28396-1-git-send-email-Joakim.Tjernlund@transmode.se>
On Thu, Mar 26, 2009 at 06:44:05PM +0100, Joakim Tjernlund wrote:
> The line:
> if ((bd == ugeth->txBd[txQ]) && (netif_queue_stopped(dev) == 0))
> break;
> in ucc_geth_tx() didn not make sense to me. Rework & cleanup
> this logic to something understandable.
> ---
>
> Reworked the patch according to Antons comments.
>
> drivers/net/ucc_geth.c | 66 +++++++++++++++++++++++++++--------------------
> 1 files changed, 38 insertions(+), 28 deletions(-)
>
> diff --git a/drivers/net/ucc_geth.c b/drivers/net/ucc_geth.c
> index 7fc91aa..465de3a 100644
> --- a/drivers/net/ucc_geth.c
> +++ b/drivers/net/ucc_geth.c
> @@ -161,6 +161,17 @@ static struct ucc_geth_info ugeth_primary_info = {
>
> static struct ucc_geth_info ugeth_info[8];
>
> +
> +static inline u32 __iomem *bd2buf(u8 __iomem *bd)
> +{
> + return (u32 __iomem *)(bd+4);
Spaces around "+"...
Also, now it's obvious that we're just reading status or buf.
So instead of these inlines we could use struct qe_bd as described
in asm/qe.h.
I.e.
struct qe_bd *bd = ...;
in_be32(&bd->buf);
in_be16(&bd->status);
Oh, wait. We can't, ucc_geth assumes status is u32, which includes
the length field, i.e. ucc_fast.h defines:
#define T_W 0x20000000
:-(
The cleanup work surely desires a separate patch, so bd2buf and
bd2status are OK, for now.
I'll test the patch as soon as I'll get some QE board back on
my table (actually I have one QE board handy, but it's a 1GHz
one, while I'd like to test the patch on a slow machine, where
we'll actually see performance regressions).
[...]
> + tx_ind = (tx_ind + 1) & TX_RING_MOD_MASK(ugeth->ug_info->bdRingLenTx[txQ]);
Line over 80 columns.
[...]
> + if (num_freed)
> + netif_wake_queue(dev); /* We freed some buffers, so restart transmission */
Ditto.
Please make sure your patches pass scripts/checkpatch.pl.
Thanks,
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-03-26 18:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 17:44 [PATCH] ucc_geth: Rework the TX logic Joakim Tjernlund
2009-03-26 18:03 ` Anton Vorontsov [this message]
2009-03-26 18:26 ` Joakim Tjernlund
2009-03-27 9:45 ` Li Yang
2009-03-27 10:23 ` Joakim Tjernlund
2009-03-27 10:39 ` Li Yang
2009-03-27 11:39 ` Joakim Tjernlund
2009-03-27 13:26 ` Scott Wood
2009-03-30 16:38 ` Joakim Tjernlund
2009-03-30 17:22 ` Scott Wood
2009-03-30 17:34 ` Joakim Tjernlund
2009-03-30 17:45 ` Scott Wood
2009-03-30 18:42 ` Joakim Tjernlund
2009-03-30 19:32 ` Scott Wood
2009-03-31 9:07 ` Joakim Tjernlund
2009-03-31 10:58 ` Li Yang
2009-03-31 14:37 ` Scott Wood
2009-03-31 8:16 ` Li Yang
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=20090326180354.GA31732@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=Joakim.Tjernlund@transmode.se \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).