public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb•de>
To: Vivek Kashyap <kashyapv@us•ibm.com>
Cc: Scott Feldman <scofeldm@cisco•com>,
	davem@davemloft•net, netdev@vger•kernel.org, chrisw@redhat•com,
	Jens Osterkamp <Jens.Osterkamp@gmx•de>
Subject: Re: [net-next-2.6 PATCH 2/2] add ndo_set_port_profile op support for enic dynamic vnics
Date: Mon, 3 May 2010 13:32:34 +0200	[thread overview]
Message-ID: <201005031332.34955.arnd@arndb.de> (raw)
In-Reply-To: <alpine.LFD.2.00.1005022119140.16925@vk>

On Monday 03 May 2010, Vivek Kashyap wrote:
> > After a successful pre-associate-with-resource-reservation step, we
> > know that the actual associate step will be both fast and successful.
> > After it completes, the VSI is known to be on the destination
> > and all traffic goes there (replacing the gratuitous ARP method we do
> > today).
> >
> > I don't think we'd ever do a pre-associate without the
> > resource-reservation, but the standard defines both. In theory,
> > we could do a pre-associate at every switch in the data center
> > in order to find out if it's possible to migrate there.
> >
> > If you want to have more details, please look at the draft spec at
> > http://www.ieee802.org/1/files/public/docs2010/bg-joint-evb-0410v1.pdf
> 
> The basic difference is that in 'pre-associate with resoruce reservation', the 
> local buffers and resources needed for the eventual 'associate' are reserved
> at the switch port.  Therefore the associate will not fail with 
> 'insufficient resources'. It might otherwise.

Yes, that's exactly what I wrote. So do you have any idea why we would
ever not want to do the resource reservation?

	Arnd

  reply	other threads:[~2010-05-03 11:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28  4:42 [net-next-2.6 PATCH 1/2] Add netdev port-profile support (take III, was iovnl) Scott Feldman
2010-04-28  4:42 ` [net-next-2.6 PATCH 2/2] add ndo_set_port_profile op support for enic dynamic vnics Scott Feldman
2010-04-28 13:32   ` Arnd Bergmann
2010-04-28 18:39     ` Scott Feldman
2010-04-28 19:16       ` Arnd Bergmann
2010-04-28 22:38         ` Scott Feldman
2010-04-29 12:27           ` Arnd Bergmann
2010-04-29 14:32             ` Scott Feldman
2010-04-29 15:48               ` Arnd Bergmann
2010-04-29 16:31                 ` Scott Feldman
2010-04-30 20:34                 ` Scott Feldman
2010-05-01 12:36                   ` Arnd Bergmann
2010-05-03  4:29                 ` Vivek Kashyap
2010-05-03 11:32                   ` Arnd Bergmann [this message]
2010-05-03 16:18                     ` Vivek Kashyap
2010-04-28 13:13 ` [net-next-2.6 PATCH 1/2] Add netdev port-profile support (take III, was iovnl) Arnd Bergmann
2010-04-28 17:51   ` Scott Feldman
2010-04-28 19:33     ` Arnd Bergmann
2010-04-28 18:54   ` Scott Feldman
2010-04-28 19:37     ` Arnd Bergmann

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=201005031332.34955.arnd@arndb.de \
    --to=arnd@arndb$(echo .)de \
    --cc=Jens.Osterkamp@gmx$(echo .)de \
    --cc=chrisw@redhat$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=kashyapv@us$(echo .)ibm.com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=scofeldm@cisco$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox