nt, so dropped the ball on my end, sorry for
that. just revisited the places where we use RTE_MAX_MEMSEG_LISTS. it seems
it would be a bigger effort to make it a run-time configurable option
instead of a compile-time one.
--
[0] https://inbox.dpdk.org/dev/20211013205417.84119-3-tchai...@gmail.com/
[1] https://inbox.dpdk.org/dev/2642296.XfZ1dg20Xv@thomas/
--
Regards
Kefu Chai
change from "how many segments each segment can have" to
"how many segments each segment list can have".
Signed-off-by: Kefu Chai
---
doc/guides/prog_guide/env_abstraction_layer.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/d
RTE_MAX_MEMSEG_LISTS = 128 is not enough for many-core machines, in our
case, we need to increase it to 8192. so add an option so user can
override it.
Signed-off-by: Kefu Chai
---
config/meson.build | 1 +
config/rte_config.h | 1 -
meson_options.txt | 2 ++
3 files changed, 3 insertions
RTE_MBUF_REFCNT_ATOMIC = 0 is not necessary for applications like
Seastar, where it's safe to assume that the mbuf refcnt is only
updated by a single core only.
Signed-off-by: Kefu Chai
---
config/meson.build | 4 +++-
config/rte_config.h | 1 -
meson_options.txt | 2 ++
3 files chang
/atomic_mbuf_ref_counts/, and update the
title of the commit message accordingly
* explain the expected number of MEMSEG_LISTS in commit message.
* remove the empty line after the newly added option
v2:
* revise the commit message.
Kefu Chai (2):
build: add meson options of atomic_mbuf_ref_counts
build
On Mon, Sep 20, 2021 at 4:08 PM Bruce Richardson
wrote:
>
> On Mon, Sep 20, 2021 at 03:51:06PM +0800, kefu chai wrote:
> > hello Bruce,
> >
> > do you have any further concerns? is there anything i can do to move
> > this forward?
> >
> > cheers,
>
hello Bruce,
do you have any further concerns? is there anything i can do to move
this forward?
cheers,
On Thu, Sep 9, 2021 at 12:51 AM Kefu Chai wrote:
>
> RTE_MAX_MEMSEG_LISTS = 128 is not enough for high-memory machines, in our
> case, we need to increase it to 8192. so add an
h for high-memory machines, in our case,
total: 0 errors, 1 warnings, 35 lines checked
Signed-off-by: Kefu Chai
---
config/meson.build | 5 -
config/rte_config.h | 2 --
meson_options.txt | 4
3 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/config/meson.build b/c
by a single
core only.
---
v3:
* s/mbuf_refcnt_atomic/atomic_mbuf_ref_counts/, and update the
title of the commit message accordingly
* explain the expected number of MEMSEG_LISTS in commit message.
* remove the empty line after the newly added option
Signed-off-by: Kefu Chai
---
c
e the commit message.
Signed-off-by: Kefu Chai
---
config/meson.build | 5 -
config/rte_config.h | 2 --
meson_options.txt | 5 +
3 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/config/meson.build b/config/meson.build
index 3b5966ec2f..72dd461198 100644
--- a/config/meson.
RTE_MAX_MEMSEG_LISTS = 128 is not enough for some use cases, so add an
option so user can override it.
RTE_MBUF_REFCNT_ATOMIC = 0 is enough for applications like Seastar,
where it's safe to assume that the mbuf refcnt is only updated by a single
core only.
Signed-off-by: Kefu Chai
---
c
otherwise the build fails with FreeBSD 12, like
In file included from contigmem.c:57:
/usr/srcs/head/src/sys/vm/vm_phys.h:122:10: error: use of undeclared
identifier 'vm_cnt'
return (vm_cnt.v_free_count += adj);
^
1 error generated.
*** Error code 1
Signed-of
+ Willem, he reported this issue
On Thu, Nov 30, 2017 at 5:56 PM, Bruce Richardson
wrote:
> On Thu, Nov 30, 2017 at 02:00:38PM +0800, kefu chai wrote:
>> otherwise the build fails with
>>
>> In file included from contigmem.c:57:
>> /usr/srcs/head/src/sys/vm/vm_p
otherwise the build fails with
In file included from contigmem.c:57:
/usr/srcs/head/src/sys/vm/vm_phys.h:122:10: error: use of undeclared
identifier 'vm_cnt'
return (vm_cnt.v_free_count += adj);
^
1 error generated.
*** Error code 1
Signed-off-by: Kefu Chai
14 matches
Mail list logo
