[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120904212145.GC3602@redhat.com>
Date: Wed, 5 Sep 2012 00:21:45 +0300
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Or Gerlitz <or.gerlitz@...il.com>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
Or Gerlitz <ogerlitz@...lanox.com>, davem@...emloft.net,
roland@...nel.org, netdev@...r.kernel.org, sean.hefty@...el.com,
Erez Shitrit <erezsh@...lanox.co.il>,
Ali Ayoub <ali@...lanox.com>,
Doug Ledford <dledford@...hat.com>
Subject: Re: [PATCH V2 09/12] net/eipoib: Add main driver functionality
On Tue, Sep 04, 2012 at 09:50:09PM +0300, Or Gerlitz wrote:
> > And just to stress the point, document the limitations as well.
>
> sure, not that I see concrete limitations for the **user** at this point, but
> if there are such, will put them clearly written.
Hmm, I'm afraid you mistook a short list of some major
bugs that jumped out at me for an exhaustive list.
This was not intended as such.
Here's how to find some of the limitations in your design
1. look through list archives. Some where pointed out to you
2. list everything ethernet does that you dont, or do differently
3. list everything ipoib does that you don't or do differently
4. list any extra setup work required on behalf of the user
5. check various overheads, compare with native ipoib and alternatives
such as routing
6. if you still have an empty list of limitations and disadvantages,
look again :)
The point is to have documentation that is useful both
for reviewers - so they can know which bugs are known
and which need to be reported; and for users -
who should not be expected to be familiar with
internals of your implementation.
--
MST
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists