mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Bjorn Wesen <bjorn@sparta.lu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: alloc_area_pte: page already exists
Date: Thu, 9 Aug 2001 18:03:44 +0200	[thread overview]
Message-ID: <20010809180344.J4895@athlon.random> (raw)
In-Reply-To: <Pine.LNX.3.96.1010809152133.5473B-100000@medusa.sparta.lu.se>
In-Reply-To: <Pine.LNX.3.96.1010809152133.5473B-100000@medusa.sparta.lu.se>; from bjorn@sparta.lu.se on Thu, Aug 09, 2001 at 03:32:44PM +0200

On Thu, Aug 09, 2001 at 03:32:44PM +0200, Bjorn Wesen wrote:
> I'm trying to track down a problem which seems to be a race condition
> vmalloc page table delayed PTE copying", or "you must never
> call free_kiovec in an interrupt context" etc..)

The latter is certainly the case. The former could be the case, however
if you know you're running any free_kiovec from irqs remove it and try
again first.

BTW, you should also avoid all the kiobuf allocation in all the fast
paths, try to pre-allocate it in a slow path to deliver higher
performance. (shortly we'll split the bh/blocks array out of the kiobuf
in a data structure called kiobuf_io so the non-IO usage will avoid the
overhead of the bh/blocks arrays and it will become lighter but still
it won't be that light)

Andrea

  reply	other threads:[~2001-08-09 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 13:32 Bjorn Wesen
2001-08-09 16:03 ` Andrea Arcangeli [this message]
2001-08-09 15:12   ` Bjorn Wesen
2001-08-09 16:36     ` Andrea Arcangeli
2001-08-09 15:33       ` Bjorn Wesen
2001-08-09 17:04         ` Andrea Arcangeli
2001-08-09 21:50           ` Bjorn Wesen
2001-08-12  9:44             ` Bjorn Wesen
2001-08-12 12:16           ` Bjorn Wesen
2001-08-12 21:43             ` Urban Widmark

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=20010809180344.J4895@athlon.random \
    --to=andrea@suse.de \
    --cc=bjorn@sparta.lu.se \
    --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®