public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	V Ganesh <ganesh@veritas.com>,
	lkml <linux-kernel@vger.kernel.org>, Steve Lord <lord@sgi.com>
Subject: Re: inode->i_dirty_buffers redundant ?
Date: Fri, 26 Jan 2001 17:34:17 +0000	[thread overview]
Message-ID: <20010126173417.A14943@redhat.com> (raw)
In-Reply-To: <20010125164432.A12984@redhat.com> <Pine.LNX.4.21.0101251907110.11559-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0101251907110.11559-100000@freak.distro.conectiva>; from marcelo@conectiva.com.br on Thu, Jan 25, 2001 at 07:11:01PM -0200

Hi,

On Thu, Jan 25, 2001 at 07:11:01PM -0200, Marcelo Tosatti wrote:
> 
> We probably want another kind of "IO buffer" abstraction for 2.5 which can
> support buffer's bigger than PAGE_SIZE. 
> 
> Do you have any thoughts on that, Stephen? 

XFS is already doing this, with pagebufs being used in their cache,
and kiobufs used for the IO submission.

--Stephen
-
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-26 17:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25 10:47 inode->i_dirty_buffers redundant ? V Ganesh
2001-01-25 16:44 ` Stephen C. Tweedie
2001-01-25 20:05   ` Daniel Phillips
2001-01-25 21:30     ` Marcelo Tosatti
2001-01-26 11:35     ` Stephen C. Tweedie
2001-01-26 19:05       ` Daniel Phillips
2001-01-25 21:11   ` Marcelo Tosatti
2001-01-26 17:34     ` Stephen C. Tweedie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-26  9:13 V Ganesh
2001-01-24  9:55 V Ganesh
2001-01-24  9:09 ` Marcelo Tosatti
2001-01-24 11:26 ` Stephen C. Tweedie

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=20010126173417.A14943@redhat.com \
    --to=sct@redhat.com \
    --cc=ganesh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lord@sgi.com \
    --cc=marcelo@conectiva.com.br \
    /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