All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: benh@kernel.crashing.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] highmem I/O for ide-pmac.c
Date: Thu, 12 Sep 2002 08:20:57 +0200	[thread overview]
Message-ID: <20020912062057.GK30234@suse.de> (raw)
In-Reply-To: <15744.12392.868240.502920@argo.ozlabs.ibm.com>

On Thu, Sep 12 2002, Paul Mackerras wrote:
> Jens Axboe writes:
> 
> > Doesn't look like it's needed at all, at least you never turn on highmem
> > I/O with ide_toggle_bounce() :-)
> 
> Foo, neither I do. :(
> 
> > BTW, it would be ok to export that from ide-dma.c instead of duplicating
> > it in ide-pmac.
> 
> Looking at it again, both ide_build_sglist and ide_raw_build_sglist do
> *almost* what we want.  If ide-pmac used hwif->sg_table instead of
> pmif->sg_table, and if ide_[raw_]build_sglist were exported and took
> the maximum number of entries as a parameter instead of using the
> PRD_ENTRIES constant, then ide-pmac wouldn't need to have its own
> versions of those routines.  Would those changes be OK?

Sounds like a perfectly fine change to me.

> Ben, any reason why we have to use pmif->sg_table rather than
> hwif->sg_table?

Looks identical to me. hwif->sg_table is kmalloc'ed sg list of
PRD_ENTRIES (256), pmif->sg_table is kmalloc'ed ditto of MAX_DCMDS (256)
entries.

-- 
Jens Axboe


  reply	other threads:[~2002-09-12  6:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11 12:48 [PATCH] highmem I/O for ide-pmac.c Paul Mackerras
2002-09-11 13:02 ` Jens Axboe
2002-09-11 13:07   ` Jens Axboe
2002-09-11 13:13     ` Jens Axboe
2002-09-11 18:53   ` Benjamin Herrenschmidt
2002-09-11 18:05     ` Jens Axboe
2002-09-12  6:54       ` Paul Mackerras
2002-09-12  6:59         ` Jens Axboe
2002-09-12  6:12   ` Paul Mackerras
2002-09-12  6:20     ` Jens Axboe [this message]
2002-09-12  5:37       ` Benjamin Herrenschmidt

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=20020912062057.GK30234@suse.de \
    --to=axboe@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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.