From: Ilya Matveychikov <matvejchikov@gmail.com>
To: Olivier MATZ <olivier.matz@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mbuf: fix for incomplete nb_segs types change
Date: Mon, 13 Nov 2017 14:21:48 +0400 [thread overview]
Message-ID: <439F4392-C1E4-4DD5-A174-1418D3594C80@gmail.com> (raw)
In-Reply-To: <2FAC1B54-ACCA-439E-BE58-10007DB35E56@gmail.com>
> But I didn’t try to fix it everywhere in drivers as it may depends of the particular hardware - does it support more that uint8_t queues or not. So, I agree with you that maintainers should have a look on that change.
does it support more that uint8_t *segments*, not queues :-)
next prev parent reply other threads:[~2017-11-13 10:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 13:51 [dpdk-dev] [PATCH] mbuf: fix for incomplete nb_segs/port " Ilya Matveychikov
2017-11-09 23:26 ` Stephen Hemminger
2017-11-10 13:56 ` [dpdk-dev] [PATCH] mbuf: fix for incomplete nb_segs " Ilya V. Matveychikov
2017-11-13 10:10 ` Olivier MATZ
2017-11-13 10:18 ` Ilya Matveychikov
2017-11-13 10:21 ` Ilya Matveychikov [this message]
2017-11-13 10:33 ` Olivier MATZ
2017-11-14 5:09 ` Thomas Monjalon
2017-11-14 8:24 ` Olivier MATZ
2017-11-14 22:46 ` 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=439F4392-C1E4-4DD5-A174-1418D3594C80@gmail.com \
--to=matvejchikov@gmail.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.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).