netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Eykholt <joe@nuovasystems.com>
To: Chris Leech <christopher.leech@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	"Kok, Auke-jan H" <auke-jan.h.kok@intel.com>,
	"Dev, Vasu" <vasu.dev@intel.com>,
	jeff@garzik.org, linux-scsi@vger.kernel.org, "Zou,
	Yi" <yi.zou@intel.com>,
	netdev@vger.kernel.org, "Waskiewicz Jr,
	Peter P" <peter.p.waskiewicz.jr@intel.com>,
	linux-kernel@vger.kernel.org,
	james.bottomley@hansenpartnership.com, "Ronciak,
	John" <john.ronciak@intel.com>,
	devel@open-fcoe.org, "Van De Ven,
	Arjan" <arjan.van.de.ven@intel.com>,
	davem@davemloft.net
Subject: Re: [Open-FCoE] [ANNOUNCE] Open-FCoE - Fibre Channel over Ethernet Project
Date: Wed, 28 Nov 2007 12:08:05 -0800	[thread overview]
Message-ID: <474DCAA5.3020108@nuovasystems.com> (raw)
In-Reply-To: <474DAB30.20703@intel.com>

Chris Leech wrote:
> Christoph Hellwig wrote:
>   
>> I just did a very quick glance over the tree.  Some extremly highlevel
>> comments to start with before actually starting the source review:
>>     
>
> Thanks for taking a look Christoph
>
>   
>>  - why do you need your own libcrc?  lib/crc32.c has a crc32_le
>>     
>
> We shouldn't, but we may want to add a CRC and copy routine.
>
>   
>>  - libsa should go.  Much of it is just wrappers of kernel functions
>>    that should be used directly.  Other like that hash, even or state
>>    helpers might either be opencoded in the caller or made completely
>>    generic in lib/.  Probably the former but we'll have to see.
>>     
>
> Yes, and along with it the last use of the BSD TAILQ macros.  Just 
> before Rob set up the open repos I finished converting most of those to 
> list_head, the only one left is in the sa_event mechanism.  Rather than 
> convert it I'd like to replace the use of sa_event with notifier call 
> chains.  I just need to finish auditing the use to make sure the 
> differences won't cause unexpected problems.
>
> After than and unwrapping kernel functions, I think the only thing left 
> before completly removing libsa is to open code the state machines.
>
> Similarly I think net_types.h need to go.
>
>   
Hi All,

[resending as plain text -sorry].

I've had a start at getting rid of sa_state, but I haven't tested it
yet.  It's a pretty straightforward change to just call the new state
routine directly instead of going through the table.  I'll submit that
in the next week or so, or if desired, someone else can take over the
work from the code I have.

           Joe

      reply	other threads:[~2007-11-28 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27 18:49 [ANNOUNCE] Open-FCoE - Fibre Channel over Ethernet Project Love, Robert W
2007-11-28  7:44 ` Christoph Hellwig
2007-11-28 17:53   ` Chris Leech
2007-11-28 20:08     ` Joe Eykholt [this message]

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=474DCAA5.3020108@nuovasystems.com \
    --to=joe@nuovasystems.com \
    --cc=arjan.van.de.ven@intel.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=christopher.leech@intel.com \
    --cc=davem@davemloft.net \
    --cc=devel@open-fcoe.org \
    --cc=hch@infradead.org \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=jeff@garzik.org \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --cc=vasu.dev@intel.com \
    --cc=yi.zou@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).