I completely agree with Cristian here, instead of leaving to applications where
to place their meta data, we can provide a guidance by having this field about
placement of application meta while maintaining transparency on the contents of
application meta information.
Regards
Kannan Babu Ramia
Hi Olivier,
I agree that your suggested approach for application-dependent metadata makes
sense, in fact the two approaches work in exactly the same way (packet metadata
immediately after the regular mbuf), there is only a subtle difference, which
is related to defining consistent DPDK usage gu
Hi Bruce,
2014-09-16 11:18, Bruce Richardson:
> I'm just wondering what the expected timeline is for you starting to merge
> patches in for the 1.8 release? As you have
> probably seen, I have quite a number of outstanding patches submitted for
> mbufs, and I'm wonder when the "part 1" set,
> w
On Fri, Sep 12, 2014 at 02:05:23PM -0400, John W. Linville wrote:
> Ping? Are there objections to this patch from mid-July?
>
> John
>
Thomas, Where are you on this? It seems like if you don't have any objections
to this patch, it should go in, in ilght of the lack of further commentary.
Neil
Hi,
2014-08-21 10:04, Alejandro Lucero:
> Documentation and header files describe stat_idx parameter for
> rte_eth_dev_set_tx_queue_stats_mapping
> and
> rte_eth_dev_set_rx_queue_stats_mapping
> as
> The value must be in the range
> [0, RTE_MAX_ETHPORT_QUEUE_STATS_MAPS - 1]
This function should n
On Tue, Aug 26, 2014 at 4:12 PM, David Marchand
wrote:
> This patchset reworks the bonding pmd so that we don't need to modify the
> eal
> for this pmd to work.
>
> Basically, the arguments parsed at bond_init are stored in the bond private
> structure to be used at dev_configure time.
> If no ar
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Tuesday, September 16, 2014 3:20 PM
> To: Richardson, Bruce
> Cc: dev at dpdk.org
> Subject: Re: Patch merges for 1.8 release
>
> Hi Bruce,
>
> 2014-09-16 11:18, Bruce Richardson:
> > I'm just wonde
Hi all,
I am interested to hear if anyone here have had any luck running Valgrind on
DPDK applications?
I tried to use this some time ago, but Valgrind does not seem to work
together with hugepages ? or
I am doing something wrong ;-)
I would like to hear form anyone having success or fai
From: Reshma Pattan
Changes in V2:
Signed-off-by: Reshma Pattan
---
examples/distributor_app/main.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/examples/distributor_app/main.c b/examples/distributor_app/main.c
index fab8199..b064a3a 100644
--- a
From: Reshma Pattan
* support provided for command-line option portmask.
* removed -g option in make file
* spacing adjustment in header files inclusion in main.c
* removal of const +3 in delcarration of rte_mbuf inside
output_buffer structure declaration
Changes in V2:
From: Bruce Richardson
A new sample app that shows the usage of the distributor library. This
app works as follows:
* An RX thread runs which pulls packets from each ethernet port in turn
and passes those packets to worker using a distributor component.
* The workers take the packets in turn,
From: Reshma Pattan
A new sample app that shows the usage of the distributor library. This
app works as follows:
*An RX thread runs which pulls packets from each ethernet port in turn
and passes those packets to worker using a distributor component.
*The workers take the packets in turn, and de
Hi Thomas,
I'm just wondering what the expected timeline is for you starting to merge
patches in for the 1.8 release? As you have
probably seen, I have quite a number of outstanding patches submitted for
mbufs, and I'm wonder when the "part 1" set,
which by now has been pretty well reviewed and
Hi Haifeng:
Might be in the release after 1.8.
> -Original Message-
> From: Linhaifeng [mailto:haifeng.lin at huawei.com]
> Sent: Saturday, September 13, 2014 1:28 PM
> To: Xie, Huawei; dev at dpdk.org
> Subject: Re: [dpdk-dev] [RFC] lib/librte_vhost: qemu vhost-user support
> into DPDK vh
14 matches
Mail list logo