From: Johannes Berg <johannes@sipsolutions.net>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: "Yu, Fenghua" <fenghua.yu@intel.com>,
David Woodhouse <dwmw2@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
"Zhu, Yi" <yi.zhu@intel.com>, Chris Wright <chrisw@sous-sol.org>,
LKML <linux-kernel@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>
Subject: RE: [PATCH]iwlan dma mapping read and write changes
Date: Wed, 11 Feb 2009 22:50:07 +0100 [thread overview]
Message-ID: <1234389007.16004.55.camel@johannes.local> (raw)
In-Reply-To: <1234388845.16004.53.camel@johannes.local>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On Wed, 2009-02-11 at 22:47 +0100, Johannes Berg wrote:
> > >> Indeed the firmware/ucode write back to host memory to update retry
> > >> counter for APMDU packets. I'm not sure if this is needed for legacy
> > >> traffic, though.
> > >
> > >I don't think they can be seeing AMPDU packets since that is, well,
> > >broken?
> >
> > Currently I'm not aware of any other cases where memory is accessed
> > back but I may have not complete info. Will be back with the answer
> > tomorrow.
>
> I don't think it really matters, since AMPDU packets will be fixed soon,
> and for those you know it's necessary (and the report says that under
> some other circumstances it's also necessary). Unless there'd be some
> benefit from using BIDI only when we know it'll be needed, and using
> TODEV in the other cases?
Or if there's a firmware bug.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-02-11 21:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 16:56 [PATCH 0/2]Add Variable Page Size and IA64 Support in Intel IOMMU Fenghua Yu
2008-10-03 15:50 ` Bjorn Helgaas
2008-10-06 19:44 ` Yu, Fenghua
2008-10-07 0:01 ` [PATCH V2 0/2] Add " Fenghua Yu
2009-02-11 18:26 ` [PATCH]iwlan dma mapping read and write changes Fenghua Yu
2009-02-11 18:35 ` Bhavesh Davda
2009-02-11 19:29 ` Yu, Fenghua
2009-02-11 18:59 ` Chris Wright
2009-02-11 21:27 ` Winkler, Tomas
2009-02-11 21:33 ` Johannes Berg
2009-02-11 21:41 ` Winkler, Tomas
2009-02-11 21:47 ` Johannes Berg
2009-02-11 21:50 ` Johannes Berg [this message]
2009-02-11 22:10 ` Winkler, Tomas
2009-02-11 22:13 ` Yu, Fenghua
2009-02-11 22:13 ` David Woodhouse
2009-02-12 13:42 ` Winkler, Tomas
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=1234389007.16004.55.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=chrisw@sous-sol.org \
--cc=dwmw2@infradead.org \
--cc=emmanuel.grumbach@intel.com \
--cc=fenghua.yu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tomas.winkler@intel.com \
--cc=yi.zhu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®