From: Richard Cochran <richardcochran@gmail.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: linux-net-drivers <linux-net-drivers@solarflare.com>,
netdev <netdev@vger.kernel.org>,
Laurence Evans <levans@solarflare.com>
Subject: Re: PHC device sharing between PCI functions
Date: Thu, 4 Jul 2013 19:39:25 +0200 [thread overview]
Message-ID: <20130704173925.GA4429@netboy> (raw)
In-Reply-To: <1372954878.1853.6.camel@bwh-desktop.uk.level5networks.com>
On Thu, Jul 04, 2013 at 05:21:18PM +0100, Ben Hutchings wrote:
>
> But that is the opposite of what we're talking about. Say the card has,
> 16 functions resulting in net devices eth0-eth15, each of which can
> access the same physical clock. You said it's OK to have read-only
> aliases for a clock, so then there might be a writable /dev/ptp0 and
> read-only /dev/ptp1-ptp15. What is the proper association between net
> devices and clock devices?
But the card doesn't have 16 plugs, or does it?
I understood you to have meant that the card has one physical plug,
shared between one host and fifteen guests. Or maybe I am total
confused. No, I am surely confused.
Anyhow, if a host is multihomed, then ideally all of the interfaces
share one and the same clock. But, if the only purpose of the multiple
interfaces in the VM host is to assign them to VM guests, then I guess
it doesn't matter very much how they appear in the VM host.
Richard
next prev parent reply other threads:[~2013-07-04 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 16:56 PHC device sharing between PCI functions Ben Hutchings
2013-07-02 14:24 ` Richard Cochran
2013-07-02 15:17 ` Ben Hutchings
2013-07-03 18:30 ` Richard Cochran
2013-07-03 19:52 ` Ben Hutchings
2013-07-04 5:36 ` Richard Cochran
2013-07-04 14:34 ` Ben Hutchings
2013-07-04 15:53 ` Richard Cochran
2013-07-04 16:21 ` Ben Hutchings
2013-07-04 17:39 ` Richard Cochran [this message]
2013-07-04 18:19 ` Ben Hutchings
2013-07-05 5:25 ` Richard Cochran
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=20130704173925.GA4429@netboy \
--to=richardcochran@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=levans@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.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 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).