linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: David Miller <davem@davemloft.net>
Cc: Linuxppc-dev Development <linuxppc-dev@ozlabs.org>,
	Netdev <netdev@vger.kernel.org>,
	Haiying Wang <Haiying.Wang@freescale.com>
Subject: Re: [PATCH 5/6 v2] net/ucc_geth: Assign six threads to Rx for UEC
Date: Fri, 1 May 2009 16:56:19 -0500	[thread overview]
Message-ID: <F2CB7830-33F9-4F6C-A782-6B086166FC4D@kernel.crashing.org> (raw)
In-Reply-To: <1241206851-27749-3-git-send-email-Haiying.Wang@freescale.com>


On May 1, 2009, at 2:40 PM, Haiying Wang wrote:

> in the case the QE has 46 SNUMs for the threads to support four UCC  
> Ethernet at
> 1000Base-T simultaneously.
>
> Signed-off-by: Haiying Wang <Haiying.Wang@freescale.com>
> ---
> v2 change: Add comments for the Rx threads change.
> drivers/net/ucc_geth.c |   10 +++++++++-
> 1 files changed, 9 insertions(+), 1 deletions(-)

Dave,

One more patch for you to Ack and let me handle via the powerpc tree  
because of dependencies.

- k

>
>
> diff --git a/drivers/net/ucc_geth.c b/drivers/net/ucc_geth.c
> index 44f8392..1cb2710 100644
> --- a/drivers/net/ucc_geth.c
> +++ b/drivers/net/ucc_geth.c
> @@ -3702,7 +3702,15 @@ static int ucc_geth_probe(struct of_device*  
> ofdev, const struct of_device_id *ma
> 		ug_info->uf_info.utfet = UCC_GETH_UTFET_GIGA_INIT;
> 		ug_info->uf_info.utftt = UCC_GETH_UTFTT_GIGA_INIT;
> 		ug_info->numThreadsTx = UCC_GETH_NUM_OF_THREADS_4;
> -		ug_info->numThreadsRx = UCC_GETH_NUM_OF_THREADS_4;
> +
> +		/* If QE's snum number is 46 which means we need to support
> +		 * 4 UECs at 1000Base-T simultaneously, we need to allocate
> +		 * more Threads to Rx.
> +		 */
> +		if (qe_get_num_of_snums() == 46)
> +			ug_info->numThreadsRx = UCC_GETH_NUM_OF_THREADS_6;
> +		else
> +			ug_info->numThreadsRx = UCC_GETH_NUM_OF_THREADS_4;
> 	}
>
> 	if (netif_msg_probe(&debug))
> -- 
> 1.6.0.2

  parent reply	other threads:[~2009-05-01 21:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01 19:40 [PATCH 2/6 v2] powerpc/qe: update risc allocation for QE Haiying Wang
2009-05-01 19:40 ` [PATCH 4/6 v2] powerpc/qe: update QE Serial Number Haiying Wang
2009-05-01 19:40   ` [PATCH 5/6 v2] net/ucc_geth: Assign six threads to Rx for UEC Haiying Wang
2009-05-01 19:40     ` [PATCH 6/6 v2] powerpc/85xx: Add MPC8569MDS board support Haiying Wang
2009-05-01 19:40       ` [PATCH] powerpc/85xx: add new qe properties for QE based chips Haiying Wang
2009-05-01 20:13         ` Timur Tabi
2009-05-01 22:04         ` Kumar Gala
2009-05-01 22:12       ` [PATCH 6/6 v2] powerpc/85xx: Add MPC8569MDS board support Kumar Gala
2009-05-01 20:17     ` [PATCH 5/6 v2] net/ucc_geth: Assign six threads to Rx for UEC Timur Tabi
2009-05-01 21:56     ` Kumar Gala [this message]
2009-05-01 22:03       ` David Miller
2009-05-01 22:12     ` Kumar Gala
2009-05-01 20:14   ` [PATCH 4/6 v2] powerpc/qe: update QE Serial Number Timur Tabi
2009-05-01 22:03   ` Kumar Gala
2009-05-01 20:15 ` [PATCH 2/6 v2] powerpc/qe: update risc allocation for QE Timur Tabi
2009-05-01 22:03   ` Kumar Gala

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=F2CB7830-33F9-4F6C-A782-6B086166FC4D@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=Haiying.Wang@freescale.com \
    --cc=davem@davemloft.net \
    --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).