From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ranjit.menon@intel.com>
Received: from mga12.intel.com (mga12.intel.com [192.55.52.136])
 by dpdk.org (Postfix) with ESMTP id B0A4A1B486
 for <dev@dpdk.org>; Wed, 24 Apr 2019 01:16:31 +0200 (CEST)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from fmsmga004.fm.intel.com ([10.253.24.48])
 by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;
 23 Apr 2019 16:16:29 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.60,387,1549958400"; d="scan'208";a="164446998"
Received: from rmenon-mobl.amr.corp.intel.com (HELO [134.134.172.74])
 ([134.134.172.74])
 by fmsmga004.fm.intel.com with ESMTP; 23 Apr 2019 16:16:29 -0700
To: "dev@dpdk.org" <dev@dpdk.org>
From: Ranjit Menon <ranjit.menon@intel.com>
Message-ID: <765bc645-eb70-2a59-39de-5a573021e328@intel.com>
Date: Tue, 23 Apr 2019 16:16:29 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: [dpdk-dev] DPDK Windows Community call - 18 April 2019
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2019 23:16:32 -0000

Attendees:
(Present)
Thomas (thomas@monjalon.net)
Harini (harini.ramakrishnan@microsoft.com)
Bruce (bruce.richardson@intel.com)
Cathal (cathal.ohare@intel.com)
Anand (anand.rawat@intel.com)
Pallavi (pallavi.kadam@intel.com)
Ranjit (ranjit.menon@intel.com)

Eilon  (eilong@mellanox.com)
Raslan (rasland@mellanox.com)
        (yohadt@mellanox.com)
Jeffrey (jeffrey.tippet@microsoft.com)
Omar (ocardona@microsoft.com)
Khoa (khot@microsoft.com)

New interested attendees added to meeting invite for next call:
Haseeb.Gani@cavium.com
shshaikh@marvell.com
nareshkumar.pbs@broadcom.com

Agenda:
------
Meeting for 1 hour as a place holder every 2 weeks.
Expect call to last 30-40 minutes or longer as needed.
Encourage other dpdk.org windows partners to join this call.
Minutes via public mailing list.
a. Current release
b. Improvements/Shared objectives - sync up on the bus/pci and general 
status
    - Mellanox agrees bus/pci port should be our next target
    - Intel has latest bus/pci updates available in windows draft repo
c. Any other business


Minutes:
-------
- Removing rte_panic() calls in EAL (and other libraries)
- Some functions that call rte_panic() are defined as 'void' return.
   - will need to modify these functions - which breaks ABI.
- If we're doing this it would require deprecation notice in 19.05.
- Group discussion on removal of rte panics void returns.
- Might need another definition for fatal error codes
   - Why? The application layer will assess whether something is fatal
   - Better to return what the error is and let the application take the 
decision on whether or not it’s a fatal error.
- Advice is to use current error codes that is close enough to the error 
seen.
- Use a matching a core id error – we should pass back an int-return and 
allow the app to decide what action to take.
- Thomas says Arnon Warshavsky (arnon@qwilt.com) was working on removing 
rte panics last year (eal: replace rte_panic instances to return an 
error value).
- Check the list of what APIs need to change and get the list out now to 
the community in 19.05.
- This woudl be a pre-announcement message to the mailing list – this is 
sent as a patch in 19.05, explaining what will be changed in which files.
- Offline discussion with Arnon: see mailing list for detail.

- What other changes do we need to do in EAL to make upstreaming easier?
  - Open source libraries to support common code (BSD licenses).
  - May need a better wrapper on Linux files to use for windows.
  - Some of them (eg: pthreads) not supported in windows
    - so we did macro substitutions to use Windows threads.
  - Wrappers could be used more widely.
    - Need to work out how to do this more widely.
- Please send your ideas for a solution to the mailing list to seek 
comments (RFC).
  - We need to identify the blockers we’re aware of at the moment
    - Perhaps, TSC is one.
- Send interesting topics for the community to work on.

- Is the bus/pci code available?
  - Ask is to move the bus/pci code over to the latest branch (intel).
- Intel/Microsoft currently working to tidy up the branches & names on 
windows draft repo.

- Any new code for the tree?
  - Microsoft is trying to add new code to existing UIO driver
  - This will be available on windows draft repo (18.08 branch)

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by dpdk.space (Postfix) with ESMTP id 08FF5A05D3
	for <public@inbox.dpdk.org>; Wed, 24 Apr 2019 01:16:33 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id CFA571B486;
	Wed, 24 Apr 2019 01:16:32 +0200 (CEST)
Received: from mga12.intel.com (mga12.intel.com [192.55.52.136])
 by dpdk.org (Postfix) with ESMTP id B0A4A1B486
 for <dev@dpdk.org>; Wed, 24 Apr 2019 01:16:31 +0200 (CEST)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from fmsmga004.fm.intel.com ([10.253.24.48])
 by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;
 23 Apr 2019 16:16:29 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.60,387,1549958400"; d="scan'208";a="164446998"
Received: from rmenon-mobl.amr.corp.intel.com (HELO [134.134.172.74])
 ([134.134.172.74])
 by fmsmga004.fm.intel.com with ESMTP; 23 Apr 2019 16:16:29 -0700
To: "dev@dpdk.org" <dev@dpdk.org>
From: Ranjit Menon <ranjit.menon@intel.com>
Message-ID: <765bc645-eb70-2a59-39de-5a573021e328@intel.com>
Date: Tue, 23 Apr 2019 16:16:29 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: [dpdk-dev] DPDK Windows Community call - 18 April 2019
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>
Message-ID: <20190423231629.wvjhQEbkH53tQwn6qzjOEmsrGkDXPwmBQEd24UyAlnA@z>

Attendees:
(Present)
Thomas (thomas@monjalon.net)
Harini (harini.ramakrishnan@microsoft.com)
Bruce (bruce.richardson@intel.com)
Cathal (cathal.ohare@intel.com)
Anand (anand.rawat@intel.com)
Pallavi (pallavi.kadam@intel.com)
Ranjit (ranjit.menon@intel.com)

Eilon  (eilong@mellanox.com)
Raslan (rasland@mellanox.com)
        (yohadt@mellanox.com)
Jeffrey (jeffrey.tippet@microsoft.com)
Omar (ocardona@microsoft.com)
Khoa (khot@microsoft.com)

New interested attendees added to meeting invite for next call:
Haseeb.Gani@cavium.com
shshaikh@marvell.com
nareshkumar.pbs@broadcom.com

Agenda:
------
Meeting for 1 hour as a place holder every 2 weeks.
Expect call to last 30-40 minutes or longer as needed.
Encourage other dpdk.org windows partners to join this call.
Minutes via public mailing list.
a. Current release
b. Improvements/Shared objectives - sync up on the bus/pci and general 
status
    - Mellanox agrees bus/pci port should be our next target
    - Intel has latest bus/pci updates available in windows draft repo
c. Any other business


Minutes:
-------
- Removing rte_panic() calls in EAL (and other libraries)
- Some functions that call rte_panic() are defined as 'void' return.
   - will need to modify these functions - which breaks ABI.
- If we're doing this it would require deprecation notice in 19.05.
- Group discussion on removal of rte panics void returns.
- Might need another definition for fatal error codes
   - Why? The application layer will assess whether something is fatal
   - Better to return what the error is and let the application take the 
decision on whether or not it’s a fatal error.
- Advice is to use current error codes that is close enough to the error 
seen.
- Use a matching a core id error – we should pass back an int-return and 
allow the app to decide what action to take.
- Thomas says Arnon Warshavsky (arnon@qwilt.com) was working on removing 
rte panics last year (eal: replace rte_panic instances to return an 
error value).
- Check the list of what APIs need to change and get the list out now to 
the community in 19.05.
- This woudl be a pre-announcement message to the mailing list – this is 
sent as a patch in 19.05, explaining what will be changed in which files.
- Offline discussion with Arnon: see mailing list for detail.

- What other changes do we need to do in EAL to make upstreaming easier?
  - Open source libraries to support common code (BSD licenses).
  - May need a better wrapper on Linux files to use for windows.
  - Some of them (eg: pthreads) not supported in windows
    - so we did macro substitutions to use Windows threads.
  - Wrappers could be used more widely.
    - Need to work out how to do this more widely.
- Please send your ideas for a solution to the mailing list to seek 
comments (RFC).
  - We need to identify the blockers we’re aware of at the moment
    - Perhaps, TSC is one.
- Send interesting topics for the community to work on.

- Is the bus/pci code available?
  - Ask is to move the bus/pci code over to the latest branch (intel).
- Intel/Microsoft currently working to tidy up the branches & names on 
windows draft repo.

- Any new code for the tree?
  - Microsoft is trying to add new code to existing UIO driver
  - This will be available on windows draft repo (18.08 branch)