public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: KIOBUFS ??
Date: Thu, 11 Jan 2001 18:04:43 +0100	[thread overview]
Message-ID: <20010111180443.I640@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10101100008160.23071-100000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10101100008160.23071-100000@master.linux-ide.org>; from andre@linux-ide.org on Wed, Jan 10, 2001 at 12:28:18AM -0800

On Wed, Jan 10 2001, Andre Hedrick wrote:
> 
> LT,
> 
> Will this maddness insure that the granularity of the request will be
> dependent to the k_dev_t?  Specifically, can one make KIOBUFS do the
> sizing of buffer to match the ideal or specified size limits imposed by a
> given block device?  Otherwise I will need to design an sub-request layer
> to reduce the pain of restarting the entire request because of the huge
> DMA-PRD-Chain that has no clue how to report error location and allow a
> restart from NxPRD's before the error.

Take a look at the XFS tree. I wrote IDE kiobuf support for that, and
it simply doesn't take the request the queue before it has been
completed (which may take many start-ups for a huge request). But unless
you can make the prd table bigger (which doesn't make much sense anyway),
I don't see any harm in setting up sg for each iteration.

-- 
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-01-11 17:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10  8:28 KIOBUFS ?? Andre Hedrick
2001-01-11 17:04 ` Jens Axboe [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=20010111180443.I640@suse.de \
    --to=axboe@suse.de \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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