All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: PATCH - InfiniBand Access Layer (IBAL)
Date: Mon, 15 Mar 2004 16:18:00 -0800	[thread overview]
Message-ID: <20040316001800.GF30801@sventech.com> (raw)
In-Reply-To: <20040316000906.A24435@infradead.org>

On Tue, Mar 16, 2004, Christoph Hellwig <hch@infradead.org> wrote:
> On Mon, Mar 15, 2004 at 03:54:14PM -0800, Johannes Erdfelt wrote:
> > > Did you actually read it?
> > 
> > The code on openib.org? Yes, I wrote some of it.
> > 
> > I would be the first to say that there are portions that need to be
> > rewritten, but I definately do not think all or even most of it does.
> > 
> > That's why I was asking what specifically you found fatally wrong with
> > it. I haven't seen many critiques, so I can only assume it's the same
> > things I see wrong with it.
> 
> Start with the thing Robert already mentioned.  Ad ontop of that:
> 
>  - the horrible Winodes/Linux compat code.  We all know this kind
>    of compat code is messy.  But the way it's don in this code is just
>    incredibly idiotic.
>  - totally braindead use of macro abstraction
>  - those split into far too many files
>  - wrong use of dma mapping abstraction
>  - braindead malloc code
>  - wrong modversions handling duplicated in every file
> 
> I'm really surprised you're admitting to having touched that code.
> I'd have guessed everyone who did would hide in his house ashamed.

You do realize that the code on openib.org is from multiple vendors,
right? I only touched one part of that code. That's why I said 'some'.

Only some of the code has the problems you listed, and some of those are
far from fatal.

How about I ask you what parts of the code do you feel don't need a
complete rewrite?

> > > p.s.  if you reply to my mails please keep me in the To line.  Really,
> > > please don't do any fany reply to group tricks unless people explicitly
> > > request it in the Mail-Fup header.
> > 
> > If you really want duplicates of all the replies, sure, I'll make an
> > exception for you.
> > 
> > I don't see why a smarter client, or mail filter, couldn't do the same
> > thing without depending on the behaviour of the sender.
> 
> Replying to people personally is good taste.  You might know I'm on
> lkml but on many other lists I'm not.  As are other people on lkml.
> A filter can easily filter out duplicates but it can't magically
> create copies of mails not addressed to you. 

Sure it can. I replied to your email. Check the mail headers,
specifically the ones labeled References and In-Reply-To.

> In addition I tend to read my inbox fairly quick all the time and
> the lkml mailbox only when I'm at least a little idle.

I didn't need an immediate answer.

JE


  reply	other threads:[~2004-03-16  0:45 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15 22:52 PATCH - InfiniBand Access Layer (IBAL) Woodruff, Robert J
2004-03-15 23:17 ` Christoph Hellwig
2004-03-15 23:44   ` Johannes Erdfelt
2004-03-15 23:48     ` Christoph Hellwig
2004-03-15 23:54       ` Johannes Erdfelt
2004-03-16  0:09         ` Christoph Hellwig
2004-03-16  0:18           ` Johannes Erdfelt [this message]
2004-03-16  1:41 ` Roland Dreier
2004-03-19 18:47 ` Ulrich Drepper
2004-03-19 19:21   ` Fab Tillier
2004-03-19 20:20     ` Ulrich Drepper
2004-03-19 20:47   ` Roland Dreier
  -- strict thread matches above, loose matches on Subject: below --
2004-03-20 19:15 Acker, Dave
2004-03-20 17:15 Acker, Dave
2004-03-20 17:55 ` Ulrich Drepper
2004-03-21 22:16   ` Roland Dreier
2004-03-14 23:14 Nivedita Singhvi
2004-03-14  3:46 Woodruff, Robert J
2004-03-15  2:10 ` Greg KH
2004-03-13 22:07 Woodruff, Robert J
2004-03-14  1:13 ` Andrew Morton
2004-03-14  2:28 ` Greg KH
2004-02-24 23:02 Woodruff, Robert J
2004-02-25  3:32 ` Rik van Riel
2004-02-24 22:18 Woodruff, Robert J
2004-02-24 21:33 Woodruff, Robert J
2004-02-24 19:29 Woodruff, Robert J
2004-02-24 19:44 ` Greg KH
2004-02-24 19:50   ` Christoph Hellwig
2004-02-24 19:57     ` Greg KH
2004-02-24 22:29       ` Rik van Riel
2004-02-25  0:28         ` Matti Aarnio
2004-02-25  3:39           ` Rik van Riel
2004-02-25 16:25             ` Timothy Miller
2004-02-25 17:34               ` Roland Dreier
2004-02-25 18:55               ` Sam Ravnborg
2004-02-25 18:05                 ` Linus Torvalds
2004-02-25 19:09                   ` Timothy Miller
2004-02-25 19:55                   ` Sam Ravnborg
2004-02-25 19:05                     ` Linus Torvalds
2004-02-25 13:19           ` Christoph Hellwig

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=20040316001800.GF30801@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.