All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Michael Chan <mchan@broadcom.com>
Cc: Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	akpm@osdl.org, greg@kroah.com, "Durairaj,
	Sundarapandian" <sundarapandian.durairaj@intel.com>
Subject: Re: [PATCH] pci-mmconfig fix for 2.6.9
Date: Fri, 12 Nov 2004 11:35:47 -0700	[thread overview]
Message-ID: <20041112183547.GA8828@colo.lackof.org> (raw)
In-Reply-To: <B1508D50A0692F42B217C22C02D84972020F3C99@NT-IRVA-0741.brcm.ad.broadcom.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 1473 bytes --]

On Fri, Nov 12, 2004 at 09:52:17AM -0800, Michael Chan wrote:
> On Wednesday, November 10, 2004 11:58 PM Andi Kleen wrote:
> > Where is it guaranteed that these writes are non posted?
> 
> Intel chipset engineer confirmed that they are non-posted.

Michael,
Thanks for digging that up.
I think Andi was looking for references to the PCI-E spec.
I found such a statement in "PCI Express(TM) Base Specification
Revision 1.0a".

Table 2-3 on page 47 says:
| Cpl 00 0 1010 Completion without Data ­ Used for I/O and
|               Configuration Write Completions and Read
|               Completions (I/O, Configuration, or
|               Memory) with Completion Status other than
|               Successful Completion.

Section "2.2. Transaction Layer Protocol - Packet Definition"
| Transactions are carried using Requests and Completions. Completions
| are used only where required, for example, to return read data, or
| to acknowledge Completion of I/O and Configuration Write Transactions.
| Completions are associated with their corresponding Requests by the value
| in the Transaction ID field of the Packet header.

And "2.6.1 Flow Control Rules":
| Flow Control distinguishes three types of TLPs (note relationship
| to ordering rules ­ see Section 2.4):
| ·   Posted Requests (P) ­ Messages and Memory Writes
| ·   Non-Posted Requests (NP) ­ All Reads, I/O, and Configuration Writes
| ·   Completions (CPL) ­ Associated with corresponding NP Requests


hth,
grant

  reply	other threads:[~2004-11-12 18:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 17:52 [PATCH] pci-mmconfig fix for 2.6.9 Michael Chan
2004-11-12 18:35 ` Grant Grundler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-15  7:07 Michael Chan
2004-11-15  8:01 ` Grant Grundler
2004-11-13 16:22 Michael Chan
2004-11-13 19:46 ` Grant Grundler
2004-11-14  8:58   ` Andi Kleen
2004-11-15  6:00     ` Grant Grundler
2004-11-15  8:33       ` Andi Kleen
2004-11-12 23:56 Michael Chan
2004-11-13  9:22 ` Andi Kleen
2004-11-12 21:49 Michael Chan
2004-11-12 22:31 ` Grant Grundler
2004-11-12 19:23 Michael Chan
2004-11-12 20:55 ` Grant Grundler
2004-11-11 16:33 Nguyen, Tom L
2004-11-10 22:20 long
2004-11-11  1:30 ` Greg KH
2004-11-11  7:57 ` Andi Kleen
2004-11-10 19:38 long
2004-11-10 19:35 ` Greg KH
2004-11-10 17:26 Durairaj, Sundarapandian
2004-11-10 17:35 ` Greg KH

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=20041112183547.GA8828@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=mchan@broadcom.com \
    --cc=sundarapandian.durairaj@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.