All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Christoph Hellwig <hch@infradead.org>,
	Dan Aloni <da-x@monatomic.org>, Luke-Jr <luke-jr@utopios.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.4.x] prevent emulated SCSI hosts from wasting DMA memory
Date: Wed, 21 Dec 2005 16:17:32 -0200	[thread overview]
Message-ID: <20051221181732.GC28272@dmt.cnet> (raw)
In-Reply-To: <20051201113610.GG3958@infradead.org>

On Thu, Dec 01, 2005 at 11:36:10AM +0000, Christoph Hellwig wrote:
> On Wed, Nov 30, 2005 at 11:02:23PM +0200, Dan Aloni wrote:
> > On Wed, Nov 30, 2005 at 07:33:47PM +0000, Luke-Jr wrote:
> > > On Wednesday 30 November 2005 17:15, Dan Aloni wrote:
> > > > Emulated scsi hosts don't do DMA, so don't unnecessarily increase
> > > > the SCSI DMA pool.
> > > 
> > > They don't? Recently I learned(?) that apparently using hdparm -d on the 
> > > old /dev/hdX device still worked/applied when using ide-scsi... or do 
> > > "emulated scsi hosts" refer to something else?
> > 
> > Actually by 'do DMA' I meant use the scsi_malloc() interface - which 
> > is mostly used by low level drivers. The IDE drivers allocate their
> > DMA memory outside the SCSI layer. iSCSI hosts for instance, don't 
> > need to cause unnecessary DMA allocations.
> 
> (1) there's no guranteee a driver setting ->emulated can't use scsi_malloc
> (2) 2.4.x is very late in the cycle so there's just no point in putting this
>     in (and in 2.6.x scsi_malloc is gone fortunately)

Agreed - this does not sound like a critical bug fix to me.

      parent reply	other threads:[~2005-12-21 18:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-30 17:15 [PATCH 2.4.x] prevent emulated SCSI hosts from wasting DMA memory Dan Aloni
2005-11-30 19:33 ` Luke-Jr
2005-11-30 21:02   ` Dan Aloni
2005-12-01 11:36     ` Christoph Hellwig
2005-12-01 15:39       ` Dan Aloni
2005-12-21 18:17       ` Marcelo Tosatti [this message]

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=20051221181732.GC28272@dmt.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=da-x@monatomic.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke-jr@utopios.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.