From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Robert Pearson
<rpearson-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
Cc: 'Jason Gunthorpe'
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
'frank zago'
<fzago-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
'John Groves'
<john-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
Subject: Re: [Announce] rxe dev tree available (soft RDMAoE)
Date: Thu, 17 Dec 2009 13:25:58 -0800 [thread overview]
Message-ID: <adazl5h47ix.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <031b01ca7e99$38abf510$aa03df30$@com> (Robert Pearson's message of "Wed, 16 Dec 2009 15:46:26 -0600")
> Yes, but later. For now it is still being actively developed and is changing
> a lot. Once it settles down we plan to convert to patches and push up
> stream.
I think you would probably be better off developing the kernel driver as
a branch in an up-to-date kernel tree, and then worrying about backports
later. You could get rid of some of the redundant infrastructure like
dump_hex() and crc32 (too bad IB didn't choose the CRC32C polynomial, so
you can't use the crypto API and get Intel CRC32 instruction
acceleration for free).
- R.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-12-17 21:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 21:06 [Announce] rxe dev tree available (soft RDMAoE) frank zago
[not found] ` <4B294BDD.3010405-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org>
2009-12-16 21:38 ` Jason Gunthorpe
[not found] ` <20091216213816.GV6188-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2009-12-16 21:46 ` Robert Pearson
2009-12-16 22:20 ` Sean Hefty
[not found] ` <7FFE592E129646A2B0DB5AC99D0261C7-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-12-16 22:36 ` Robert Pearson
2009-12-16 23:53 ` Roland Dreier
[not found] ` <adafx7a79xh.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2009-12-17 1:32 ` Dave Olson
2009-12-17 17:36 ` Robert Pearson
2009-12-17 21:25 ` Roland Dreier [this message]
[not found] ` <adazl5h47ix.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2009-12-17 21:43 ` Robert Pearson
2009-12-17 21:56 ` Roland Dreier
2009-12-17 22:04 ` Jason Gunthorpe
[not found] ` <20091217220450.GA8383-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2009-12-17 23:00 ` Robert Pearson
2009-12-17 23:30 ` Jason Gunthorpe
2009-12-17 23:35 ` Roland Dreier
2009-12-17 23:46 ` Roland Dreier
2009-12-17 23:17 ` Robert Pearson
2009-12-17 23:10 ` Robert Pearson
2009-12-17 0:19 ` Woodruff, Robert J
[not found] ` <382A478CAD40FA4FB46605CF81FE39F4431FB84A-osO9UTpF0URzLByeVOV5+bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2009-12-17 0:59 ` fzago-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5
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=adazl5h47ix.fsf@roland-alpha.cisco.com \
--to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=fzago-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=john-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rpearson-klaOcWyJdxkshyMvu7JE4pqQE7yCjDx5@public.gmane.org \
/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