linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: George Pontis <GPontis@z9.com>, linux-mtd@lists.infradead.org
Subject: Re: atmel_nand, DMA, and "Fall back to CPU I/O"
Date: Thu, 03 May 2012 13:35:18 +0300	[thread overview]
Message-ID: <1336041318.13013.30.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CAN8TOE9+WpSrYufSpKXy6RW_V8M_1dZg+uBB6ChmcAWnxmVCnA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

On Wed, 2012-05-02 at 12:32 -0700, Brian Norris wrote:
> 
> And how might you recommend we use kmalloc()'ed memory, Artem? We
> can't really kmalloc() whole eraseblock-sized chunks. Or is there an
> inexpensive way of providing an intermediary kmalloc'ed buffer? I'm
> not too familiar at hacking at UBI(FS), but it might be worth a shot
> sometime, if you think it's reasonable.

This would need to change several places in UBI and UBIFS and switch
from continuous vmalloc buffers to iterating over an array of smaller
buffers.

I was thinking about this in the past but this is rather big project (a
months or a couple I'd say) so I did not have time to do this.

I think we basically need to switch to flexible arrays
(Documentation/flexible-arrays.txt), but last time I looked at this I
remember I decided that flexible arrays functionality would need to be
extended for our purposes.

If someone seriously is going to do this work, I am happy to discuss.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-05-03 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 22:09 atmel_nand, DMA, and "Fall back to CPU I/O" George Pontis
2012-05-02 11:53 ` Artem Bityutskiy
2012-05-02 19:32   ` Brian Norris
2012-05-03 10:35     ` Artem Bityutskiy [this message]

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=1336041318.13013.30.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=GPontis@z9.com \
    --cc=computersforpeace@gmail.com \
    --cc=linux-mtd@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).