From: Joe Damato <jdamato@fastly.com> To: intel-wired-lan@lists.osuosl.org Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net, anthony.l.nguyen@intel.com, jesse.brandeburg@intel.com, maciej.fijalkowski@intel.com, sridhar.samudrala@intel.com, Joe Damato <jdamato@fastly.com> Subject: [next-queue v4 1/4] i40e: Store the irq number in i40e_q_vector Date: Fri, 7 Oct 2022 14:38:40 -0700 [thread overview] Message-ID: <1665178723-52902-2-git-send-email-jdamato@fastly.com> (raw) In-Reply-To: <1665178723-52902-1-git-send-email-jdamato@fastly.com> Make it easy to figure out the IRQ number for a particular i40e_q_vector by storing the assigned IRQ in the structure itself. Signed-off-by: Joe Damato <jdamato@fastly.com> Acked-by: Jesse Brandeburg <jesse.brandeburg@intel.com> Acked-by: Sridhar Samudrala <sridhar.samudrala@intel.com> --- drivers/net/ethernet/intel/i40e/i40e.h | 1 + drivers/net/ethernet/intel/i40e/i40e_main.c | 1 + 2 files changed, 2 insertions(+) diff --git a/drivers/net/ethernet/intel/i40e/i40e.h b/drivers/net/ethernet/intel/i40e/i40e.h index 9926c4e..8e1f395 100644 --- a/drivers/net/ethernet/intel/i40e/i40e.h +++ b/drivers/net/ethernet/intel/i40e/i40e.h @@ -992,6 +992,7 @@ struct i40e_q_vector { struct rcu_head rcu; /* to avoid race with update stats on free */ char name[I40E_INT_NAME_STR_LEN]; bool arm_wb_state; + int irq_num; /* IRQ assigned to this q_vector */ } ____cacheline_internodealigned_in_smp; /* lan device */ diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c index 6b7535a..6efe130 100644 --- a/drivers/net/ethernet/intel/i40e/i40e_main.c +++ b/drivers/net/ethernet/intel/i40e/i40e_main.c @@ -4123,6 +4123,7 @@ static int i40e_vsi_request_irq_msix(struct i40e_vsi *vsi, char *basename) } /* register for affinity change notifications */ + q_vector->irq_num = irq_num; q_vector->affinity_notify.notify = i40e_irq_affinity_notify; q_vector->affinity_notify.release = i40e_irq_affinity_release; irq_set_affinity_notifier(irq_num, &q_vector->affinity_notify); -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Joe Damato <jdamato@fastly.com> To: intel-wired-lan@lists.osuosl.org Cc: netdev@vger.kernel.org, Joe Damato <jdamato@fastly.com>, kuba@kernel.org, davem@davemloft.net Subject: [Intel-wired-lan] [next-queue v4 1/4] i40e: Store the irq number in i40e_q_vector Date: Fri, 7 Oct 2022 14:38:40 -0700 [thread overview] Message-ID: <1665178723-52902-2-git-send-email-jdamato@fastly.com> (raw) In-Reply-To: <1665178723-52902-1-git-send-email-jdamato@fastly.com> Make it easy to figure out the IRQ number for a particular i40e_q_vector by storing the assigned IRQ in the structure itself. Signed-off-by: Joe Damato <jdamato@fastly.com> Acked-by: Jesse Brandeburg <jesse.brandeburg@intel.com> Acked-by: Sridhar Samudrala <sridhar.samudrala@intel.com> --- drivers/net/ethernet/intel/i40e/i40e.h | 1 + drivers/net/ethernet/intel/i40e/i40e_main.c | 1 + 2 files changed, 2 insertions(+) diff --git a/drivers/net/ethernet/intel/i40e/i40e.h b/drivers/net/ethernet/intel/i40e/i40e.h index 9926c4e..8e1f395 100644 --- a/drivers/net/ethernet/intel/i40e/i40e.h +++ b/drivers/net/ethernet/intel/i40e/i40e.h @@ -992,6 +992,7 @@ struct i40e_q_vector { struct rcu_head rcu; /* to avoid race with update stats on free */ char name[I40E_INT_NAME_STR_LEN]; bool arm_wb_state; + int irq_num; /* IRQ assigned to this q_vector */ } ____cacheline_internodealigned_in_smp; /* lan device */ diff --git a/drivers/net/ethernet/intel/i40e/i40e_main.c b/drivers/net/ethernet/intel/i40e/i40e_main.c index 6b7535a..6efe130 100644 --- a/drivers/net/ethernet/intel/i40e/i40e_main.c +++ b/drivers/net/ethernet/intel/i40e/i40e_main.c @@ -4123,6 +4123,7 @@ static int i40e_vsi_request_irq_msix(struct i40e_vsi *vsi, char *basename) } /* register for affinity change notifications */ + q_vector->irq_num = irq_num; q_vector->affinity_notify.notify = i40e_irq_affinity_notify; q_vector->affinity_notify.release = i40e_irq_affinity_release; irq_set_affinity_notifier(irq_num, &q_vector->affinity_notify); -- 2.7.4 _______________________________________________ Intel-wired-lan mailing list Intel-wired-lan@osuosl.org https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-10-07 21:39 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-07 21:38 [next-queue v4 0/4] Add an i40e_napi_poll tracepoint Joe Damato 2022-10-07 21:38 ` [Intel-wired-lan] " Joe Damato 2022-10-07 21:38 ` Joe Damato [this message] 2022-10-07 21:38 ` [Intel-wired-lan] [next-queue v4 1/4] i40e: Store the irq number in i40e_q_vector Joe Damato 2022-10-14 3:56 ` G, GurucharanX 2022-10-14 3:56 ` G, GurucharanX 2022-10-07 21:38 ` [next-queue v4 2/4] i40e: Record number TXes cleaned during NAPI Joe Damato 2022-10-07 21:38 ` [Intel-wired-lan] " Joe Damato 2022-10-14 3:54 ` G, GurucharanX 2022-10-14 3:54 ` G, GurucharanX 2022-10-07 21:38 ` [next-queue v4 3/4] i40e: Record number of RXes " Joe Damato 2022-10-07 21:38 ` [Intel-wired-lan] " Joe Damato 2022-10-14 3:55 ` G, GurucharanX 2022-10-14 3:55 ` G, GurucharanX 2022-10-07 21:38 ` [next-queue v4 4/4] i40e: Add i40e_napi_poll tracepoint Joe Damato 2022-10-07 21:38 ` [Intel-wired-lan] " Joe Damato 2022-10-14 3:56 ` G, GurucharanX 2022-10-14 3:56 ` G, GurucharanX
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=1665178723-52902-2-git-send-email-jdamato@fastly.com \ --to=jdamato@fastly.com \ --cc=anthony.l.nguyen@intel.com \ --cc=davem@davemloft.net \ --cc=intel-wired-lan@lists.osuosl.org \ --cc=jesse.brandeburg@intel.com \ --cc=kuba@kernel.org \ --cc=maciej.fijalkowski@intel.com \ --cc=netdev@vger.kernel.org \ --cc=sridhar.samudrala@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: linkBe 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.