summaryrefslogtreecommitdiff
path: root/hurd/translator/ext2fs.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2013-04-07 18:18:44 +0200
committerThomas Schwinge <tschwinge@gnu.org>2013-04-07 18:18:44 +0200
commit6c7d45e4631784d0e077e806521a736da6b0266e (patch)
treef9d3e9ed304e8cdbf72fc77c135781eb49990f6a /hurd/translator/ext2fs.mdwn
parentf8ed211a4da23edf469089254b3dace9479bf11f (diff)
IRC.
Diffstat (limited to 'hurd/translator/ext2fs.mdwn')
-rw-r--r--hurd/translator/ext2fs.mdwn31
1 files changed, 31 insertions, 0 deletions
diff --git a/hurd/translator/ext2fs.mdwn b/hurd/translator/ext2fs.mdwn
index 65361ff4..b276ff0c 100644
--- a/hurd/translator/ext2fs.mdwn
+++ b/hurd/translator/ext2fs.mdwn
@@ -89,6 +89,37 @@ small backend stores, like floppy devices.
<youpi> which can be quite probable
+##### IRC, freenode, #hurd, 2013-03-19
+
+ <braunr> youpi: i'm back on polishing the large store patch
+ <braunr> did you remember seeing something else than the bzero/memset
+ out-of-scope changes ?
+ <braunr> (i mean, readily noticeable)
+ <youpi> I don't remember
+ <braunr> ok
+ <braunr> the original code already assumes mmap succeeds
+ <braunr> is it ok to consider the patch can do the same ?
+ <youpi> I'd say so
+ <braunr> ok
+ <braunr> youpi: actually, it looks like a good part of the patch isn't
+ related to large stores
+ <braunr> for example, in ext2fs/inode.c, there are calls to
+ dino_ref/dino_deref
+ <youpi> hum
+ <braunr> i'm not sure at all these have anything to do with handling large
+ stores
+ <youpi> but dino_ref is introduced by this patch, isn't it?
+ <braunr> it replaces dino
+ <youpi> yes, it replaces it because the dino() approach can't work beyond
+ 2GiB
+ <braunr> i see
+ <braunr> youpi: i'd like to replace the recursive call to
+ disk_cache_block_ref with a goto, is that fine with you ?
+ <youpi> looks ok to me
+ <youpi> better than relying on tail recursion
+ <braunr> that's the idea :)
+
+
#### [[libpager]] API change
##### IRC, freenode, #hurd, 2013-03-04