All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Jan Blunck <jblunck@infradead.org>
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH 8/8] eal: VMBUS infrastructure
Date: Tue, 10 Jan 2017 10:05:02 -0800	[thread overview]
Message-ID: <20170110100502.5b55059b@xeon-e3> (raw)
In-Reply-To: <CALe+Z000WmS4WeL315otctGkYayPqspEB20o+RTxzgA8ieS8_g@mail.gmail.com>

On Tue, 10 Jan 2017 18:27:31 +0100
Jan Blunck <jblunck@infradead.org> wrote:

> > +#ifdef RTE_LIBRTE_HV_PMD
> > +/**
> > + * @internal
> > + * Wrapper for use by vmbus drivers as a .probe function to attach to a ethdev
> > + * interface.
> > + */
> > +int rte_eth_dev_vmbus_probe(struct rte_vmbus_driver *vmbus_drv,
> > +                         struct rte_vmbus_device *vmbus_dev);
> > +
> > +/**
> > + * @internal
> > + * Wrapper for use by vmbus drivers as a .remove function to detach a ethdev
> > + * interface.
> > + */
> > +int rte_eth_dev_vmbus_remove(struct rte_vmbus_device *vmbus_dev);
> > +#endif  
> 
> I don't think that replicating the PCI probe/remove wrappers is the
> right thing to do. To me it looks like this should move into the
> rte_vmbus_driver's probe function instead. That way the ethdev header
> can decoupled from the low-level device implementations.

With a real bus model. There would be registration of busses. And the probe would
be:
   foreach bus
       foreach device on bus
...

  reply	other threads:[~2017-01-10 18:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-07 18:17 [PATCH v2 0/8] device abstraction and VMBUS support infrastructure Stephen Hemminger
2017-01-07 18:17 ` [PATCH 1/8] ethdev: increase length ethernet device internal name Stephen Hemminger
2017-01-07 18:17 ` [PATCH 2/8] i40e: don't refer to eth_dev->pci_dev Stephen Hemminger
2017-01-10 12:08   ` Jan Blunck
2017-01-10 17:57     ` Stephen Hemminger
2017-01-11  7:55       ` Jan Blunck
2017-01-07 18:17 ` [PATCH 3/8] vmxnet3: " Stephen Hemminger
2017-01-10 12:10   ` Jan Blunck
2017-01-07 18:17 ` [PATCH 4/8] cxgbe: " Stephen Hemminger
2017-01-10 12:12   ` Jan Blunck
2017-01-07 18:17 ` [PATCH 5/8] nfp: " Stephen Hemminger
2017-01-10 12:13   ` Jan Blunck
2017-01-07 18:17 ` [PATCH 6/8] qat: " Stephen Hemminger
2017-01-10 12:15   ` Jan Blunck
2017-01-07 18:17 ` [PATCH 7/8] ethdev: break ethernet driver and pci_driver connection Stephen Hemminger
2017-01-10 13:59   ` Ferruh Yigit
2017-01-10 17:58     ` Ferruh Yigit
2017-01-10 18:02       ` [PATCH 1/2] add rte_bus->probe Ferruh Yigit
2017-01-10 18:02         ` [PATCH 2/2] separate bus and functionality driver structs Ferruh Yigit
2017-01-11  4:53         ` [PATCH 1/2] add rte_bus->probe Shreyansh Jain
2017-01-11 15:03           ` Ferruh Yigit
2017-01-12  5:28             ` Shreyansh Jain
2017-01-10 16:11   ` [PATCH 7/8] ethdev: break ethernet driver and pci_driver connection Jan Blunck
2017-01-10 18:03     ` Stephen Hemminger
2017-01-07 18:17 ` [PATCH 8/8] eal: VMBUS infrastructure Stephen Hemminger
2017-01-10 17:27   ` Jan Blunck
2017-01-10 18:05     ` Stephen Hemminger [this message]
2017-01-11 14:49   ` Jan Blunck
2017-01-11 21:13     ` Jan Blunck
2017-01-12  1:20       ` Stephen Hemminger

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=20170110100502.5b55059b@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=jblunck@infradead.org \
    --cc=sthemmin@microsoft.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 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.