All of lore.kernel.org
 help / color / mirror / Atom feed
From: jeremy@classic.engr.sgi.com (Jeremy Higdon)
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: changes to kiobuf support in 2.4.(?)4
Date: Thu, 2 Aug 2001 02:25:48 -0700 (PDT)	[thread overview]
Message-ID: <10108020225.ZM236505@classic.engr.sgi.com> (raw)
In-Reply-To: Andrea Arcangeli <andrea@suse.de> "Re: changes to kiobuf support in 2.4.(?)4" (Aug  2, 11:11am)
In-Reply-To: <10108012254.ZM192062@classic.engr.sgi.com>  <20010802084259.H29065@athlon.random>  <andrea@suse.de>  <10108020031.ZM229058@classic.engr.sgi.com>  <20010802094517.I29065@athlon.random>  <10108020110.ZM232959@classic.engr.sgi.com>  <20010802102431.L29065@athlon.random>  <10108020142.ZM233422@classic.engr.sgi.com>  <20010802111150.N29065@athlon.random>

On Aug 2, 11:11am, Andrea Arcangeli wrote:
> 
> > At 13000 IOPS, when allocating and freeing on every I/O request,
> > the allocate/free overhead was approximately .6% on a 2 CPU system,
> > where the total overhead was about 25%.  So I would theoretically
> > gain 3% (maybe a little better since there is locking involved) if
> > I could avoid the alloc/free.
> 
> Ok good.
> 
> Andrea


So one more question for now:

Where do I get the O_DIRECT patch?

Oh, and is there a plan to get it into 2.4.X?

(ok, so two questions)

thanks

jeremy

  reply	other threads:[~2001-08-02  9:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02  5:55 changes to kiobuf support in 2.4.(?)4 Jeremy Higdon
2001-08-02  6:43 ` Andrea Arcangeli
2001-08-02  7:31   ` Jeremy Higdon
2001-08-02  7:45     ` Andrea Arcangeli
2001-08-02  8:10       ` Jeremy Higdon
2001-08-02  8:24         ` Andrea Arcangeli
2001-08-02  8:42           ` Jeremy Higdon
2001-08-02  9:11             ` Andrea Arcangeli
2001-08-02  9:25               ` Jeremy Higdon [this message]
2001-08-02 10:00                 ` Andrea Arcangeli
2001-08-02  8:23   ` Gerd Knorr
2001-08-03 11:32     ` Ingo Oeser
2001-08-03 12:45     ` Andrea Arcangeli

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=10108020225.ZM236505@classic.engr.sgi.com \
    --to=jeremy@classic.engr.sgi.com \
    --cc=andrea@suse.de \
    --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 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.