From: Arjan van de Ven <arjan@infradead.org>
To: Steve Wise <swise@opengridcomputing.com>
Cc: rdreier@cisco.com, mshefty@ichips.intel.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
openib-general@openib.org
Subject: Re: [PATCH v3 1/7] AMSO1100 Low Level Driver.
Date: Fri, 23 Jun 2006 16:04:31 +0200 [thread overview]
Message-ID: <1151071471.3204.12.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1151071005.7808.39.camel@stevo-desktop>
On Fri, 2006-06-23 at 08:56 -0500, Steve Wise wrote:
> On Fri, 2006-06-23 at 15:48 +0200, Arjan van de Ven wrote:
> > > > > + /* Tell HW to xmit */
> > > > > + __raw_writeq(cpu_to_be64(mapaddr), elem->hw_desc + C2_TXP_ADDR);
> > > > > + __raw_writew(cpu_to_be16(maplen), elem->hw_desc + C2_TXP_LEN);
> > > > > + __raw_writew(cpu_to_be16(TXP_HTXD_READY), elem->hw_desc + C2_TXP_FLAGS);
> > > >
> > > > or here
> > > >
> > >
> > > No need here. This logic submits the packet for transmission. We don't
> > > assume it is transmitted until we (after a completion interrupt usually)
> > > read back the HTXD entry and see the TXP_HTXD_DONE bit set (see
> > > c2_tx_interrupt()).
> >
> > ... but will that interrupt happen at all if these 3 writes never hit
> > the hardware?
> >
>
> I thought the posted write WILL eventually get to adapter memory. Not
> stall forever cached in a bridge. I'm wrong?
I'm not sure there is a theoretical upper bound....
(and if it's several msec per bridge, then you have a lot of latency
anyway)
next prev parent reply other threads:[~2006-06-23 14:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 20:30 [PATCH v3 0/7][RFC] Ammasso 1100 iWARP Driver Steve Wise
2006-06-20 20:30 ` [PATCH v3 1/7] AMSO1100 Low Level Driver Steve Wise
2006-06-20 20:43 ` Arjan van de Ven
2006-06-21 16:32 ` Steve Wise
2006-06-21 17:13 ` Arjan van de Ven
2006-06-21 18:47 ` Steve Wise
2006-06-21 17:37 ` [openib-general] " Grant Grundler
2006-06-23 13:44 ` Steve Wise
2006-06-23 13:48 ` Arjan van de Ven
2006-06-23 13:56 ` Steve Wise
2006-06-23 14:04 ` Arjan van de Ven [this message]
2006-06-23 17:14 ` [openib-general] " Grant Grundler
2006-06-20 20:31 ` [PATCH v3 3/7] AMSO1100 OpenFabrics Provider Steve Wise
2006-06-20 20:31 ` [PATCH v3 4/7] AMSO1100 Memory Management Steve Wise
2006-06-20 20:31 ` [PATCH v3 5/7] AMSO1100 Message Queues Steve Wise
2006-06-20 20:31 ` [PATCH v3 6/7] AMSO1100: Privileged Verbs Queues Steve Wise
2006-06-20 20:31 ` [PATCH v3 7/7] AMSO1100 Makefiles and Kconfig changes Steve Wise
2006-06-20 21:00 ` [PATCH v3 2/7] AMSO1100 WR / Event Definitions Steve Wise
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=1151071471.3204.12.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mshefty@ichips.intel.com \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.com \
--cc=swise@opengridcomputing.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