netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Chan" <mchan@broadcom.com>
To: "Rick Jones" <rick.jones2@hp.com>
Cc: "David Miller" <davem@davemloft.net>,
	mcarlson@broadcom.com, "netdev" <netdev@vger.kernel.org>,
	andy@greyhouse.net
Subject: Re: [PATCH 10/13] tg3: Increase the PCI MRRS
Date: Thu, 15 Nov 2007 18:17:11 -0800	[thread overview]
Message-ID: <1195179431.5745.22.camel@dell> (raw)
In-Reply-To: <473CE526.4080209@hp.com>

On Thu, 2007-11-15 at 16:32 -0800, Rick Jones wrote:

> I'm going to get very rapidly out of my PCI depth, but on one or the 
> other (e vs X) isn't is possible from the standpoint of PCI for a device 
> to have multiple transactions outstanding at a time?

Yes, see my other response.  Multiple outstanding transactions and a
bigger maximum payload size will increase the throughput without the
need to increase the MRRS.

> 
> Does the current value of the MRRS get displayed in lspci output?  It 
> wouldn't be a slam dunk, but if someone were looking at that and saw the 
> value large they might make an educated guess.
> 

Yes:
        Capabilities: [ac] Express Endpoint IRQ 0
                Device: Supported: MaxPayload 512 bytes, PhantFunc 0, ExtTag-
                Device: Latency L0s <1us, L1 <2us
                Device: AtnBtn- AtnInd- PwrInd-
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr+ NoSnoop+
                Device: MaxPayload 256 bytes, MaxReadReq 512 bytes




      reply	other threads:[~2007-11-16  1:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-10  0:39 [PATCH 10/13] tg3: Increase the PCI MRRS Matt Carlson
2007-11-13  5:21 ` David Miller
2007-11-15 22:20   ` Matt Carlson
2007-11-15 22:41     ` David Miller
2007-11-15 23:51       ` Michael Chan
2007-11-15 23:08         ` David Miller
2007-11-16  0:32       ` Rick Jones
2007-11-16  2:17         ` Michael Chan [this message]

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=1195179431.5745.22.camel@dell \
    --to=mchan@broadcom.com \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=mcarlson@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.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).