DPDK usage discussions
 help / color / mirror / Atom feed
From: Zhongming Qu <zhongming@luminatewireless.com>
To: users@dpdk.org
Subject: [dpdk-users] Do the two functions on 82599ES have independent registers?
Date: Tue, 23 Aug 2016 17:59:41 -0700	[thread overview]
Message-ID: <CADc8JchdMUgxga4KR5f=4xxHbQqNxyNcOtOkauRvWkJDVHZSsg@mail.gmail.com> (raw)

Hi,


Thanks in advance (Orz)!

Could someone quickly confirm that the two functions on a 82599ES nic have
independent BAR0-based registers or not?

For example, when running two primary dpdk processes, one of which uses
port0 and the other of which uses port1, writing to RDBAL[0] simultaneously
is a race condition or not?

The BAR0-based registers are mapped to different physical memories, as in:

```
lwr@dev5:~$ lspci -s 02:00.0 -xx -n -v
02:00.0 0200: 8086:10fb (rev 01)
    ....
    Memory at fbd80000 (64-bit, prefetchable) [size=512K]
    ...

lwr@dev5:~$ lspci -s 02:00.1 -xx -n -v
02:00.1 0200: 8086:10fb (rev 01)
    ...
    Memory at fbd00000 (64-bit, prefetchable) [size=512K]
    ...
```

Could these two physical addresses be mapped to actually the same PCI
address?


The 82599 data sheet says that the two ports have independent BAR's. But it
does not explicitly say that the two ports share the same rx/tx queue
registers or not. It does not, either, say that the 128 rx/tx queues are
per-port or shared by the two ports.

It has been really difficult to find relevant information outside of this
group. Thanks in advance!



Best,
Zhongming

                 reply	other threads:[~2016-08-24  0:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CADc8JchdMUgxga4KR5f=4xxHbQqNxyNcOtOkauRvWkJDVHZSsg@mail.gmail.com' \
    --to=zhongming@luminatewireless.com \
    --cc=users@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).