All of lore.kernel.org
 help / color / mirror / Atom feed
From: Penigalapati, Sandeep <sandeep.penigalapati@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v6 1/9] ice: implement low level recipes functions
Date: Thu, 30 Sep 2021 09:04:58 +0000	[thread overview]
Message-ID: <MW3PR11MB4554696BCE4E7A93674E470C9CAA9@MW3PR11MB4554.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1628239746-17380-2-git-send-email-wojciech.drewek@intel.com>

>-----Original Message-----
>From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
>Wojciech Drewek
>Sent: Friday, August 6, 2021 2:19 PM
To: intel-wired-lan@lists.osuosl.org
>Subject: [Intel-wired-lan] [PATCH net-next v6 1/9] ice: implement low level
>recipes functions
>
>From: Grishma Kotecha <grishma.kotecha@intel.com>
>
>Add code to manage recipes and profiles on admin queue layer.
>
>Allow the driver to add a new recipe and update an existing one. Get a recipe
>and get a recipe to profile association is mostly used in update existing recipes
>code.
>
>Only default recipes can be updated. An update is done by reading recipes
>from HW, changing their params and calling add recipe command.
>
>Support following admin queue commands:
>- ice_aqc_opc_add_recipe (0x0290) - create a recipe with protocol header
>information and other details that determine how this recipe filter works
>- ice_aqc_opc_recipe_to_profile (0x0291) - associate a switch recipe to a
>profile
>- ice_aqc_opc_get_recipe (0x0292) - get details of an exsisting recipe
>- ice_aqc_opc_get_recipe_to_profile (0x0293) - get a recipe associated with
>profile ID
>
>Define ICE_AQC_RES_TYPE_RECIPE resource type to hold a switch recipe. It is
>needed when a new switch recipe needs to be created.
>
>Co-developed-by: Dan Nowlin <dan.nowlin@intel.com>
>Signed-off-by: Dan Nowlin <dan.nowlin@intel.com>
>Signed-off-by: Grishma Kotecha  <grishma.kotecha@intel.com>
>Signed-off-by: Wojciech Drewek <wojciech.drewek@intel.com>
>---
> drivers/net/ethernet/intel/ice/ice_adminq_cmd.h |  57 +++++++
> drivers/net/ethernet/intel/ice/ice_switch.c     | 213
>++++++++++++++++++++++++
> drivers/net/ethernet/intel/ice/ice_switch.h     |   9 +
> 3 files changed, 279 insertions(+)
>
Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>

  reply	other threads:[~2021-09-30  9:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06  8:48 [Intel-wired-lan] [PATCH net-next v1 0/9] advanced switch rule management Wojciech Drewek
2021-08-06  8:48 ` [Intel-wired-lan] [PATCH net-next v6 1/9] ice: implement low level recipes functions Wojciech Drewek
2021-09-30  9:04   ` Penigalapati, Sandeep [this message]
2021-08-06  8:48 ` [Intel-wired-lan] [PATCH net-next v6 2/9] ice: manage profiles and field vectors Wojciech Drewek
2021-09-30  9:04   ` Penigalapati, Sandeep
2021-08-06  8:49 ` [Intel-wired-lan] [PATCH net-next v6 3/9] ice: create advanced switch recipe Wojciech Drewek
2021-09-28  5:51   ` Penigalapati, Sandeep
2021-08-06  8:49 ` [Intel-wired-lan] [PATCH net-next v6 4/9] ice: allow adding advanced rules Wojciech Drewek
2021-09-30  4:56   ` Penigalapati, Sandeep
2021-08-06  8:49 ` [Intel-wired-lan] [PATCH net-next v6 5/9] ice: allow deleting " Wojciech Drewek
2021-09-30  4:57   ` Penigalapati, Sandeep
2021-08-06  8:49 ` [Intel-wired-lan] [PATCH net-next v6 6/9] ice: cleanup rules info Wojciech Drewek
2021-09-30  5:01   ` Penigalapati, Sandeep
2021-08-06  8:49 ` [Intel-wired-lan] [PATCH net-next v6 7/9] ice: Allow changing lan_en and lb_en on all kinds of filters Wojciech Drewek
2021-09-30  4:55   ` Penigalapati, Sandeep
2021-08-06  8:49 ` [Intel-wired-lan] [PATCH net-next v6 8/9] ice: ndo_setup_tc implementation for PF Wojciech Drewek
2021-09-30  4:53   ` Penigalapati, Sandeep
2021-08-06  8:49 ` [Intel-wired-lan] [PATCH net-next v6 9/9] ice: ndo_setup_tc implementation for PR Wojciech Drewek
2021-09-30  4:54   ` Penigalapati, Sandeep

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=MW3PR11MB4554696BCE4E7A93674E470C9CAA9@MW3PR11MB4554.namprd11.prod.outlook.com \
    --to=sandeep.penigalapati@intel.com \
    --cc=intel-wired-lan@osuosl.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.