public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matt D. Robinson" <yakker@alacritech.com>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@zip.com.au>, linux-kernel@vger.kernel.org
Subject: Re: direct-to-BIO for O_DIRECT
Date: Mon, 08 Jul 2002 08:03:24 -0700	[thread overview]
Message-ID: <3D29A9BC.266EC55E@alacritech.com> (raw)
In-Reply-To: p73adp2wugy.fsf@oldwotan.suse.de

Andi Kleen wrote:
> 
> Andrew Morton <akpm@zip.com.au> writes:
> 
> >       drivers/md/lvm-snap.c
> >       drivers/media/video/video-buf.c
> >       drivers/mtd/devices/blkmtd.c
> >       drivers/scsi/sg.c
> >
> > the video and mtd drivers seems to be fairly easy to de-kiobufize.
> > I'm aware of one proprietary driver which uses kiobufs.  XFS uses
> > kiobufs a little bit - just to map the pages.
> 
> lkcd uses it too for its kernel crash dump. I suspect it wouldn't be that
> hard to change.
> 

We can remove their use from our 2.5 tree.  Not a problem, as
there are other ways to accomplish what we want.

> -Andi

--Matt

  parent reply	other threads:[~2002-07-08 15:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3D2904C5.53E38ED4@zip.com.au.suse.lists.linux.kernel>
2002-07-08  7:26 ` direct-to-BIO for O_DIRECT Andi Kleen
2002-07-08  9:19   ` Suparna Bhattacharya
2002-07-08 15:03   ` Matt D. Robinson [this message]
2002-07-11  6:09 Adam J. Richter
  -- strict thread matches above, loose matches on Subject: below --
2002-07-09  3:57 Douglas Gilbert
2002-07-09  4:26 ` Andrew Morton
2002-07-09  8:16   ` Ingo Oeser
2002-07-11 17:28   ` Ingo Oeser
2002-07-11 20:43   ` Daniel Phillips
2002-07-08  3:19 Andrew Morton
2002-07-08  3:30 ` Lincoln Dale
2002-07-08  7:44 ` Ingo Oeser
2002-07-11  2:25 ` Lincoln Dale
2002-07-11  3:24   ` Andrew Morton
2002-07-11  3:25     ` Lincoln Dale
2002-07-11 19:52   ` Jesse Barnes
2002-07-11 23:40     ` Lincoln Dale

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=3D29A9BC.266EC55E@alacritech.com \
    --to=yakker@alacritech.com \
    --cc=ak@suse.de \
    --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