From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: [dpdk-dev] please help with reviews
Date: Wed, 21 Jun 2017 16:59:19 +0200 [thread overview]
Message-ID: <3141281.vjnBUAcREE@xps> (raw)
Hi,
During the last techboard meeting, it has been decided to call
more frequently for reviews by giving a list of hot patches.
For this first burst, I would like to highlight some important
patches in EAL and ethdev. The first EAL patches are all related
to NUMA. We have also some work around physical addresses,
and others to finalize the bus rework.
There are also some ethdev patches which require more eyes.
Please consider this list as important topics to close
as soon as possible. Thanks for helping.
eal: Set numa node value for system which not support it.
http://dpdk.org/patch/24212
eal: use get_mempolicy(2) to find numa socket on Linux
http://dpdk.org/patch/25417
eal: check if socket has memory reserved
http://dpdk.org/patch/25537
mem: balanced allocation of hugepages
http://dpdk.org/patch/25542
mem: fix malloc_elem resize with padding
http://dpdk.org/patch/25203
eal: don't advertise a physical address when no hugepages
http://dpdk.org/patch/25222
eal: add support for 24 40 and 48 bit operations
http://dpdk.org/patch/25367
[PATCH 00/10] Infrastructure to detect iova mapping on the bus
from Santosh Shukla
eal: remove vdev probe by dev args
http://dpdk.org/patch/24196
[PATCH v5 0/7] rte_bus parse API
from Gaetan Rivet
[PATCH v5 00/19] Generic devargs parsing
from Gaetan Rivet
eal/x86: rte pause implementation for x86
http://dpdk.org/patch/25052
timer: inform periodic timers of multiple expiries
http://dpdk.org/patch/24888
ethdev: add lock-less txq capability flag
http://dpdk.org/patch/23806
ethdev: add function to adjust number of descriptors
http://dpdk.org/patch/24587
ethdev: add fuzzy match in flow API
http://dpdk.org/patch/25292
reply other threads:[~2017-06-21 14:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3141281.vjnBUAcREE@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
/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).