From: Pawel Wodkowski <pawelx.wodkowski@intel.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Vlad Zolotarov <vladz@cloudius-systems.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5 1/3] ixgbe: Cleanups
Date: Mon, 09 Mar 2015 12:09:14 +0100 [thread overview]
Message-ID: <54FD7F5A.4090809@intel.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB977258213F4B37@irsmsx105.ger.corp.intel.com>
On 2015-03-09 11:49, Ananyev, Konstantin wrote:
>
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Vlad Zolotarov
>> Sent: Monday, March 09, 2015 10:21 AM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] [PATCH v5 1/3] ixgbe: Cleanups
>>
>> - Removed the not needed casting.
>> - ixgbe_dev_rx_init(): shorten the lines by defining a local alias variable to access
>> &dev->data->dev_conf.rxmode.
>>
>> Signed-off-by: Vlad Zolotarov <vladz@cloudius-systems.com>
>> ---
>> lib/librte_pmd_ixgbe/ixgbe_rxtx.c | 27 ++++++++++++---------------
>> 1 file changed, 12 insertions(+), 15 deletions(-)
>>
>> diff --git a/lib/librte_pmd_ixgbe/ixgbe_rxtx.c b/lib/librte_pmd_ixgbe/ixgbe_rxtx.c
>> index 72c65df..609b5fd 100644
>> --- a/lib/librte_pmd_ixgbe/ixgbe_rxtx.c
>> +++ b/lib/librte_pmd_ixgbe/ixgbe_rxtx.c
>> @@ -1032,8 +1032,7 @@ ixgbe_rx_alloc_bufs(struct igb_rx_queue *rxq)
>> int diag, i;
>>
>> /* allocate buffers in bulk directly into the S/W ring */
>> - alloc_idx = (uint16_t)(rxq->rx_free_trigger -
>> - (rxq->rx_free_thresh - 1));
>> + alloc_idx = rxq->rx_free_trigger - (rxq->rx_free_thresh - 1);
>
> I think all these extra casts came in to keep icc 12.* compiling without warnings.
> I am agree that they are unnecessary.
> Though if we still have to support icc 12.* we either need to keep them, or find
> some other way to keep it happy.
> Konstantin
>
What warnings icc 12.* is throwing? Only warning I can think of here is
signed -> unsigned implicit cast. Changing '1' to '1U' helps?
--
Pawel
next prev parent reply other threads:[~2015-03-09 11:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 10:20 [dpdk-dev] [PATCH v5 0/3]This series adds the missing flow for enabling the LRO in the ethdev and Vlad Zolotarov
2015-03-09 10:20 ` [dpdk-dev] [PATCH v5 1/3] ixgbe: Cleanups Vlad Zolotarov
2015-03-09 10:49 ` Ananyev, Konstantin
2015-03-09 11:09 ` Pawel Wodkowski [this message]
2015-03-09 11:29 ` Ananyev, Konstantin
2015-03-09 15:57 ` Vlad Zolotarov
2015-03-09 16:39 ` Ananyev, Konstantin
2015-03-09 17:13 ` Vladislav Zolotarov
2015-03-09 18:00 ` Mcnamara, John
2015-03-09 18:21 ` Vladislav Zolotarov
2015-03-09 18:21 ` Vladislav Zolotarov
[not found] ` <2601191342CEEE43887BDE71AB977258213F4F13@irsmsx105.ger.corp.intel.com>
2015-03-09 19:13 ` Ananyev, Konstantin
2015-03-09 19:32 ` Vlad Zolotarov
2015-03-09 19:36 ` Ananyev, Konstantin
2015-03-09 12:53 ` Vlad Zolotarov
2015-03-09 10:20 ` [dpdk-dev] [PATCH v5 2/3] ixgbe: Code refactoring Vlad Zolotarov
2015-03-09 10:20 ` [dpdk-dev] [PATCH v5 3/3] ixgbe: Add LRO support Vlad Zolotarov
2015-03-09 10:46 ` [dpdk-dev] [PATCH v5 0/3]This series adds the missing flow for enabling the LRO in the ethdev and Vlad Zolotarov
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=54FD7F5A.4090809@intel.com \
--to=pawelx.wodkowski@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=vladz@cloudius-systems.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).