From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
Ilya Maximets <i.maximets@samsung.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Zhang, Helin" <helin.zhang@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Heetae Ahn <heetae82.ahn@samsung.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Subject: Re: [dpdk-dev] [PATCH RFC 0/2] Allow vectorized Rx with 4096 desc ring size on Intel NICs.
Date: Fri, 6 Jan 2017 02:29:18 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810CC3F98@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <0110a9dd-d89b-2cc2-a623-4befa3ae95bf@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Wednesday, January 4, 2017 1:25 AM
> To: Thomas Monjalon <thomas.monjalon@6wind.com>; Ilya Maximets
> <i.maximets@samsung.com>
> Cc: dev@dpdk.org; Zhang, Helin <helin.zhang@intel.com>; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>;
> Heetae Ahn <heetae82.ahn@samsung.com>; Richardson, Bruce
> <bruce.richardson@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>
> Subject: Re: [dpdk-dev] [PATCH RFC 0/2] Allow vectorized Rx with 4096 desc ring
> size on Intel NICs.
>
> On 1/2/2017 3:40 PM, Thomas Monjalon wrote:
> > 2016-12-27 08:03, Ilya Maximets:
> >> Hello.
> >> Ferruh, Thomas, is there a chance for this to be accepted to 17.02?
> >> Maybe I should resend this patch-set without 'RFC' tag?
> >
> > Yes it should be integrated in 17.02.
> > Ferruh, any news?
> >
>
> I was waiting for a review from driver maintainers
The patch looks good me, both ixgbe and i40e.
Thanks, Ilya.
Another idea is like, now the memory zone can be freed now.
So maybe later, we don't need to reserve a maximum size for rx ring, and can change it when number of desc are changed.
next prev parent reply other threads:[~2017-01-06 2:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161019140725eucas1p1cb53318d974fb1152f1a7b571f328fd5@eucas1p1.samsung.com>
2016-10-19 14:07 ` Ilya Maximets
[not found] ` <CGME20161019140730eucas1p2b1cf9daba45bdbf915bb69b24a0a850f@eucas1p2.samsung.com>
2016-10-19 14:07 ` [dpdk-dev] [PATCH RFC 1/2] net/i40e: allow bulk alloc for the max size desc ring Ilya Maximets
2016-11-29 10:59 ` Ilya Maximets
2016-11-29 12:50 ` Ananyev, Konstantin
2016-11-29 13:06 ` Ilya Maximets
[not found] ` <CGME20161019140735eucas1p267bb4aa03547e70e5f13d78e2ffedcc4@eucas1p2.samsung.com>
2016-10-19 14:07 ` [dpdk-dev] [PATCH RFC 2/2] net/ixgbe: " Ilya Maximets
2016-11-29 10:59 ` Ilya Maximets
2016-10-19 14:30 ` [dpdk-dev] [PATCH RFC 0/2] Allow vectorized Rx with 4096 desc ring size on Intel NICs Ferruh Yigit
2016-11-21 13:53 ` Ferruh Yigit
2016-12-21 12:33 ` Ilya Maximets
2016-12-27 5:03 ` Ilya Maximets
2017-01-02 15:40 ` Thomas Monjalon
2017-01-03 17:24 ` Ferruh Yigit
2017-01-06 2:29 ` Wu, Jingjing [this message]
2017-01-06 13:56 ` Ferruh Yigit
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=9BB6961774997848B5B42BEC655768F810CC3F98@SHSMSX103.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=heetae82.ahn@samsung.com \
--cc=helin.zhang@intel.com \
--cc=i.maximets@samsung.com \
--cc=konstantin.ananyev@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=wenzhuo.lu@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).