From: Jens Axboe <axboe@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: Andy Chittenden <AChittenden@bluearc.com>,
Anton Altaparmakov <aia21@cam.ac.uk>,
Andrew Morton <akpm@osdl.org>,
davej@redhat.com, linux-kernel@vger.kernel.org,
lwoodman@redhat.com,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: adding swap workarounds oom - was: Re: Out of Memory: Killed process 16498 (java).
Date: Thu, 2 Mar 2006 13:26:14 +0100 [thread overview]
Message-ID: <20060302122614.GK4329@suse.de> (raw)
In-Reply-To: <200603021321.09082.ak@suse.de>
On Thu, Mar 02 2006, Andi Kleen wrote:
> On Thursday 02 March 2006 12:10, Jens Axboe wrote:
>
> > I'm waiting for Andi to render an opinion on the problem. It should have
> > no corruption implications, the PIO path will handle arbitrarily large
> > requests. I'm assuming the mapped sg table is correct, just odd looking
> > for some reason.
>
> I was waiting for feedback if iommu=nomerge changes anything. With that option
> the IOMMU code will never touch the layout of the sg list, just rewrite
> ->dma_address
Andy already reported that it didn't change anything. The output doesn't
looked merged anyways in most of the cases, it's the offsetting that
looks odd.
--
Jens Axboe
next prev parent reply other threads:[~2006-03-02 12:26 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 10:46 adding swap workarounds oom - was: Re: Out of Memory: Killed process 16498 (java) Andy Chittenden
2006-03-02 11:10 ` Jens Axboe
2006-03-02 12:21 ` Andi Kleen
2006-03-02 12:26 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-03 9:16 Andy Chittenden
[not found] <89E85E0168AD994693B574C80EDB9C270393C141@uk-email.terastack.bluearc.com>
2006-03-01 15:57 ` Jens Axboe
2006-03-01 14:40 Andy Chittenden
2006-03-01 13:34 Andy Chittenden
2006-03-01 13:41 ` Jens Axboe
2006-03-01 14:05 ` Andi Kleen
2006-03-01 14:18 ` Jens Axboe
2006-03-01 14:26 ` Andi Kleen
2006-03-01 14:34 ` Jens Axboe
2006-03-01 14:41 ` Andi Kleen
2006-03-01 15:00 ` Jens Axboe
2006-03-01 10:47 Andy Chittenden
2006-03-01 12:15 ` Jens Axboe
2006-03-01 12:19 ` Jens Axboe
2006-03-01 12:23 ` Andi Kleen
2006-03-01 12:25 ` Jens Axboe
2006-03-01 9:42 Andy Chittenden
2006-03-01 9:55 ` Jens Axboe
2006-02-28 10:27 Andy Chittenden
2006-02-28 10:29 ` Jens Axboe
2006-02-28 10:10 Andy Chittenden
2006-02-28 10:20 ` Jens Axboe
2006-02-27 16:39 Andy Chittenden
2006-02-27 14:50 Andy Chittenden
2006-02-27 14:56 ` Jens Axboe
[not found] <89E85E0168AD994693B574C80EDB9C270393BF0E@uk-email.terastack.bluearc.com>
2006-02-27 14:28 ` Jens Axboe
2006-02-24 9:33 Andy Chittenden
2006-02-22 10:43 Andy Chittenden
2006-02-22 13:34 ` Jens Axboe
2006-02-22 13:35 ` Jens Axboe
2006-02-22 13:38 ` Jens Axboe
2006-02-03 13:56 Andy Chittenden
2006-02-03 14:00 ` Jens Axboe
2006-01-27 11:53 Andy Chittenden
2006-01-27 14:21 ` Jens Axboe
2006-01-27 14:39 ` Anton Altaparmakov
2006-02-03 9:20 ` adding swap workarounds oom - was: " Anton Altaparmakov
2006-02-03 9:26 ` Andrew Morton
2006-02-03 11:01 ` Anton Altaparmakov
2006-02-03 13:54 ` Jens Axboe
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=20060302122614.GK4329@suse.de \
--to=axboe@suse.de \
--cc=AChittenden@bluearc.com \
--cc=aia21@cam.ac.uk \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bzolnier@gmail.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwoodman@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).