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:36:35 +0200 [thread overview]
Message-ID: <20010809183634.K4895@athlon.random> (raw)
In-Reply-To: <20010809180344.J4895@athlon.random> <Pine.LNX.3.96.1010809170813.5473D-100000@medusa.sparta.lu.se>
In-Reply-To: <Pine.LNX.3.96.1010809170813.5473D-100000@medusa.sparta.lu.se>; from bjorn@sparta.lu.se on Thu, Aug 09, 2001 at 05:12:43PM +0200
On Thu, Aug 09, 2001 at 05:12:43PM +0200, Bjorn Wesen wrote:
> Yes, I found it. The irq which signals end-of-I/O also frees the kiovec,
> which is bad. But it seemed that what would happen then would be deadlocks
> (due to the spinlocks) and not races - but I'll try to make it free in a
In SMP the most obvious sympthom would be a deadlock right, but maybe
you're testing with a kernel compiled UP?
The locking there looks quite sane.
> task or something instead (there is no kernel context for the "calling"
> process because the driver is asynchronous so the context which did the
> alloc_kiovec etc. has exited when the irq comes later) and see if it works
> better.
Ok.
> > 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
>
> Ok, that's probably not a problem since the allocation is done in a normal
> system-call context.
Ok.
Andrea
next prev parent reply other threads:[~2001-08-09 16:36 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
2001-08-09 15:12 ` Bjorn Wesen
2001-08-09 16:36 ` Andrea Arcangeli [this message]
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=20010809183634.K4895@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®