mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: bio_chain: proposed solution for bio_alloc failure and large IO simplification
Date: Sat, 15 Jun 2002 11:14:05 +0200	[thread overview]
Message-ID: <20020615091405.GB5990@suse.de> (raw)
In-Reply-To: <200206150910.CAA00831@adam.yggdrasil.com>

On Sat, Jun 15 2002, Adam J. Richter wrote:
> >> 	So, I need a fourth location at in generic_make_request
> >> just before the call to q->make_request_fn, like so:
> >> 
> >> 	if (q->make_request_fn != __make_request) {
> >> 		int flags;
> >> 		spin_lock_irqsave(q->lock, flags);
> >> 		clear_hint(bio);
> >> 		spin_unlock_irqrestore(q->lock, flags);
> >> 	}
> >> 	ret = q->make_request_fn(q, bio);
> 
> >Irk, this is ugly. But how you are moving away from the initial goal (or
> >maybe this was your goal the whole time, just a single merge hint?) of
> >passing back the hint instead of maintaing it in the queue. So let me
> >ask, are you aware of the last_merge I/O scheduler hint? Which does
> >exactly this already...
> 
> 	The code that I think I more or less have in my head has not
> changed (aside from that fourth test).
> 
> 	Although I was not aware of q->last_merge, I see that it is
> not what I want.  I want up to one hint per request, for the last bio
> in the request.  bi_hint would be null for all bio's except possibly
> the last bio in a request.  I do not want just one hint per queue.

.. which, as far as I can see, brings us right back into the problems
with stalling the i/o and other nastiness. So far your approach seems
hackish at best, but ->

> 	If it is unclear what I mean, perhaps I really need to code it
> up to explain it. and we can discuss it from there.

go ahead and code it up if you want and we can discuss it some more.

-- 
Jens Axboe


  reply	other threads:[~2002-06-15  9:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-15  9:10 Adam J. Richter
2002-06-15  9:14 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-15 20:24 Adam J. Richter
2002-06-17  6:37 ` Jens Axboe
2002-06-15 20:01 Adam J. Richter
2002-06-15 20:22 ` Andrew Morton
2002-06-15 10:30 Adam J. Richter
2002-06-15 19:50 ` Andrew Morton
2002-06-17  6:36   ` Jens Axboe
2002-06-17  7:09     ` Andrew Morton
2002-06-15  8:52 Adam J. Richter
2002-06-15  9:00 ` Jens Axboe
2002-06-15  8:45 Adam J. Richter
2002-06-15  8:50 ` Jens Axboe
2002-06-15  4:38 Adam J. Richter
2002-06-15  0:22 Adam J. Richter
2002-06-14 23:39 Adam J. Richter
2002-06-14 23:58 ` Andrew Morton
2002-06-15  1:38   ` Oliver Xymoron
2002-06-15  7:55 ` Jens Axboe
2002-06-14 16:52 Adam J. Richter
2002-06-14 23:00 ` Andrew Morton
2002-06-14 23:29   ` William Lee Irwin III
2002-06-14 23:38     ` Andrew Morton
2002-06-15  7:55 ` Jens Axboe
2002-06-14  1:56 Adam J. Richter
2002-06-14  2:24 ` Andreas Dilger
2002-06-14 14:57 ` Jens Axboe

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=20020615091405.GB5990@suse.de \
    --to=axboe@suse.de \
    --cc=adam@yggdrasil.com \
    --cc=akpm@zip.com.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®