From: kylin <fierykylin@gmail.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-scsi@vger.kernel.org
Subject: Re: PCI express equipment
Date: Thu, 5 May 2005 00:28:17 +0800 [thread overview]
Message-ID: <87ab37ab05050409283d26dcab@mail.gmail.com> (raw)
In-Reply-To: <20050504121420.GH19678@parcelfarce.linux.theplanet.co.uk>
On 5/4/05, Matthew Wilcox <matthew@wil.cx> wrote:
> On Wed, May 04, 2005 at 07:51:12PM +0800, kylin wrote:
> > 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
>
> rubbish. MSI and Hotplug are independent of PCI Express and are used
> by conventional PCI drivers today. Flow control, TC and VC are all part
> of the same thing.
sorry for my innocence,but all i want to say here is if the unMSI and
unHotplug device driver would influence the normal speed in ONE
common scenarios
> > 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.
>
> Um, no, not really. There's very little hardware support for VC/TC at the
> moment, so having software support for it isn't a priority.
yeah ,even the bios will rarely support this
> In addition,
> it really depends how deep your PCI bus hierarchy is whether VC/TC will
> have any effect on performance at all.
have you seen the E7520 chipset ,sir?
> Why is this question on linux-scsi anyway?
because myu SCSI interface is connecting to the pcie bus:),love it and
love the dog :)
--
we who r about to die,salute u!
prev parent reply other threads:[~2005-05-04 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 11:51 PCI express equipment kylin
2005-05-04 12:14 ` Matthew Wilcox
2005-05-04 16:28 ` kylin [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=87ab37ab05050409283d26dcab@mail.gmail.com \
--to=fierykylin@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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