From: Jens Axboe <jens.axboe@oracle.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Geoff Levand <geoffrey.levand@am.sony.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Jim Paris <jim@jtan.com>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
linux-mtd@lists.infradead.org,
Vivien Chappelier <vivien.chappelier@free.fr>,
David Woodhouse <dwmw2@infradead.org>,
Cell Broadband Engine OSS Development <cbe-oss-dev@ozlabs.org>
Subject: Re: [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device
Date: Thu, 5 Mar 2009 09:37:01 +0100 [thread overview]
Message-ID: <20090305083701.GQ11787@kernel.dk> (raw)
In-Reply-To: <alpine.LRH.2.00.0903041444300.32279@vixen.sonytel.be>
On Wed, Mar 04 2009, Geert Uytterhoeven wrote:
> Hi,
>
> Below is the rewrite of the PS3 Video RAM Storage Driver as a plain block
> device, as requested by Arnd Bergmann.
>
> The MTD-based PS3 Video RAM Storage Driver was integrated into the mainline
> kernel in 2.6.29-rc1.
>
> Ideally, we think it would be best if the existing MTD-based ps3vram driver
> would be replaced by the new block-based ps3vram driver before 2.6.29 is
> released. This would relieve the burden of supporting two different swap space
> schemes on PS3 (swap on /dev/mtdblock0 vs. /dev/ps3vram) from the distro
> maintainer's shoulders, as in that case there would never have been a stable
> kernel version containing the MTD-based ps3vram driver.
>
> What do you think? If this is accepted, I'll submit a patch to remove the MTD
> ps3vram and add the new driver as ps3vram (instead of ps3vram-ng).
>
> Thanks for your (review and other) comments!
I'd rewrite this as a ->make_request_fn handler instead. Then you can
get rid of the kernel thread. IOW, change
queue = blk_init_queue(ps3vram_request, &priv->lock);
to
queue = blk_alloc_queue(GFP_KERNEL);
blk_queue_make_request(queue, ps3vram_make_request);
Add error handling of course, and call blk_queue_max_*() to set your
limits for this device. Then add a ps3vram_make_request() ala:
static void ps3vram_do_request(struct request_queue *q, struct bio *bio)
{
struct ps3_system_bus_device *dev = q->queuedata;
struct ps3vram_priv *priv = dev->core.driver_data;
int write, res, err = -EIO;
struct bio_vec *bv;
sector_t sector;
loff_t offset;
size_t len, retlen;
int i;
write = bio_data_dir(bio) == WRITE;
sector = bio->bi_sector;
bio_for_each_segment(bv, bio, i) {
char *ptr = page_address(bv->bv_page) + bv->bv_offset;
len = bv->bv_len;
offset = sector << 9;
if (write)
res = ps3vram_write(dev, offset, len, &retlen, ptr);
else
res = ps3vram_read(dev, offset, len, &retlen, ptr);
if (res) {
dev_err(&dev->core, "%s failed\n", op);
goto out;
}
if (retlen != len) {
dev_err(&dev->core, "Short %s\n", op);
goto out;
}
sector += (len >> 9);
}
dev_dbg(&dev->core, "%s completed\n", op);
err = 0;
out:
bio_endio(bio, err);
}
I just typed it here, so if it doesn't compile you get to keep the
pieces :-)
Since ps3 is very RAM limited, I didn't bother with any highmem mapping
for the bio, since I gather that isn't an issue on that platform. You
may want to detail that in a comment above the page_addres() thing at
the top of the loop, though.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
Jim Paris <jim@jtan.com>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
linux-mtd@lists.infradead.org,
Vivien Chappelier <vivien.chappelier@free.fr>,
David Woodhouse <dwmw2@infradead.org>,
Cell Broadband Engine OSS Development <cbe-oss-dev@ozlabs.org>
Subject: Re: [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device
Date: Thu, 5 Mar 2009 09:37:01 +0100 [thread overview]
Message-ID: <20090305083701.GQ11787@kernel.dk> (raw)
In-Reply-To: <alpine.LRH.2.00.0903041444300.32279@vixen.sonytel.be>
On Wed, Mar 04 2009, Geert Uytterhoeven wrote:
> Hi,
>
> Below is the rewrite of the PS3 Video RAM Storage Driver as a plain block
> device, as requested by Arnd Bergmann.
>
> The MTD-based PS3 Video RAM Storage Driver was integrated into the mainline
> kernel in 2.6.29-rc1.
>
> Ideally, we think it would be best if the existing MTD-based ps3vram driver
> would be replaced by the new block-based ps3vram driver before 2.6.29 is
> released. This would relieve the burden of supporting two different swap space
> schemes on PS3 (swap on /dev/mtdblock0 vs. /dev/ps3vram) from the distro
> maintainer's shoulders, as in that case there would never have been a stable
> kernel version containing the MTD-based ps3vram driver.
>
> What do you think? If this is accepted, I'll submit a patch to remove the MTD
> ps3vram and add the new driver as ps3vram (instead of ps3vram-ng).
>
> Thanks for your (review and other) comments!
I'd rewrite this as a ->make_request_fn handler instead. Then you can
get rid of the kernel thread. IOW, change
queue = blk_init_queue(ps3vram_request, &priv->lock);
to
queue = blk_alloc_queue(GFP_KERNEL);
blk_queue_make_request(queue, ps3vram_make_request);
Add error handling of course, and call blk_queue_max_*() to set your
limits for this device. Then add a ps3vram_make_request() ala:
static void ps3vram_do_request(struct request_queue *q, struct bio *bio)
{
struct ps3_system_bus_device *dev = q->queuedata;
struct ps3vram_priv *priv = dev->core.driver_data;
int write, res, err = -EIO;
struct bio_vec *bv;
sector_t sector;
loff_t offset;
size_t len, retlen;
int i;
write = bio_data_dir(bio) == WRITE;
sector = bio->bi_sector;
bio_for_each_segment(bv, bio, i) {
char *ptr = page_address(bv->bv_page) + bv->bv_offset;
len = bv->bv_len;
offset = sector << 9;
if (write)
res = ps3vram_write(dev, offset, len, &retlen, ptr);
else
res = ps3vram_read(dev, offset, len, &retlen, ptr);
if (res) {
dev_err(&dev->core, "%s failed\n", op);
goto out;
}
if (retlen != len) {
dev_err(&dev->core, "Short %s\n", op);
goto out;
}
sector += (len >> 9);
}
dev_dbg(&dev->core, "%s completed\n", op);
err = 0;
out:
bio_endio(bio, err);
}
I just typed it here, so if it doesn't compile you get to keep the
pieces :-)
Since ps3 is very RAM limited, I didn't bother with any highmem mapping
for the bio, since I gather that isn't an issue on that platform. You
may want to detail that in a comment above the page_addres() thing at
the top of the loop, though.
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Jim Paris <jim@jtan.com>,
Vivien Chappelier <vivien.chappelier@free.fr>,
David Woodhouse <dwmw2@infradead.org>,
Arnd Bergmann <arnd@arndb.de>,
Geoff Levand <geoffrey.levand@am.sony.com>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
Cell Broadband Engine OSS Development <cbe-oss-dev@ozlabs.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device
Date: Thu, 5 Mar 2009 09:37:01 +0100 [thread overview]
Message-ID: <20090305083701.GQ11787@kernel.dk> (raw)
In-Reply-To: <alpine.LRH.2.00.0903041444300.32279@vixen.sonytel.be>
On Wed, Mar 04 2009, Geert Uytterhoeven wrote:
> Hi,
>
> Below is the rewrite of the PS3 Video RAM Storage Driver as a plain block
> device, as requested by Arnd Bergmann.
>
> The MTD-based PS3 Video RAM Storage Driver was integrated into the mainline
> kernel in 2.6.29-rc1.
>
> Ideally, we think it would be best if the existing MTD-based ps3vram driver
> would be replaced by the new block-based ps3vram driver before 2.6.29 is
> released. This would relieve the burden of supporting two different swap space
> schemes on PS3 (swap on /dev/mtdblock0 vs. /dev/ps3vram) from the distro
> maintainer's shoulders, as in that case there would never have been a stable
> kernel version containing the MTD-based ps3vram driver.
>
> What do you think? If this is accepted, I'll submit a patch to remove the MTD
> ps3vram and add the new driver as ps3vram (instead of ps3vram-ng).
>
> Thanks for your (review and other) comments!
I'd rewrite this as a ->make_request_fn handler instead. Then you can
get rid of the kernel thread. IOW, change
queue = blk_init_queue(ps3vram_request, &priv->lock);
to
queue = blk_alloc_queue(GFP_KERNEL);
blk_queue_make_request(queue, ps3vram_make_request);
Add error handling of course, and call blk_queue_max_*() to set your
limits for this device. Then add a ps3vram_make_request() ala:
static void ps3vram_do_request(struct request_queue *q, struct bio *bio)
{
struct ps3_system_bus_device *dev = q->queuedata;
struct ps3vram_priv *priv = dev->core.driver_data;
int write, res, err = -EIO;
struct bio_vec *bv;
sector_t sector;
loff_t offset;
size_t len, retlen;
int i;
write = bio_data_dir(bio) == WRITE;
sector = bio->bi_sector;
bio_for_each_segment(bv, bio, i) {
char *ptr = page_address(bv->bv_page) + bv->bv_offset;
len = bv->bv_len;
offset = sector << 9;
if (write)
res = ps3vram_write(dev, offset, len, &retlen, ptr);
else
res = ps3vram_read(dev, offset, len, &retlen, ptr);
if (res) {
dev_err(&dev->core, "%s failed\n", op);
goto out;
}
if (retlen != len) {
dev_err(&dev->core, "Short %s\n", op);
goto out;
}
sector += (len >> 9);
}
dev_dbg(&dev->core, "%s completed\n", op);
err = 0;
out:
bio_endio(bio, err);
}
I just typed it here, so if it doesn't compile you get to keep the
pieces :-)
Since ps3 is very RAM limited, I didn't bother with any highmem mapping
for the bio, since I gather that isn't an issue on that platform. You
may want to detail that in a comment above the page_addres() thing at
the top of the loop, though.
--
Jens Axboe
next prev parent reply other threads:[~2009-03-05 8:37 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 13:57 [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device Geert Uytterhoeven
2009-03-04 13:57 ` Geert Uytterhoeven
2009-03-04 13:57 ` Geert Uytterhoeven
2009-03-04 23:27 ` Benjamin Herrenschmidt
2009-03-04 23:27 ` Benjamin Herrenschmidt
2009-03-04 23:27 ` Benjamin Herrenschmidt
2009-03-05 6:54 ` Jens Axboe
2009-03-05 6:54 ` Jens Axboe
2009-03-05 6:54 ` Jens Axboe
2009-03-06 12:54 ` [PATCH] ps3/block: Replace mtd/ps3vram by block/ps3vram (was: Re: [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device) Geert Uytterhoeven
2009-03-06 12:54 ` Geert Uytterhoeven
2009-03-06 12:54 ` Geert Uytterhoeven
2009-03-09 17:51 ` [PATCH] ps3/block: Replace mtd/ps3vram by block/ps3vram Geoff Levand
2009-03-09 17:51 ` Geoff Levand
2009-03-05 0:21 ` [Cbe-oss-dev] [PATCH/RFC] ps3/block: Add ps3vram-ng driver for accessing video RAM as block device Marcus G. Daniels
2009-03-05 0:21 ` Marcus G. Daniels
2009-03-05 0:21 ` Marcus G. Daniels
2009-03-05 7:17 ` Olaf Hering
2009-03-05 7:17 ` Olaf Hering
2009-03-05 7:17 ` Olaf Hering
2009-03-05 7:59 ` Geert Uytterhoeven
2009-03-05 7:59 ` Geert Uytterhoeven
2009-03-05 7:59 ` Geert Uytterhoeven
2009-03-05 10:24 ` Geert Uytterhoeven
2009-03-05 10:24 ` Geert Uytterhoeven
2009-03-05 10:24 ` Geert Uytterhoeven
2009-03-05 18:12 ` Olaf Hering
2009-03-05 18:12 ` Olaf Hering
2009-03-05 18:12 ` Olaf Hering
2009-03-05 8:37 ` Jens Axboe [this message]
2009-03-05 8:37 ` Jens Axboe
2009-03-05 8:37 ` Jens Axboe
2009-03-05 10:50 ` Geert Uytterhoeven
2009-03-05 10:50 ` Geert Uytterhoeven
2009-03-05 10:50 ` Geert Uytterhoeven
2009-03-05 11:09 ` Jens Axboe
2009-03-05 11:09 ` Jens Axboe
2009-03-05 11:09 ` Jens Axboe
2009-03-05 16:45 ` Geert Uytterhoeven
2009-03-05 16:45 ` Geert Uytterhoeven
2009-03-05 16:45 ` Geert Uytterhoeven
2009-03-06 7:46 ` Jens Axboe
2009-03-06 7:46 ` Jens Axboe
2009-03-06 7:46 ` Jens Axboe
2009-03-06 12:48 ` Geert Uytterhoeven
2009-03-06 12:48 ` Geert Uytterhoeven
2009-03-06 12:48 ` Geert Uytterhoeven
2009-03-06 12:58 ` Jens Axboe
2009-03-06 12:58 ` Jens Axboe
2009-03-06 12:58 ` Jens Axboe
2009-03-06 14:26 ` Geert Uytterhoeven
2009-03-06 14:26 ` Geert Uytterhoeven
2009-03-06 14:26 ` Geert Uytterhoeven
2009-03-06 19:03 ` Jens Axboe
2009-03-06 19:03 ` Jens Axboe
2009-03-06 19:03 ` Jens Axboe
2009-03-09 10:43 ` Geert Uytterhoeven
2009-03-09 10:43 ` Geert Uytterhoeven
2009-03-09 10:43 ` Geert Uytterhoeven
2009-03-09 10:48 ` Jens Axboe
2009-03-09 10:48 ` Jens Axboe
2009-03-09 10:48 ` Jens Axboe
2009-03-09 10:50 ` Jens Axboe
2009-03-09 10:50 ` Jens Axboe
2009-03-09 10:50 ` Jens Axboe
2009-03-09 10:52 ` Geert Uytterhoeven
2009-03-09 10:52 ` Geert Uytterhoeven
2009-03-09 10:52 ` Geert Uytterhoeven
2009-03-09 10:58 ` Jens Axboe
2009-03-09 10:58 ` Jens Axboe
2009-03-09 10:58 ` 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=20090305083701.GQ11787@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=geoffrey.levand@am.sony.com \
--cc=jim@jtan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=vivien.chappelier@free.fr \
/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.