RE: [openib-general] Making gen2 transport neutral

2005-07-01 Thread Caitlin Bestler
: openib-general; [EMAIL PROTECTED] Subject: Re: [openib-general] Making gen2 transport neutral On Thu, Jun 30, 2005 at 08:52:54AM -0700, Caitlin Bestler wrote: structs: typically struct ib_xyz is transformed as follows: struct ib_xyz { /* Only IB specific fields remain

Re: [openib-general] Making gen2 transport neutral

2005-06-30 Thread Christoph Hellwig
On Thu, Jun 30, 2005 at 08:52:54AM -0700, Caitlin Bestler wrote: structs: typically struct ib_xyz is transformed as follows: struct ib_xyz { /* Only IB specific fields remain */ /* In some cases fields have been split, because * iWARP allows

RE: [openib-general] Making gen2 transport neutral

2005-06-30 Thread Caitlin Bestler
-Original Message- From: Christoph Hellwig [mailto:[EMAIL PROTECTED] Sent: Thursday, June 30, 2005 9:03 AM To: Caitlin Bestler Cc: openib-general; [EMAIL PROTECTED] Subject: Re: [openib-general] Making gen2 transport neutral On Thu, Jun 30, 2005 at 08:52:54AM -0700, Caitlin

Re: [openib-general] Making gen2 transport neutral

2005-06-30 Thread Roland Dreier
Christoph Even better make the methods implementing them optional Christoph and let the upper layer return EOPNOTSUPP when it's not Christoph implemeneted. That's what the current drivers/infiniband code does, except we use ENOSYS. However I have no objection to changing to

Re: [openib-general] Making gen2 transport neutral

2005-06-30 Thread Christoph Hellwig
On Thu, Jun 30, 2005 at 09:09:47AM -0700, Caitlin Bestler wrote: If there's a citation in coding standards somewhere that makes this a closed issue please cite it. That would close the discussion quickly. It's far too highlevel for the coding standards documents we have. Maybe I'll find time