On Wed, May 17, 2017 at 01:50:40PM +0100, Ferruh Yigit wrote:
On 3/20/2017 3:00 PM, Thomas Monjalon wrote:
There have been some discussions on this new PMD and it will be
discussed today in the techboard meeting.
I would like to expose my view and summarize the solutions I have heard.
First it
On 3/20/2017 3:00 PM, Thomas Monjalon wrote:
> There have been some discussions on this new PMD and it will be
> discussed today in the techboard meeting.
>
> I would like to expose my view and summarize the solutions I have heard.
> First it is important to remind that everyone agrees on the need
On 3/8/2017 3:15 PM, Gaetan Rivet wrote:
> This PMD intercepts and manages Ethernet device removal events issued by
> slave PMDs and re-initializes them transparently when brought back so that
> existing applications do not need to be modified to benefit from true
> hot-plugging support.
>
> The s
There have been some discussions on this new PMD and it will be
discussed today in the techboard meeting.
I would like to expose my view and summarize the solutions I have heard.
First it is important to remind that everyone agrees on the need for
this feature, i.e. masking the hotplug events by m
On Fri, Mar 17, 2017 at 11:56:21AM +0100, Gaëtan Rivet wrote:
> On Thu, Mar 16, 2017 at 04:50:43PM -0400, Neil Horman wrote:
> > On Wed, Mar 15, 2017 at 03:25:37PM +0100, Gaëtan Rivet wrote:
> > > On Wed, Mar 15, 2017 at 12:15:56PM +0100, Thomas Monjalon wrote:
> > > > 2017-03-15 03:28, Bruce Richa
On Thu, Mar 16, 2017 at 04:50:43PM -0400, Neil Horman wrote:
On Wed, Mar 15, 2017 at 03:25:37PM +0100, Gaëtan Rivet wrote:
On Wed, Mar 15, 2017 at 12:15:56PM +0100, Thomas Monjalon wrote:
> 2017-03-15 03:28, Bruce Richardson:
> > On Tue, Mar 14, 2017 at 03:49:47PM +0100, Gaëtan Rivet wrote:
> >
On Wed, Mar 15, 2017 at 03:25:37PM +0100, Gaëtan Rivet wrote:
> On Wed, Mar 15, 2017 at 12:15:56PM +0100, Thomas Monjalon wrote:
> > 2017-03-15 03:28, Bruce Richardson:
> > > On Tue, Mar 14, 2017 at 03:49:47PM +0100, Gaëtan Rivet wrote:
> > > > - In the bonding, the init and configuration steps are
On Wed, Mar 15, 2017 at 12:15:56PM +0100, Thomas Monjalon wrote:
2017-03-15 03:28, Bruce Richardson:
On Tue, Mar 14, 2017 at 03:49:47PM +0100, Gaëtan Rivet wrote:
> - In the bonding, the init and configuration steps are still the
> responsibility of the application and no one else. The bonding
2017-03-15 03:28, Bruce Richardson:
> On Tue, Mar 14, 2017 at 03:49:47PM +0100, Gaëtan Rivet wrote:
> > > > 2. Bonding and link availability
> > > >
> > > > The hot-plug functionality is not a core function of the bonding PMD.
> > > > It is only interested in knowing if the link is active or not.
On Tue, Mar 14, 2017 at 03:49:47PM +0100, Gaëtan Rivet wrote:
> > > The central question that I would like to tackle is this: why should
> > > we require from our users declaring a bonding device to have
> > > hot-plug support?
> > >
> > We'll, strictly speaking, I suppose we don't have to require
> The central question that I would like to tackle is this: why should
> we require from our users declaring a bonding device to have
> hot-plug support?
>
We'll, strictly speaking, I suppose we don't have to require it. But by that
same token, we don't need to do it in a separate PMD either, the
On Fri, Mar 10, 2017 at 10:13:32AM +0100, Gaëtan Rivet wrote:
> On Thu, Mar 09, 2017 at 09:15:14AM +, Bruce Richardson wrote:
> > On Wed, Mar 08, 2017 at 11:54:02AM -0500, Neil Horman wrote:
> > > On Wed, Mar 08, 2017 at 04:15:33PM +0100, Gaetan Rivet wrote:
> > > > This PMD intercepts and mana
On Thu, Mar 09, 2017 at 09:15:14AM +, Bruce Richardson wrote:
On Wed, Mar 08, 2017 at 11:54:02AM -0500, Neil Horman wrote:
On Wed, Mar 08, 2017 at 04:15:33PM +0100, Gaetan Rivet wrote:
> This PMD intercepts and manages Ethernet device removal events issued by
> slave PMDs and re-initializes
On Wed, Mar 08, 2017 at 11:54:02AM -0500, Neil Horman wrote:
> On Wed, Mar 08, 2017 at 04:15:33PM +0100, Gaetan Rivet wrote:
> > This PMD intercepts and manages Ethernet device removal events issued by
> > slave PMDs and re-initializes them transparently when brought back so that
> > existing appli
On Wed, Mar 08, 2017 at 04:15:33PM +0100, Gaetan Rivet wrote:
> This PMD intercepts and manages Ethernet device removal events issued by
> slave PMDs and re-initializes them transparently when brought back so that
> existing applications do not need to be modified to benefit from true
> hot-pluggin
This PMD intercepts and manages Ethernet device removal events issued by
slave PMDs and re-initializes them transparently when brought back so that
existing applications do not need to be modified to benefit from true
hot-plugging support.
The stacked PMD approach shares many similarities with the
16 matches
Mail list logo
