From: "Qiu, Michael" <michael.qiu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
David Marchand <david.marchand@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] Fix rte_is_power_of_2
Date: Mon, 19 Jan 2015 09:30:30 +0000 [thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E60286CB74C5@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <7022282.sJULtgJP1R@xps13>
On 2015/1/19 17:14, Thomas Monjalon wrote:
> 2015-01-19 08:21, David Marchand:
>> On Mon, Jan 19, 2015 at 3:45 AM, Zhang, Helin <helin.zhang@intel.com> wrote:
>>
>>> It seems that your fix result in cannot launching applications.
>>> I don't suspect the correction of your fix, but somewhere else needs to be
>>> corrected together with your fix.
>>>
>>> Logs:
>>> /************************************************************
>>> RING: Cannot reserve memory for tailq
>> I have a quick fix for this one (rte_malloc_socket refuses 0 alignment),
>> but looking at the change, I would say there are a lot of places to be
>> checked.
>> Were those places checked during review ?
> http://dpdk.org/browse/dpdk/commit/?id=2fc8d6daa4c7a
> This case demonstrates that an Acked-by line is not always sufficient
> to apply a patch.
>
>> Kerur, did you run a make test ?
>> All tests fail for me because of rte_malloc_socket.
> My dream would be to have a machine receiving patches, applying them in a sandbox,
> run some basic tests and reports failures.
This could be, but I hope every contributor could do basic check like
build and run of at lease one app like test-pmd, then it will reduce
most of failure we faced.
Then I think we can have one next branch, all patches first been
reviewed and basic verified then applied to next, after all tested then
merge to master(more stable)
Then all the release could based on master branch, it also could avoid
lots of unstable RC release(like compile error we see before, it should
not happen in RC release in my mind).
Thanks,
Michael
>
> It should be fixed now:
> http://dpdk.org/browse/dpdk/commit/?id=8e3e06501660
>
next prev parent reply other threads:[~2015-01-19 9:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 15:28 Ravi Kerur
2014-12-27 15:30 ` Ravi Kerur
2014-12-27 20:49 ` Neil Horman
2015-01-15 13:12 ` Thomas Monjalon
2015-01-19 2:45 ` Zhang, Helin
2015-01-19 7:21 ` David Marchand
2015-01-19 9:13 ` Thomas Monjalon
2015-01-19 9:30 ` Qiu, Michael [this message]
2015-01-19 9:49 ` David Marchand
2015-01-19 10:02 ` Qiu, Michael
2015-01-19 10:07 ` Qiu, Michael
2015-01-19 17:07 ` Ravi Kerur
2015-01-19 22:07 ` Ravi Kerur
2015-01-19 9:14 ` De Lara Guarch, Pablo
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=533710CFB86FA344BFBF2D6802E60286CB74C5@SHSMSX101.ccr.corp.intel.com \
--to=michael.qiu@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).