From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH 2/4] bus/vmbus: add host latency tuning function
Date: Thu, 23 Aug 2018 08:40:03 -0700 [thread overview]
Message-ID: <20180823084003.48118955@xeon-e3> (raw)
In-Reply-To: <6547feff-b3fb-4efe-bc3c-057f92d411b1@intel.com>
On Thu, 23 Aug 2018 15:45:44 +0100
Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> On 8/9/2018 6:50 PM, Stephen Hemminger wrote:
> > Add vmbus API to allow tuning the scan interval on the host side.
> >
> > Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
>
> <...>
>
> > @@ -20,6 +20,7 @@ DPDK_18.08 {
> > rte_vmbus_probe;
> > rte_vmbus_register;
> > rte_vmbus_scan;
> > + rte_vmbus_set_latency;
> > rte_vmbus_sub_channel_index;
> > rte_vmbus_subchan_open;
> > rte_vmbus_unmap_device;
>
> Needs to be on DPDK_18.11 now, will fix while merging.
>
> (Since this is not really a public API, I think no need to mark as experimental
> as process and checkpatches requires.)
Sure, thanks. I was testing on 18.08. We need to be able to figure
out internal versus public API symbols at some point. It doesn't matter
if a bus API changes if there is no userspace API that can directly access it.
next prev parent reply other threads:[~2018-08-23 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 17:50 [PATCH 0/4] netvsc performance enhancements Stephen Hemminger
2018-08-09 17:50 ` [PATCH 1/4] netvsc: chimney buffer size error handling Stephen Hemminger
2018-08-23 14:45 ` Ferruh Yigit
2018-08-23 15:38 ` Stephen Hemminger
2018-08-09 17:50 ` [PATCH 2/4] bus/vmbus: add host latency tuning function Stephen Hemminger
2018-08-23 14:45 ` Ferruh Yigit
2018-08-23 15:40 ` Stephen Hemminger [this message]
2018-08-09 17:50 ` [PATCH 3/4] netvsc: set lower host latency Stephen Hemminger
2018-08-09 17:50 ` [PATCH 4/4] netvsc: implement tx_done_cleanup Stephen Hemminger
2018-08-23 14:46 ` Ferruh Yigit
2018-08-23 14:47 ` [PATCH 0/4] netvsc performance enhancements Ferruh Yigit
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=20180823084003.48118955@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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.