All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Jan Mędala" <jan@semihalf.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com,
	Alexander Matushevsky <matua@amazon.com>,
	Jakub Palider <jpa@semihalf.com>
Subject: Re: [PATCH v3 3/6] ena: disable readless communication regarding to HW revision
Date: Tue, 5 Jul 2016 16:47:34 +0100	[thread overview]
Message-ID: <20160705154734.GA26504@bricha3-MOBL3> (raw)
In-Reply-To: <CANw_3ZdD=ABrZLxFK_9ifdgmp98LrKf1W6pC_jX9vaZJh1-NSA@mail.gmail.com>

On Tue, Jul 05, 2016 at 12:02:41PM +0200, Jan Mędala wrote:
> Bruce,
> 
> Here's explanation of readless communication (on behalf of Alex):
> 
> > "readless" refers to ability to read ENA registers without actually
> > issuing read request from host (x86).
> > Instead, host programs 2 registers on device that trigger DMA from device
> > to host and report register value.
> > However, this functionality is not going to be available in all type of
> > devices. The decision if this mode is supported or not , is taken from
> > revision_id in pci configuration space.
> 
> 

Thanks, I'll add this into the commit message to help explain things to anyone
looking at the commit later.

/Bruce

> Regards
> 
>   Jan
> 
> 2016-07-04 17:43 GMT+02:00 Bruce Richardson <bruce.richardson@intel.com>:
> 
> > On Thu, Jun 30, 2016 at 05:04:56PM +0200, Jan Medala wrote:
> > > Depending on HW revision readless communcation between host and device
> > > may be unavailable.
> > > In that case prevent PMD of seting up readless communication mechanism.
> > >
> > The idea of readless communication is a strange one. Can you provide a bit
> > more detail as to what "readless communication" refers to.
> >
> > /Bruce
> >

  reply	other threads:[~2016-07-05 15:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16 17:54 [PATCH] ena: Update PMD to cooperate with latest ENA firmware Jan Medala
2016-06-20 16:16 ` Ferruh Yigit
2016-06-21 12:05 ` [PATCH v2 0/6] ena: update " Jan Medala
2016-06-21 12:05   ` [PATCH v2 1/6] ena: update of ENA communication layer Jan Medala
2016-06-21 12:05   ` [PATCH v2 2/6] ena: add debug area and host information Jan Medala
2016-06-21 12:06   ` [PATCH v2 3/6] ena: disable readless communication regarding to HW revision Jan Medala
2016-06-21 12:06   ` [PATCH v2 4/6] ena: allocate coherent memory in node-aware way Jan Medala
2016-06-21 12:06   ` [PATCH v2 5/6] ena: fix memory management issue Jan Medala
2016-06-30 15:04     ` [PATCH v3 0/6] ena: update PMD to cooperate with latest ENA firmware Jan Medala
2016-06-30 15:04       ` [PATCH v3 1/6] ena: update of ENA communication layer Jan Medala
2016-06-30 15:04       ` [PATCH v3 2/6] ena: add debug area and host information Jan Medala
2016-06-30 15:04       ` [PATCH v3 3/6] ena: disable readless communication regarding to HW revision Jan Medala
2016-07-04 15:43         ` Bruce Richardson
2016-07-05 10:02           ` Jan Mędala
2016-07-05 15:47             ` Bruce Richardson [this message]
2016-06-30 15:04       ` [PATCH v3 4/6] ena: allocate coherent memory in node-aware way Jan Medala
2016-06-30 15:04       ` [PATCH v3 5/6] ena: fix memory management issue Jan Medala
2016-07-04 16:27         ` Bruce Richardson
2016-07-05 16:13           ` Bruce Richardson
2016-07-05 17:03             ` Jan Mędala
2016-07-05 17:03             ` Jan Mędala
2016-06-30 15:04       ` [PATCH v3 6/6] ena: fix for icc compiler Jan Medala
2016-07-05  8:52         ` Ferruh Yigit
2016-07-05 16:19           ` Bruce Richardson
2016-07-05 17:03             ` Jan Mędala
2016-07-05 17:04               ` Jan Mędala
2016-07-05 17:10                 ` Jan Mędala
2016-07-06  8:14                   ` Bruce Richardson
2016-07-06  8:50                     ` Jan Mędala
2016-07-08 13:23           ` Bruce Richardson
2016-07-08 14:07             ` Ferruh Yigit
2016-07-08 13:24       ` [PATCH v3 0/6] ena: update PMD to cooperate with latest ENA firmware Bruce Richardson
2016-06-21 12:06   ` [PATCH v2 6/6] ena: fix for icc compiler Jan Medala
2016-06-24 11:52   ` [PATCH v2 0/6] ena: update PMD to cooperate with latest ENA firmware Bruce Richardson
2016-06-29 11:01     ` Bruce Richardson
2016-06-29 11:31       ` Jan Mędala
2016-06-29 12:28         ` Bruce Richardson

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=20160705154734.GA26504@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jan@semihalf.com \
    --cc=jpa@semihalf.com \
    --cc=matua@amazon.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.