From: Bruce Richardson <bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Tetsuya Mukawa <mukawa-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [RFC PATCH] lib/librte_ethdev: Expand port identifier
Date: Wed, 18 Feb 2015 12:31:59 +0000 [thread overview]
Message-ID: <20150218123159.GC5960@bricha3-MOBL3> (raw)
In-Reply-To: <20150218123006.GB5960@bricha3-MOBL3>
On Wed, Feb 18, 2015 at 12:30:07PM +0000, Bruce Richardson wrote:
> On Wed, Feb 18, 2015 at 08:02:49PM +0900, Tetsuya Mukawa wrote:
> > Currently uint8_t is used for port identifier. This patch changes it,
> > and use uint16_t as port identifier.
> > This patch only changes ethdev library. ABI of the library will be
> > kept even after applying it.
> >
> > Also, this patch involves following fixes.
> > - Use "port_id" as variable name instead of "port".
> >
> >
> > Signed-off-by: Tetsuya Mukawa <mukawa-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org>
> > ---
> > lib/librte_ether/rte_ethdev.c | 212 +-
> > lib/librte_ether/rte_ethdev_internal.h | 3672 ++++++++++++++++++++++++++++++++
> > 2 files changed, 3778 insertions(+), 106 deletions(-)
> > create mode 100644 lib/librte_ether/rte_ethdev_internal.h
> >
> I'm not sure I follow why we need a new header file for this.
> Also, thinking about this change, a more fundamental problem is going to be
> the mbuf structure, which stores a port id inside it in an 8-bit value.
> Upgrading that to a 16-bit value requires some thought, and verification to
> ensure any adjustment of fields does not lead to serious performance issues.
>
> Therefore, I suggest we leave the port id values as 8-bits until such time
> as we need greater than 255 port values in a real-world use case.
> Out of interest - anyone have a DPDK app where they use >16 port id values? If
> so, how high does the port id value get?
>
> Regards,
> /Bruce
>
Resending with correct email addr for Neil.
/Bruce
next prev parent reply other threads:[~2015-02-18 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 11:02 [RFC PATCH] lib/librte_ethdev: Expand port identifier Tetsuya Mukawa
[not found] ` <1424257369-19130-1-git-send-email-mukawa-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.org>
2015-02-18 12:30 ` Bruce Richardson
2015-02-18 12:31 ` Bruce Richardson [this message]
2015-02-18 13:05 ` Wodkowski, PawelX
[not found] ` <F6F2A6264E145F47A18AB6DF8E87425D12BAA717-kPTMFJFq+rFP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-02-18 14:10 ` Bruce Richardson
2015-02-18 13:10 ` Marc Sune
[not found] ` <54E48F58.6080909-kpkqNMk1I7M@public.gmane.org>
2015-02-18 13:49 ` Bruce Richardson
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=20150218123159.GC5960@bricha3-MOBL3 \
--to=bruce.richardson-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=mukawa-AlSX/UN32fvPDbFq/vQRIQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.