public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.21pre4aa1
Date: Fri, 31 Jan 2003 17:11:02 +0100	[thread overview]
Message-ID: <20030131161102.GE8395@dualathlon.random> (raw)
In-Reply-To: <20030131105643.B18876@infradead.org>

On Fri, Jan 31, 2003 at 10:56:43AM +0000, Christoph Hellwig wrote:
> On Fri, Jan 31, 2003 at 02:40:20AM +0100, Andrea Arcangeli wrote:
> > Only in 2.4.21pre3aa1: 00_getcwd-err-1
> > Only in 2.4.21pre4aa1: 00_getcwd-err-2
> > 
> > 	Part of it merged in mainline.
> 
> A different, cleaner version has been merged in mainline.  00_getcwd-err-2
> just adds unreachable code.

Ok agreed, it's a noop, I'll drop it. It won't hurt in the meantime.

> 
> > Only in 2.4.21pre4aa1: 9996_kiobuf-slab-1
> > 
> > 	Keep the kiobuf + bhs cache in the slab rather than in the file
> > 	structure, so it scales also while sharing the same file from two
> > 	different filedescriptors at the same time (like with threads or
> > 	after forks). From Jun Nakajima.
> 
> The patch is ugly as hell.  I'll dig up the patch I did with similar

I don't think it's so ugly, infact it's very clever compared to the
previous code, the big hit for the kiobuf is the bh allocation and this
solves it moving the bh into the slab too.

> functionality but a much nicer style and a sysctl-controllable cut-off

sysctl-controllable? I don't like it. This one should perform well
always.

> point for keeping the bhs around in the constructed kiobuf objects.

Feel free to provide a replacement but I don't see how you can make it
that much better as you claim.

The only unclean bit is the initialized field probably, but that's not a
significant cost and it's probably the simpler way to deal with the
ctor failures.

Andrea

  reply	other threads:[~2003-01-31 16:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-31  1:40 2.4.21pre4aa1 Andrea Arcangeli
2003-01-31 10:56 ` 2.4.21pre4aa1 Christoph Hellwig
2003-01-31 16:11   ` Andrea Arcangeli [this message]
2003-02-05 23:12 ` 2.4.21pre4aa1 Samuel Flory
2003-02-05 23:16   ` 2.4.21pre4aa1 Andrea Arcangeli
2003-02-05 23:22     ` 2.4.21pre4aa1 Samuel Flory
2003-02-05 23:45       ` 2.4.21pre4aa1 J.A. Magallon
2003-02-06  9:39       ` 2.4.21pre4aa1 - hard lockup (PCnet32 related?) Sergey S. Kostyliov

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=20030131161102.GE8395@dualathlon.random \
    --to=andrea@suse.de \
    --cc=hch@infradead.org \
    --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