From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
David Marchand <david.marchand@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 00/10] eal: rte_tailq api cleanup
Date: Thu, 12 Mar 2015 11:12:45 +0900 [thread overview]
Message-ID: <5500F61D.8060600@igel.co.jp> (raw)
In-Reply-To: <5500F46F.8020107@igel.co.jp>
On 2015/03/12 11:05, Tetsuya Mukawa wrote:
> On 2015/03/12 7:25, Mcnamara, John wrote:
>> From: David Marchand [mailto:david.marchand@6wind.com]
>> Sent: Wednesday, March 11, 2015 9:30 PM
>> To: Mcnamara, John
>> Cc: Tetsuya Mukawa; dev@dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH 00/10] eal: rte_tailq api cleanup
>>
>>>> I just tested the patch with testpmd and it fixes the previous issue.
>>> Ok, thanks, just for the record, can you add your setup ?
>>> linux / bsd, uio / vfio (if linux), which pmd ?
>> Hi David,
>>
>> I always complain when people don't send enough details in bug reports or updates, so sorry about that.
>>
>> Here we go, it is pretty vanilla but I sure you will get other data points by morning:
>>
>> $ uname -a
>> Linux sie-lab-214-036.ir.intel.com 3.6.10-4.fc18.x86_64
>> #1 SMP Tue Dec 11 18:01:27 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
>>
>> UIO with testpmd and skeleton forwarding app
>>
>> John.
>> --
>>
> Hi David,
>
> I've checked the patch on following environments, and make sure it works
> fine.
>
> - igb_uio:
> - vfio:
> - uio_pci_generic
> Tested on Ubuntu14.04 (3.13.0-30-generic) with e1000 PMD.
>
> - nic_uio
> Tested on FreeBSD 10.1-RELEASE #0 r274401 with e1000 PMD.
>
> Thanks,
> Tetsuya
>
Sorry for my bad English.
I've already made sure above.
Everything works fine with the patch on my environments.
Tetsuya
next prev parent reply other threads:[~2015-03-12 2:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 21:50 David Marchand
2015-03-04 21:50 ` [dpdk-dev] [PATCH 01/10] eal: remove yet another remaining reference to pm David Marchand
2015-03-04 21:50 ` [dpdk-dev] [PATCH 02/10] pci: use lookup tailq api David Marchand
2015-03-04 21:50 ` [dpdk-dev] [PATCH 03/10] tailq: remove unneeded inclusion of rte_tailq.h David Marchand
2015-03-04 21:50 ` [dpdk-dev] [PATCH 04/10] tailq: use a single cast macro David Marchand
2015-03-04 21:50 ` [dpdk-dev] [PATCH 05/10] tailq: get rid of broken "reserve" api David Marchand
2015-03-04 21:50 ` [dpdk-dev] [PATCH 06/10] tailq: remove unused RTE_EAL_TAILQ_* macros David Marchand
2015-03-04 21:50 ` [dpdk-dev] [PATCH 07/10] tailq: introduce dynamic register system David Marchand
2015-03-04 21:50 ` [dpdk-dev] [PATCH 08/10] tailq: move to dynamic tailq David Marchand
2015-03-04 21:50 ` [dpdk-dev] [PATCH 09/10] tailq: remove static slots David Marchand
2015-03-04 21:50 ` [dpdk-dev] [PATCH 10/10] eal: no need for E_RTE_NO_TAILQ anymore David Marchand
2015-03-04 22:55 ` [dpdk-dev] [PATCH 00/10] eal: rte_tailq api cleanup Thomas Monjalon
2015-03-06 0:26 ` Neil Horman
2015-03-10 11:20 ` Thomas Monjalon
2015-03-11 7:44 ` Tetsuya Mukawa
2015-03-11 8:47 ` David Marchand
2015-03-11 17:28 ` David Marchand
2015-03-11 20:24 ` Mcnamara, John
2015-03-11 21:29 ` David Marchand
2015-03-11 22:25 ` Mcnamara, John
2015-03-12 2:05 ` Tetsuya Mukawa
2015-03-12 2:12 ` Tetsuya Mukawa [this message]
2015-03-12 5:44 ` David Marchand
2015-03-12 8:38 ` Liu, Yong
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=5500F61D.8060600@igel.co.jp \
--to=mukawa@igel.co.jp \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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;
as well as URLs for NNTP newsgroup(s).