All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Blunck <jblunck@infradead.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Vincent JARDIN <vincent.jardin@6wind.com>,
	Joao Martins <joao.m.martins@oracle.com>,
	Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Tan, Jianfeng" <jianfeng.tan@intel.com>,
	Konrad Rzeszutek Wilk <konrad@kernel.org>, dev <dev@dpdk.org>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Yuanhan Liu <yuanhan.liu@linux.intel.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] maintainers: claim responsability for xen
Date: Mon, 20 Feb 2017 10:56:57 +0100	[thread overview]
Message-ID: <CALe+Z0153tPoor2HpNXOX57t4E_coHaNcVLnwFtL=6LFE0nr7A@mail.gmail.com> (raw)
In-Reply-To: <20170217160731.GA30539@char.us.ORACLE.com>

On Fri, Feb 17, 2017 at 5:07 PM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Thu, Feb 16, 2017 at 10:51:44PM +0100, Vincent JARDIN wrote:
>> Le 16/02/2017 à 14:36, Konrad Rzeszutek Wilk a écrit :
>> > > Is it time now to officially remove Dom0 support?
>> > So we do have an prototype implementation of netback but it is waiting
>> > for review of xen-devel to the spec.
>> >
>> > And I believe the implementation does utilize some of the dom0
>> > parts of code in DPDK.
>>
>> Please, do you have URLs/pointers about it? It would be interesting to share
>> it with DPDK community too.
>
> Joao, would it be possible to include an tarball of the patches? I know
> they are no in the right state with the review of the staging
> grants API - they are incompatible, but it may help folks to get
> a feel for what DPDK APIs you used?
>
> Staging grants API:
> https://lists.xenproject.org/archives/html/xen-devel/2016-12/msg01878.html
>

The topic of the grants API is unrelated to the dom0 memory pool. The
memory pool which uses xen_create_contiguous_region() is used in cases
we know that there are no hugepages available.

Joao and I met in Dublin and I whined about not being able to call
into the grants API from userspace and instead need to kick a kernel
driver to do the work for every burst. It would be great if that could
change in the future.

  reply	other threads:[~2017-02-20  9:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07  7:38 [PATCH] maintainers: claim responsability for xen Jianfeng Tan
2016-11-09 22:03 ` Thomas Monjalon
2016-11-10 18:59   ` [dpdk-dev] " Konrad Rzeszutek Wilk
2016-11-10 18:59   ` Konrad Rzeszutek Wilk
2016-11-10 20:49     ` [dpdk-dev] " Tan, Jianfeng
2016-11-10 20:49     ` Tan, Jianfeng
2017-02-16 11:06       ` [dpdk-dev] " Thomas Monjalon
2017-02-16 11:06       ` Thomas Monjalon
2017-02-16 13:02         ` Vincent JARDIN
2017-02-16 13:02         ` [dpdk-dev] " Vincent JARDIN
2017-02-16 13:36         ` Konrad Rzeszutek Wilk
2017-02-16 16:17           ` Jan Blunck
2017-02-16 16:17           ` [dpdk-dev] " Jan Blunck
2017-02-16 21:51           ` Vincent JARDIN
2017-02-17 16:07             ` [dpdk-dev] " Konrad Rzeszutek Wilk
2017-02-20  9:56               ` Jan Blunck [this message]
2017-02-20 17:36                 ` Joao Martins
2017-02-20 17:36                 ` [dpdk-dev] " Joao Martins
2017-02-20  9:56               ` Jan Blunck
2017-02-20 15:33               ` Joao Martins
2017-02-23  8:49                 ` Thomas Monjalon
2017-02-23  8:49                 ` Thomas Monjalon
2017-02-23 20:10                   ` Martinx - ジェームズ
2017-05-04 22:04                   ` Thomas Monjalon
2017-05-11 11:41                     ` Tan, Jianfeng
2017-06-19 13:22                       ` Thomas Monjalon
2017-06-19 13:22                       ` [dpdk-dev] " Thomas Monjalon
2017-05-11 11:41                     ` Tan, Jianfeng
2017-05-04 22:04                   ` Thomas Monjalon
2017-02-16 21:51           ` Vincent JARDIN

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='CALe+Z0153tPoor2HpNXOX57t4E_coHaNcVLnwFtL=6LFE0nr7A@mail.gmail.com' \
    --to=jblunck@infradead.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.com \
    --cc=joao.m.martins@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=konrad@kernel.org \
    --cc=thomas.monjalon@6wind.com \
    --cc=vincent.jardin@6wind.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=yuanhan.liu@linux.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: 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.