DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] config files maintenance
Date: Fri, 31 Jul 2015 16:34:54 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A8B84F3@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1508851.EJxvAFadW3@xps13>



> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Friday, July 31, 2015 8:43 AM
> To: Zhang, Helin
> Cc: Ananyev, Konstantin; Richardson, Bruce; dev@dpdk.org
> Subject: Re: config files maintenance
> 
> 2015-07-31 15:39, Zhang, Helin:
> > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > > 2015-07-31 15:29, Zhang, Helin:
> > > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > > > > Can we remove i40e bulk alloc option?
> > > >
> > > > As the receiving functions are different for bulk_alloc or not, we need this
> flag.
> > >
> > > What brings the non bulk alloc function?
> >
> > Bulk-alloc means it will allocate mbufs in bulk, which was added
> > before we supporting Vector PMD long long ago, to show the possible better
> performance.
> > I think all was disabled by default, and later it is enabled by default for Linux.
> 
> Yes, I know that. My question was:
> Why not removing the non bulk alloc Rx in i40e?
> Who needs to disable I40E_RX_ALLOW_BULK_ALLOC?
> 
> I think you understand that the goal is remove some options and code useless
> nowadays (maintenance stuff).

I remember that last time somebody else were discussing about removing that,
but finally gave up. Let me find out why they gave up, and then see if we can remove it later.

Thanks,
Helin

  reply	other threads:[~2015-07-31 16:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 15:08 Thomas Monjalon
2015-07-31 15:29 ` Zhang, Helin
2015-07-31 15:31   ` Thomas Monjalon
2015-07-31 15:39     ` Zhang, Helin
2015-07-31 15:43       ` Thomas Monjalon
2015-07-31 16:34         ` Zhang, Helin [this message]
2015-07-31 15:41 ` Ananyev, Konstantin
2015-07-31 20:45 ` Thomas Monjalon
2015-07-31 21:11 ` [dpdk-dev] [PATCH 0/3] sync linux/bsd config options Thomas Monjalon
2015-07-31 21:11   ` [dpdk-dev] [PATCH 1/3] ixgbe: fix offload config option name Thomas Monjalon
2015-07-31 21:11   ` [dpdk-dev] [PATCH 2/3] config: enable same drivers options for linux and bsd Thomas Monjalon
2015-07-31 21:11   ` [dpdk-dev] [PATCH 3/3] config: remove kni options for bsd Thomas Monjalon
2015-07-31 21:24     ` Zhang, Helin
2015-08-03 10:44   ` [dpdk-dev] [PATCH 0/3] sync linux/bsd config options 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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A8B84F3@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@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).