DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: "Adrien Mazarguil" <adrien.mazarguil@6wind.com>,
	"Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 4/4] net/mlx4: add new Memory Region	support
Date: Thu, 10 May 2018 06:01:49 +0000	[thread overview]
Message-ID: <2F032BAA-5743-4DA6-96B6-BBDFDCE0CF69@mellanox.com> (raw)
In-Reply-To: <2DDD3185-6284-4BA3-A187-AED4C96407EB@mellanox.com>


> On May 9, 2018, at 8:00 PM, Yongseok Koh <yskoh@mellanox.com> wrote:
> 
> 
>> On May 9, 2018, at 4:12 PM, Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>> 
>> On 5/9/2018 12:09 PM, Yongseok Koh wrote:
>> <...>
>> 
>>> +/**
>>> + * Insert an entry to B-tree lookup table.
>>> + *
>>> + * @param bt
>>> + *   Pointer to B-tree structure.
>>> + * @param entry
>>> + *   Pointer to new entry to insert.
>>> + *
>>> + * @return
>>> + *   0 on success, -1 on failure.
>>> + */
>>> +static int
>>> +mr_btree_insert(struct mlx4_mr_btree *bt, struct mlx4_mr_cache *entry)
>>> +{
>>> +	struct mlx4_mr_cache *lkp_tbl;
>>> +	uint16_t idx = 0;
>>> +	size_t shift;
>>> +
>>> +	assert(bt != NULL);
>>> +	assert(bt->len <= bt->size);
>>> +	assert(bt->len > 0);
>>> +	lkp_tbl = *bt->table;
>>> +	/* Find out the slot for insertion. */
>>> +	if (mr_btree_lookup(bt, &idx, entry->start) != UINT32_MAX) {
>>> +		DEBUG("abort insertion to B-tree(%p):"
>>> +		      " already exist at idx=%u [0x%lx, 0x%lx) lkey=0x%x",
>>> +		      (void *)bt, idx, entry->start, entry->end, entry->lkey);
>> 
>> This and various other logs causing 32bits build error because of %lx usage. Can
>> you please check them?
>> 
>> I am feeling sad to complain a patch like this just because of log format issue,
>> we should find a solution to this issue as community, either checkpatch checks
>> or automated 32bit builds, I don't know.
> 
> Bummer. I have to change my bad habit of using %lx. And we will add 32-bit build
> check to our internal system to filter this kind of mistakes beforehand.
> 
> Will work with Shahaf to fix it and rebase next-net-mlx.

Ferruh, I've sent out a patch to Shahaf to change printing format specifiers and
Shahaf will squash it into the previous patches.

However, it seems we had stopped supporting 32-bit compilation since Nelio's
commit [1]

Not sure I'm doing right but I'm compiling it for T=i686-native-linuxapp-gcc and
still having a few more errors even except for my code. And even if I fix all of
the errors, linkage fails as explained in the commit message of [1].

Are you sure you encountered this 32b compilation issue for the first time?


[1] http://dpdk.org/browse/dpdk/commit/?id=ebbb81eb27daca0a89ee8f228fcf141d9eb6ef1c


Thanks,
Yongseok

  reply	other threads:[~2018-05-10  6:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 23:16 [dpdk-dev] [PATCH 0/5] net/mlx: " Yongseok Koh
2018-05-02 23:16 ` [dpdk-dev] [PATCH 1/5] net/mlx5: trim debug messages for reference counters Yongseok Koh
2018-05-06  6:37   ` Shahaf Shuler
2018-05-07 21:37     ` Yongseok Koh
2018-05-02 23:16 ` [dpdk-dev] [PATCH 2/5] net/mlx5: remove Memory Region support Yongseok Koh
2018-05-06  6:41   ` Shahaf Shuler
2018-05-02 23:16 ` [dpdk-dev] [PATCH 3/5] net/mlx5: add new " Yongseok Koh
2018-05-03  8:21   ` Burakov, Anatoly
2018-05-06 12:53   ` Shahaf Shuler
2018-05-08  1:52     ` Yongseok Koh
2018-05-02 23:16 ` [dpdk-dev] [PATCH 4/5] net/mlx4: remove " Yongseok Koh
2018-05-02 23:16 ` [dpdk-dev] [PATCH 5/5] net/mlx4: add new " Yongseok Koh
2018-05-09 11:09 ` [dpdk-dev] [PATCH v2 0/4] net/mlx: " Yongseok Koh
2018-05-09 11:09   ` [dpdk-dev] [PATCH v2 1/4] net/mlx5: remove " Yongseok Koh
2018-05-09 12:03     ` Shahaf Shuler
2018-05-09 11:09   ` [dpdk-dev] [PATCH v2 2/4] net/mlx5: add new " Yongseok Koh
2018-05-09 11:09   ` [dpdk-dev] [PATCH v2 3/4] net/mlx4: remove " Yongseok Koh
2018-05-09 11:09   ` [dpdk-dev] [PATCH v2 4/4] net/mlx4: add new " Yongseok Koh
2018-05-09 23:12     ` Ferruh Yigit
2018-05-10  3:00       ` Yongseok Koh
2018-05-10  6:01         ` Yongseok Koh [this message]
2018-05-10 19:29           ` Ferruh Yigit
2018-05-15  9:00             ` Nélio Laranjeiro

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=2F032BAA-5743-4DA6-96B6-BBDFDCE0CF69@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=nelio.laranjeiro@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).