linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Stuart_Hayes@Dell.com
Cc: bzolnier@gmail.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH 2.6.11.6] ide-scsi: kmap scatter/gather before doing PIO
Date: Mon, 2 May 2005 18:01:10 +0200	[thread overview]
Message-ID: <20050502160110.GA4817@suse.de> (raw)
In-Reply-To: <7A8F92187EF7A249BF847F1BF4903C040AFCD0@ausx2kmpc103.aus.amer.dell.com>

On Mon, May 02 2005, Stuart_Hayes@Dell.com wrote:
> >  		idescsi_input_buffers (ide_d return; }
> >  		count = min(pc->sg->length - pc->b_count, bcount);
> > -		buf = page_address(pc->sg->page) + pc->sg->offset;
> > +#ifdef CONFIG_HIGHMEM
> > +		local_irq_save(flags);
> > +#endif
> > 
> > This is just aweful, don't add tons of ifdefs. If you must
> > differentiate, just do something ala: 
> > 
> >         if (PageHighMem(page)) {
> >                 save interrupts
> >                 buf = kmap
> >         } else
> >                 buf = page_address(xxx).
> > 
> > and so on. But why are you still doing it this way? Did we not agree
> > that adding a host template no-high-mem defines was way better?? 
> 
> The ifdefs were at Bart's request.
> 
> The reason I went back to the kmap_atomic() fix instead of adding a  
> no-high-mem flag in the host is that I couldn't get James to accept that

But, why? The no_highmem flag doesn't make sense for regular host
adapters, they can just set pdev->dma_mask appropriately. But we cannot
do that for ide-scsi, so I think it would be acceptable to add it
because of that.

> patch, while this one is ide-scsi only, and Bart did accept it.  And, to
> be honest, I wasn't really sure why the kmap_atomic() fix was inferior.
> 
> But I'd certainly defer to your (or Bart's) judgment on those things--
> you guys have a lot more experience than me with the kernel.  I am
> hesitant to change the "ifdef"s to "if"s at this point, since Bart
> already accepted it (previously) with the ifdefs, but I'd be more than 
> happy to change it if he agrees.

The PageHighMem variant would be acceptable to me, although I still
prefer the highmem bounce approach.

-- 
Jens Axboe


  parent reply	other threads:[~2005-05-02 16:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-02 15:17 [PATCH 2.6.11.6] ide-scsi: kmap scatter/gather before doing PIO Stuart_Hayes
2005-05-02 15:46 ` Bartlomiej Zolnierkiewicz
2005-05-02 16:01   ` Jens Axboe
2005-05-02 16:01 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-02 20:03 Stuart_Hayes
2005-05-02 15:56 Stuart_Hayes
2005-04-29 15:53 Stuart_Hayes
2005-05-01 15:49 ` Jens Axboe
2005-04-29 15:45 Stuart_Hayes
2005-04-05 21:08 Stuart_Hayes
2005-04-05 21:41 ` Bartlomiej Zolnierkiewicz
2005-04-05 19:12 Stuart_Hayes
2005-04-05 20:27 ` Bartlomiej Zolnierkiewicz

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=20050502160110.GA4817@suse.de \
    --to=axboe@suse.de \
    --cc=Stuart_Hayes@Dell.com \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).