Netdev List
 help / color / mirror / Atom feed
From: Arthur Kepner <akepner@sgi.com>
To: raghavendra.koushik@neterion.com
Cc: jgarzik@pobox.com, netdev@oss.sgi.com, netdev@vger.kernel.org,
	ravinandan.arakali@neterion.com, leonid.grossman@neterion.com,
	rapuru.sriram@neterion.com
Subject: Re: [PATCH 2.6.12.1 5/12] S2io: Performance improvements
Date: Thu, 7 Jul 2005 16:15:20 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0507071552130.24321@resonance.WorkGroup> (raw)
In-Reply-To: <20050707222741.71C3E89826@linux.site>


On Thu, 7 Jul 2005 raghavendra.koushik@neterion.com wrote:

> .......
> 2. Removed unnecessary PIOs(read/write of tx_traffic_int and 
>    rx_traffic_int) from interrupt handler and removed read of
>    general_int_status register from xmit routine.			    
> ......
> @@ -2891,6 +2869,8 @@ int s2io_xmit(struct sk_buff *skb, struc
>  	val64 = mac_control->fifos[queue].list_info[put_off].list_phy_addr;
>  	writeq(val64, &tx_fifo->TxDL_Pointer);
>  
> +	wmb();
> +
>  	val64 = (TX_FIFO_LAST_TXD_NUM(frg_cnt) | TX_FIFO_FIRST_LIST |
>  		 TX_FIFO_LAST_LIST);
>  
> @@ -2900,9 +2880,6 @@ int s2io_xmit(struct sk_buff *skb, struc
>  #endif
>  	writeq(val64, &tx_fifo->List_Control);
>  
> -	/* Perform a PCI read to flush previous writes */
> -	val64 = readq(&bar0->general_int_status);
> -
>  	put_off++;
                                                                  
I thought that an mmiowb() was called for here (to order the PIO 
writes above more cheaply than doing the readq()). I posted a 
patch like this some time ago:

http://marc.theaimsgroup.com/?l=linux-netdev&m=111508292028110&w=2

FWIW, I've done quite a few performance measurements with the patch 
I posted earlier, and it's worked well. For 1500 byte mtus throughput 
goes up by ~20%. Is even the mmiowb() unnecessary?

What is the wmb() above for?

--
Arthur

  reply	other threads:[~2005-07-07 23:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07 22:27 [PATCH 2.6.12.1 5/12] S2io: Performance improvements raghavendra.koushik
2005-07-07 23:15 ` Arthur Kepner [this message]
2005-07-08  1:06   ` Raghavendra Koushik
2005-07-08  3:00     ` David S. Miller
2005-07-08  3:08       ` Jeff Garzik
2005-07-08 15:31     ` Arthur Kepner
2005-07-08 18:16       ` Raghavendra Koushik
2005-07-08 18:17       ` Ravinandan Arakali
2005-07-12 20:27 ` Christoph Hellwig
2005-07-12 20:34   ` David S. Miller
2005-07-12 21:00     ` Ravinandan Arakali
2005-07-12 21:04       ` David S. Miller
2005-07-12 21:07         ` Christoph Hellwig
2005-07-12 21:26           ` Andi Kleen
2005-07-12 21:54         ` Ravinandan Arakali
2005-07-29 16:37         ` Ravinandan Arakali
2005-07-31 14:05           ` Christoph Hellwig
2005-08-02 23:13             ` Ravinandan Arakali
2005-08-02 23:26               ` 'Christoph Hellwig'
2005-07-12 20:56   ` Leonid Grossman
  -- strict thread matches above, loose matches on Subject: below --
2005-08-03 12:48 Prarit Bhargava

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=Pine.LNX.4.61.0507071552130.24321@resonance.WorkGroup \
    --to=akepner@sgi.com \
    --cc=jgarzik@pobox.com \
    --cc=leonid.grossman@neterion.com \
    --cc=netdev@oss.sgi.com \
    --cc=netdev@vger.kernel.org \
    --cc=raghavendra.koushik@neterion.com \
    --cc=rapuru.sriram@neterion.com \
    --cc=ravinandan.arakali@neterion.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