From: Olivier MATZ <olivier.matz@6wind.com>
To: "Gilmore, Walter E" <walter.e.gilmore@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH RFC 03/11] mbuf: remove rte_ctrlmbuf
Date: Mon, 26 May 2014 14:23:00 +0200 [thread overview]
Message-ID: <53833224.50903@6wind.com> (raw)
In-Reply-To: <DC16335EE7FE114791FFF955B21EDB44940EF02A@ORSMSX105.amr.corp.intel.com>
Hi Walt,
> The purpose of this structure is to send commands, events or any other type
> of information between user application tasks (normally from a manager
> task). It has been there since the beginning in the original design and
> it's up to the user to define what is in the data field and how they
> wish to use it. It's one thing to fix a bug but to remove a structure
> like this because you don't see it use in the other parts is asking for
> trouble with customers.
To me, there is nothing that we cannot do without this structure:
depending on the use-case, it could be replaced with the same
functionalities by:
- a packet mbuf, in this case the user pointer would be stored in
the packet data for instance. In the worst case, I would agree to
add a flag telling that the mbuf carries control data.
- an application private structure which would contain the pointer,
the data len (if any), plus any other field that could be useful
for the application. This structure can be allocated in a mempool.
- nothing! I mean: if the application only wants to carry a pointer,
why would it need an additional structure to point to it? The
application can just give the pointer to its private data without
allocating a control mbuf for that.
To be honnest, I don't see in which case it is useful to have this
additional structure. This modification is motivated by a gain of
bytes in the mbuf and a rationalization of the rte_mbuf structure.
I can add a documentation, for instance in the commit log, about how
the rte_ctrlmbuf could be replaced by something equivalent in different
situations. Are you fine with this?
If we find use cases where rte_ctrlmbuf is required, another idea would
be to keep this structure, but make it independant of rte_mbuf.
Regards,
Olivier
next prev parent reply other threads:[~2014-05-26 12:22 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 14:50 [dpdk-dev] [PATCH RFC 00/11] ixgbe/mbuf: add TSO support Olivier Matz
2014-05-09 14:50 ` [dpdk-dev] [PATCH RFC 01/11] igb/ixgbe: fix IP checksum calculation Olivier Matz
2014-05-15 10:40 ` Ananyev, Konstantin
2014-05-09 14:50 ` [dpdk-dev] [PATCH RFC 02/11] mbuf: rename RTE_MBUF_SCATTER_GATHER into RTE_MBUF_REFCNT Olivier Matz
2014-05-09 14:50 ` [dpdk-dev] [PATCH RFC 03/11] mbuf: remove rte_ctrlmbuf Olivier Matz
2014-05-25 21:39 ` Gilmore, Walter E
2014-05-26 12:23 ` Olivier MATZ [this message]
2014-05-26 16:40 ` Dumitrescu, Cristian
2014-05-26 22:43 ` Neil Horman
2014-05-27 0:17 ` Stephen Hemminger
2014-05-28 9:45 ` Ananyev, Konstantin
2014-05-09 14:50 ` [dpdk-dev] [PATCH RFC 04/11] mbuf: remove the rte_pktmbuf structure Olivier Matz
2014-05-09 14:50 ` [dpdk-dev] [PATCH RFC 05/11] mbuf: merge physaddr and buf_len in a bitfield Olivier Matz
2014-05-09 15:39 ` Shaw, Jeffrey B
2014-05-09 16:06 ` Olivier MATZ
2014-05-09 16:11 ` Shaw, Jeffrey B
2014-05-14 14:07 ` Ananyev, Konstantin
2014-05-15 9:53 ` Olivier MATZ
2014-05-19 7:27 ` Olivier MATZ
2014-05-19 8:25 ` Richardson, Bruce
2014-05-19 9:30 ` Olivier MATZ
2014-05-19 9:57 ` Richardson, Bruce
2014-05-09 14:50 ` [dpdk-dev] [PATCH RFC 06/11] mbuf: replace data pointer by an offset Olivier Matz
2014-05-12 14:12 ` Thomas Monjalon
2014-05-12 14:36 ` Venkatesan, Venky
2014-05-12 14:41 ` Neil Horman
2014-05-12 15:07 ` Olivier MATZ
2014-05-12 15:59 ` Stephen Hemminger
2014-05-12 16:13 ` Olivier MATZ
2014-05-12 17:13 ` Stephen Hemminger
2014-05-13 13:29 ` Olivier MATZ
2014-05-12 16:06 ` Venkatesan, Venky
2014-05-12 18:39 ` Neil Horman
2014-05-13 13:54 ` Venkatesan, Venky
2014-05-13 14:09 ` Thomas Monjalon
2014-05-09 14:50 ` [dpdk-dev] [PATCH RFC 07/11] mbuf: add functions to get the name of an ol_flag Olivier Matz
2014-05-09 14:50 ` [dpdk-dev] [PATCH RFC 08/11] mbuf: change ol_flags to 32 bits Olivier Matz
2014-05-09 14:50 ` [dpdk-dev] [PATCH RFC 09/11] mbuf: rename vlan_macip_len in hw_offload and increase its size Olivier Matz
2014-05-09 14:50 ` [dpdk-dev] [PATCH RFC 10/11] testpmd: modify source address to validate checksum calculation Olivier Matz
2014-05-09 14:50 ` [dpdk-dev] [PATCH RFC 11/11] ixgbe/mbuf: add TSO support Olivier Matz
2014-05-12 14:30 ` Thomas Monjalon
2014-05-15 15:09 ` Ananyev, Konstantin
2014-05-15 15:39 ` Olivier MATZ
2014-05-15 16:30 ` Ananyev, Konstantin
2014-05-16 12:11 ` Olivier MATZ
2014-05-16 17:01 ` Ananyev, Konstantin
2014-05-19 12:32 ` Thomas Monjalon
2014-05-09 17:04 ` [dpdk-dev] [PATCH RFC 00/11] " Stephen Hemminger
2014-05-09 21:49 ` Olivier MATZ
2014-05-10 0:39 ` Stephen Hemminger
2014-05-19 12:47 ` Thomas Monjalon
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=53833224.50903@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=walter.e.gilmore@intel.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).