All of lore.kernel.org
 help / color / mirror / Atom feed
From: kylin <fierykylin@gmail.com>
To: linux-scsi@vger.kernel.org
Subject: PCI express equipment
Date: Wed, 4 May 2005 19:51:12 +0800	[thread overview]
Message-ID: <87ab37ab05050404516a2bcc40@mail.gmail.com> (raw)

On one hand ,hardwarely,as it is always said, PCIE provides the
superexcellent performance

comparing with the PCI and PCI -X 
On the other ,softwarely,in most the application scenarios i have met
, the PCIE equipment will

have to use the pci-compatible driver first in linux.
because the Configuration head is pci compatible in the first 256 byte ,
it is allowed and really works. 
i know if we use the conventional Device Driver for pcie equipment,
the advanced option such as MSI ,Flow Control ,TC ,VC and hotplug are
unavailable, i also know

that the speed is mainly the problem of Bandwidth and Clocking. Still
i know that the Trafic

control mechanism is good for the arbitration and thus improve the
performance just like the

TCP protocol ways.
So my conclusion is :
the conventional Device driver will not be the bottle neck of the PCIE
performance as long as

only speed is concerned ,and the advanced options are only
Application-related.
here allow me just compare it with the network protocol ,
oh ,i just use the IP protocol ,with out the TCP /UDP way.
is that right ?or any wise can give some advice and  


-- 
we who r about to die,salute u!

             reply	other threads:[~2005-05-04 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 11:51 kylin [this message]
2005-05-04 12:14 ` PCI express equipment Matthew Wilcox
2005-05-04 16:28   ` kylin

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=87ab37ab05050404516a2bcc40@mail.gmail.com \
    --to=fierykylin@gmail.com \
    --cc=linux-scsi@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 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.