All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Stephen Hemminger
	<stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH v2] rte_ethdev: add link support flag
Date: Fri, 20 Jun 2014 15:06:48 +0200	[thread overview]
Message-ID: <4709584.nAXykbU3l6@xps13> (raw)
In-Reply-To: <20140619151238.28b9bbea-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>

Hi Stephen,

2014-06-19 15:12, Stephen Hemminger:
> Only some devices support the link state interrupt configuration option.
> Link state control does not work in virtual drivers
> (virtio, vmxnet3, igbvf, and ixgbevf). Instead of having the application
> try and guess whether it will work or not provide a driver flag that
> can be checked instead.
> 
> Note: if device driver doesn't support link state control, what
> would happen previously is that the code would never detect link
> transitions. This prevents that.
> 
[...]
> @@ -197,6 +197,8 @@ struct rte_pci_driver {
>  #define RTE_PCI_DRV_MULTIPLE 0x0002
>  /** Device needs to be unbound even if no module is provided */
>  #define RTE_PCI_DRV_FORCE_UNBIND 0x0004
> +/** Device driver supports link state interrupt */
> +#define RTE_PCI_DRV_LSC	0x0008

I feel RTE_PCI_DRV_INTR_LSC would be easier to understand.
Do you agree?

Note that related event is RTE_ETH_EVENT_INTR_LSC
and configuration is intr_conf.lsc.

Title should be "ethdev: add link state interrupt flag".

Thanks
-- 
Thomas

  parent reply	other threads:[~2014-06-20 13:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 22:12 [PATCH v2] rte_ethdev: add link support flag Stephen Hemminger
     [not found] ` <20140619151238.28b9bbea-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2014-06-20 13:06   ` Thomas Monjalon [this message]
2014-06-25  9:27     ` Thomas Monjalon
2014-06-27  0:23     ` 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=4709584.nAXykbU3l6@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.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.