Hi Konstantin
From: Ananyev, Konstantin, Tuesday, April 17, 2018 2:00 PM
> Hi Matan,
> > Hi Konstantin
> > From: Ananyev, Konstantin, Tuesday, April 17, 2018 12:23 PM
> > > > Actually you say that the whitelist\blacklist mechanism is not
> > > > good enough
> > > and the binding workarounds it.
>
19/04/2018 10:40, Bruce Richardson:
> On Thu, Apr 19, 2018 at 10:24:24AM +0200, Thomas Monjalon wrote:
> > 19/04/2018 08:04, Alejandro Lucero:
> > > I do not completely understand the discussion, but I think the
> > > disagreement is due to how some devices interact with DPDK, at least
> > > Mellan
On Thu, Apr 19, 2018 at 10:24:24AM +0200, Thomas Monjalon wrote:
> 19/04/2018 08:04, Alejandro Lucero:
> > I do not completely understand the discussion, but I think the
> > disagreement is due to how some devices interact with DPDK, at least
> > Mellanox ones. I'm saying that because we have a DPD
19/04/2018 08:04, Alejandro Lucero:
> I do not completely understand the discussion, but I think the disagreement
> is due to how some devices interact with DPDK, at least Mellanox ones. I'm
> saying that because we have a DPDK app which starts with no device at all
> (--no-pci) and it relies on de
I do not completely understand the discussion, but I think the disagreement
is due to how some devices interact with DPDK, at least Mellanox ones. I'm
saying that because we have a DPDK app which starts with no device at all
(--no-pci) and it relies on device plugging attach/detach for configuring
On Wed, Apr 18, 2018 at 11:17:47AM -0700, Stephen Hemminger wrote:
> On Wed, 18 Apr 2018 11:11:01 -0300
> Flavio Leitner wrote:
>
> > On Sun, Apr 15, 2018 at 01:48:36AM +, Stephen Hemminger wrote:
> > > My vote is to work with udev and not try to replace it.
> > >
> > > Driverctl works well.
On Wed, 18 Apr 2018 11:11:01 -0300
Flavio Leitner wrote:
> On Sun, Apr 15, 2018 at 01:48:36AM +, Stephen Hemminger wrote:
> > My vote is to work with udev and not try to replace it.
> >
> > Driverctl works well. Just not for bifurcated driver
>
> I second that. We also have other system
On Sun, Apr 15, 2018 at 01:48:36AM +, Stephen Hemminger wrote:
> My vote is to work with udev and not try to replace it.
>
> Driverctl works well. Just not for bifurcated driver
I second that. We also have other system configs to care about like
kernel parameters and hugepage configuration w
Hi Matan,
>
>
> Hi Konstantin
>
> From: Ananyev, Konstantin, Tuesday, April 17, 2018 12:23 PM
> > To: Matan Azrad ; Richardson, Bruce
> >
> > Cc: Burakov, Anatoly ; Thomas Monjalon
> > ; dev@dpdk.org; pmati...@redhat.com;
> > david.march...@6wind.com; Guo, Jia ;
> > step...@networkplumber.org;
Hi Konstantin
From: Ananyev, Konstantin, Tuesday, April 17, 2018 12:23 PM
> To: Matan Azrad ; Richardson, Bruce
>
> Cc: Burakov, Anatoly ; Thomas Monjalon
> ; dev@dpdk.org; pmati...@redhat.com;
> david.march...@6wind.com; Guo, Jia ;
> step...@networkplumber.org; f...@redhat.com
> Subject: RE: ke
Hi everyone,
Few comments from me below.
In summary I am also in favor to keep binding decision at system level (outside
DPDK).
Konstantin
> -Original Message-
> From: Matan Azrad [mailto:ma...@mellanox.com]
> Sent: Monday, April 16, 2018 5:11 PM
> To: Richardson, Bruce
> Cc: Burakov, A
16/04/2018 18:57, Stephen Hemminger:
> Buried under this discussion is the fact that the Mellanox bifurcated driver
> behaves completely differently from every other driver. This makes coming to
> a common solution much harder. The bifurcated model has advantages and
> disadvantages,
> in this cas
Hi Stephen
From: Stephen Hemminger, Monday, April 16, 2018 8:19 PM
> On Mon, 16 Apr 2018 17:10:09 +
> Matan Azrad wrote:
>
> > Hi Stephen
> >
> > From: Stephen Hemminger, Monday, April 16, 2018 7:57 PM
> > > On Mon, 16 Apr 2018 16:11:12 +
> > > Matan Azrad wrote:
> > >
> > > > > If the
On Mon, 16 Apr 2018 17:10:09 +
Matan Azrad wrote:
> Hi Stephen
>
> From: Stephen Hemminger, Monday, April 16, 2018 7:57 PM
> > On Mon, 16 Apr 2018 16:11:12 +
> > Matan Azrad wrote:
> >
> > > > If the device management is only managed in one place, i.e. not in
> > > > DPDK, then there
Hi Stephen
From: Stephen Hemminger, Monday, April 16, 2018 7:57 PM
> On Mon, 16 Apr 2018 16:11:12 +
> Matan Azrad wrote:
>
> > > If the device management is only managed in one place, i.e. not in
> > > DPDK, then there is no conflict to manage.
> >
> > I can't agree with this statement,
> >
On Mon, 16 Apr 2018 16:11:12 +
Matan Azrad wrote:
> > If the device management is only managed in one place, i.e. not in DPDK,
> > then there is no conflict to manage.
>
> I can't agree with this statement,
> The essence of DPDK is to give a good alternative to managing network devices,
>
Hi Bruce
From: Bruce Richardson, Monday, April 16, 2018 11:32 AM
> On Sat, Apr 14, 2018 at 08:10:28PM +, Matan Azrad wrote:
> > Hi all
> >
> > From: Burakov, Anatoly, Friday, April 13, 2018 8:41 PM
> > > To: Bruce Richardson ; Thomas Monjalon
> > >
> > > Cc: dev@dpdk.org; pmati...@redhat.com;
Hi Guo
From: Guo, Jia, Monday, April 16, 2018 12:26 PM
> To: Matan Azrad ; Burakov, Anatoly
> ; Bruce Richardson
> ; Thomas Monjalon
> Cc: dev@dpdk.org; pmati...@redhat.com; david.march...@6wind.com;
> konstantin.anan...@intel.com; step...@networkplumber.org;
> f...@redhat.com
> Subject: Re: kern
hi, all
On 4/15/2018 4:10 AM, Matan Azrad wrote:
Hi all
From: Burakov, Anatoly, Friday, April 13, 2018 8:41 PM
To: Bruce Richardson ; Thomas Monjalon
Cc: dev@dpdk.org; pmati...@redhat.com; david.march...@6wind.com;
jia@intel.com; Matan Azrad ;
konstantin.anan...@intel.com; step...@networ
On Sat, Apr 14, 2018 at 08:10:28PM +, Matan Azrad wrote:
> Hi all
>
> From: Burakov, Anatoly, Friday, April 13, 2018 8:41 PM
> > To: Bruce Richardson ; Thomas Monjalon
> >
> > Cc: dev@dpdk.org; pmati...@redhat.com; david.march...@6wind.com;
> > jia@intel.com; Matan Azrad ;
> > konstantin.
On Apr 13, 2018, at 11:40 AM, Bruce Richardson
mailto:bruce.richard...@intel.com>> wrote:
On Fri, Apr 13, 2018 at 06:31:21PM +0200, Thomas Monjalon wrote:
It's time to think (again) how we bind devices with kernel modules.
We need to decide how we want to manage hotplugged devices with DPDK.
A
My vote is to work with udev and not try to replace it.
Driverctl works well. Just not for bifurcated driver
On Fri, Apr 13, 2018, 9:31 AM Thomas Monjalon wrote:
> It's time to think (again) how we bind devices with kernel modules.
> We need to decide how we want to manage hotplugged devices wi
Hi all
From: Burakov, Anatoly, Friday, April 13, 2018 8:41 PM
> To: Bruce Richardson ; Thomas Monjalon
>
> Cc: dev@dpdk.org; pmati...@redhat.com; david.march...@6wind.com;
> jia@intel.com; Matan Azrad ;
> konstantin.anan...@intel.com; step...@networkplumber.org;
> f...@redhat.com
> Subject: R
On 13-Apr-18 5:40 PM, Bruce Richardson wrote:
On Fri, Apr 13, 2018 at 06:31:21PM +0200, Thomas Monjalon wrote:
It's time to think (again) how we bind devices with kernel modules.
We need to decide how we want to manage hotplugged devices with DPDK.
A bit of history first.
There was some code in
On Fri, Apr 13, 2018 at 06:31:21PM +0200, Thomas Monjalon wrote:
> It's time to think (again) how we bind devices with kernel modules.
> We need to decide how we want to manage hotplugged devices with DPDK.
>
> A bit of history first.
> There was some code in DPDK for bind/unbind, but it has been
It's time to think (again) how we bind devices with kernel modules.
We need to decide how we want to manage hotplugged devices with DPDK.
A bit of history first.
There was some code in DPDK for bind/unbind, but it has been removed
in DPDK 1.7 - http://dpdk.org/commit/5d8751b83
Copy of the commit m
26 matches
Mail list logo
