From: David Marchand <david.marchand@redhat.com>
To: "Yan, Xiaoping (NSB - CN/Hangzhou)" <xiaoping.yan@nokia-sbell.com>
Cc: Asaf Penso <asafp@nvidia.com>, "users@dpdk.org" <users@dpdk.org>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>
Subject: Re: mlx5 VF packet lost between rx_port_unicast_packets and rx_good_packets
Date: Mon, 18 Oct 2021 12:45:10 +0200 [thread overview]
Message-ID: <CAJFAV8zNxVMPnkLsvn679GTkuh+YmPRxwZMuuALXxtBVCozZpA@mail.gmail.com> (raw)
In-Reply-To: <a7548408aacb45988f8a989880b9a97c@nokia-sbell.com>
On Mon, Oct 18, 2021 at 11:28 AM Yan, Xiaoping (NSB - CN/Hangzhou)
<xiaoping.yan@nokia-sbell.com> wrote:
> I have cloned dpdk code from github
>
> [xiaopiya@fedora30 dpdk]$ git remote -v
> origin https://github.com/DPDK/dpdk.git (fetch)
> origin https://github.com/DPDK/dpdk.git (push)
>
> which tag should I use?
>
> Or do I have to download 20.11.3 from git.dpdk.org?
>
> Sorry, I don’t know the relation between https://github.com/DPDK and git.dpdk.org?
Github DPDK/dpdk repo is a replication of the main repo hosted on
dpdk.org servers.
The official git repos and releases tarballs are on dpdk.org servers.
The list of official releases tarballs is at: http://core.dpdk.org/download/
The main repo git is at: https://git.dpdk.org/dpdk/
The LTS/stable releases repo git is at: https://git.dpdk.org/dpdk-stable/
--
David Marchand
next prev parent reply other threads:[~2021-10-18 10:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 10:07 [dpdk-users] " Yan, Xiaoping (NSB - CN/Hangzhou)
2021-07-13 12:35 ` Asaf Penso
2021-07-26 4:52 ` Yan, Xiaoping (NSB - CN/Hangzhou)
[not found] ` <DM8PR12MB54940E42337767B960E6BD28CDA69@DM8PR12MB5494.namprd12.prod.outlook.com>
[not found] ` <16515cb8ebbb4e7d833914040fa5943f@nokia-sbell.com>
[not found] ` <df15fbaac9a644fa93c55e1cfbc9226b@nokia-sbell.com>
[not found] ` <DM8PR12MB5494A1A84DA28E47CCB7496ECDA99@DM8PR12MB5494.namprd12.prod.outlook.com>
[not found] ` <22e029bf2ae6407e910cb2dcf11d49ce@nokia-sbell.com>
[not found] ` <e8e7cf781dd444fa9648facfc824d4c9@nokia-sbell.com>
[not found] ` <4b0dd266b53541c7bc4964c29e24a0e6@nokia-sbell.com>
2021-09-30 8:05 ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-10-14 6:55 ` Asaf Penso
2021-10-14 9:33 ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-10-14 9:50 ` Asaf Penso
2021-10-14 10:15 ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-10-14 11:48 ` Asaf Penso
2021-10-18 9:28 ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-10-18 10:45 ` David Marchand [this message]
2021-10-27 6:17 ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-10-27 7:26 ` David Marchand
2021-10-27 7:54 ` Martin Weiser
2021-10-28 1:39 ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-10-28 1:58 ` Gerry Wan
2021-10-29 0:44 ` Yan, Xiaoping (NSB - CN/Hangzhou)
2021-11-10 23:53 Francesco Montorsi
[not found] ` <DM8PR12MB5494181EE59EA4018F71E57DCD949@DM8PR12MB5494.namprd12.prod.outlook.com>
2021-11-11 13:25 ` Francesco Montorsi
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=CAJFAV8zNxVMPnkLsvn679GTkuh+YmPRxwZMuuALXxtBVCozZpA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=asafp@nvidia.com \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=users@dpdk.org \
--cc=viacheslavo@nvidia.com \
--cc=xiaoping.yan@nokia-sbell.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;
as well as URLs for NNTP newsgroup(s).