Get the best feeling with Pure AquaDerm.
Unique formula of our cream will help you to look like a star, no wrinkles,
smooth and soft skin.
Get Pu yjt re Aq xq uaD yx erm and realize that everyone can look and feel
years younger.
We are proud of what we offer to you as satisfied client is our m
The fnic driver needs to push the assigned FC_ID to firmware.
It currently does this by intercepting the FLOGI responses, and
in order to make that code more common with FIP and NPIV, it
makes more sense to wait until the local port has completely
handled the FLOGI or FDISC response. Also, when we
If link is up, but no FCF is selected, don't send any ELS frames.
This came up when an fnic received a multicast advertisement but
no solitited advertisments, so no FCF was selected. It tried
to send FLOGIs anyway.
Signed-off-by: Joe Eykholt
---
drivers/scsi/fcoe/libfcoe.c |2 ++
1 files c
It's possible and harmless to get FLOGI timeouts
while in RESET state. Don't do a WARN_ON in that case.
Also, split out the other WARN_ONs in fc_lport_timeout, so
we can tell which one is hit by its line number.
Signed-off-by: Joe Eykholt
---
drivers/scsi/libfc/fc_lport.c |5 -
1 files
The fnic driver with FIP is reporting link up, even though it's down.
When the interface is shut down by the switch, we receive a clear
virtual link, and set the state reported to libfc as down, although
we still report it up. Clearly wrong. That causes the subsequent
link down event not to be r
FIP's fcoe_ctlr_recv() function was previously only called from
the soft IRQ in FCoE. It's not performance critical and is more
convenient for some drivers to call it from the IRQ level. Just
Change to use skb_queue()/dequeue() which uses spinlock_irqsave
instead of separate locking with _bh lock
Use scsi host number to identify debug messages.
Previously, no instance information was given, so if multiple
ports were active, it became confusing.
Signed-off-by: Joe Eykholt
---
drivers/scsi/fcoe/libfcoe.c | 47 ---
1 files changed, 26 insertions(+),
Allow FIP to be disabled by the driver for devices
that want to use libfcoe in non-FIP mode.
The driver merely sets the fcoe_ctlr mode to the state which
should be entered when the link comes up. The default is auto.
No change is needed for fcoe.c which uses auto mode.
Signed-off-by: Joe Eykholt
The following series makes changes to libfc and libfcoe to provide
FIP support for the fnic driver. The patch to the fnic driver will
be sent separately.
The fnic firmware may not support FIP, so a mode is added to libfcoe
to run solely in non-FIP mode.
The FIP debug messages are improved to inc
Fix minor errors.
A debug message said an RLIR was received instead of ECHO.
"Expected" was misspelled in several places.
Fix a type cast from u32 to __be32.
Rob, Some of these may have been also taken care of in your
other doc cleanup patch. Feel free to fold them in.
Signed-off-by: Joe Eykholt
On Tue, 2009-09-08 at 18:36 -0700, Robert Love wrote:
> Hi,
>
> I rebased fcoe-next.git to the most recent scsi-misc and linux-2.6
> trees. I also committed Vasu's queue_depth ramp patches (mailed to
> linux-scsi) in the order that things were received on linux-scsi.
>
> I did have a
Joe Eykholt wrote:
> Robert Love wrote:
>> Hi,
>>
>> I rebased fcoe-next.git to the most recent scsi-misc and linux-2.6
>> trees. I also committed Vasu's queue_depth ramp patches (mailed to
>> linux-scsi) in the order that things were received on linux-scsi.
>>
>> I did have a few problem
On Wed, Sep 09, 2009 at 10:24:44AM -0700, Joe Eykholt wrote:
> Chris Leech wrote:
> > Just wondering, for what reasons would you see a need to continue supporting
> > a non-FIP mode? I'd think it highly unlikely to see anything non-FIP
> > put into production, and would like a plan to gradually de
Chris Leech wrote:
> This looks pretty good. What I put into fcoe with the overriding of the
> elsct_send hook does have a potential issue in that it will set a new
> MAC address before knowing that libfc actually accepted the fc_id.
Thanks. I didn't go so far as to change fcoe.c. Maybe you cou
Chris Leech wrote:
> Just wondering, for what reasons would you see a need to continue supporting
> a non-FIP mode? I'd think it highly unlikely to see anything non-FIP
> put into production, and would like a plan to gradually deprecate and
> remove non-FIP support.
We need it for fnic. The firs
Bonjour,
Nous organisons chaque mois des sessions de formation MapInfo® :
Formations inter-entreprises de 2 jours à Paris - Groupes de 2 à 6 personnes.
Session Initiation : pour découvrir les fonctionnalités principales du logiciel.
Session Perfectionnement : pour les utilisateurs MapInfo® qui sou
This looks pretty good. What I put into fcoe with the overriding of the
elsct_send hook does have a potential issue in that it will set a new
MAC address before knowing that libfc actually accepted the fc_id.
Chris
On Tue, Sep 08, 2009 at 06:38:57PM -0700, Joe Eykholt wrote:
> The fnic
This looks good to me Joe.
Acked-by: Chris Leech
On Tue, Sep 08, 2009 at 06:38:40PM -0700, Joe Eykholt wrote:
> FIP's fcoe_ctlr_recv() function was previously only called from
> the soft IRQ in FCoE. It's not performance critical and is more
> convenient for some drivers to call it from the IR
Just wondering, for what reasons would you see a need to continue supporting
a non-FIP mode? I'd think it highly unlikely to see anything non-FIP
put into production, and would like a plan to gradually deprecate and
remove non-FIP support.
Point to Point mode relies on it currently, but there are
TR_e-mailing_emmanuelle
POUR DÉCOUVRIR TOUS LES AVANTAGES DE TICKET RESTAURANTR
Accor Services France - SAS au capital de 338 036 640 Euros - Siege social :
Immeuble Columbus - 166 - 180 boulevard Gabriel Péri 92240 Malakoff
Siren : 393 365 135 R.C.S. Nanterre : 393 365 135 - Intra-commun
Newsletter boutique
Chère Cliente, Cher Client,
Bénéficiez de promotions et de prix imbattables pour satisfaire toutes vos
envies coquines! Des articles bradés jusqu'à -50% dans tous les rayons et des
nouveautés à prix explosés...
Dépêchez-vous, les frais de port sont à 1 ? seulement pour
On Wed, 2009-09-09 at 15:00 +0200, Ronnie Koch wrote:
> Robert,
>
> On Tue, 2009-09-08 at 10:31 -0700, Robert Love wrote:
>
> > Each kernel module (libfc.ko, libfcoe.ko and fcoe.ko) has a debug
> > logging module parameter. So, for fcoe.ko you can write to the
> > /sys/module/fcoe/parameters/deb
Dr.Eugene B. Carlisle
My new address:
Burns, OR
Phone:133-586-3775
We present you the official results of the research made by Independent
Research Organization. According to these results Canadian ŤCan yz adia vm nPha
cqm rmacyť dru xwl gstore has the best service, quality and prices on the W
Robert,
On Tue, 2009-09-08 at 10:31 -0700, Robert Love wrote:
> Each kernel module (libfc.ko, libfcoe.ko and fcoe.ko) has a debug
> logging module parameter. So, for fcoe.ko you can write to the
> /sys/module/fcoe/parameters/debug_logging file to change the debug
> logging level. The files repr
Bonjour,
Vous recherchez un partenaire de confiance qui vous propose les solutions les
mieux adaptées à vos besoins informatiques et vous conseille dans
l'optimisation de vos systèmes d'information ?
Ordi et Compagnie offre une solution co
Si vous souhaitez vous désabonner, recopiez cette
25 matches
Mail list logo
