summaryrefslogtreecommitdiff
path: root/open_issues/performance
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2013-04-07 18:28:11 +0200
committerThomas Schwinge <thomas@codesourcery.com>2013-04-07 18:28:11 +0200
commit325d3600adae1a2da62f9a24ac34ad2b47a22f97 (patch)
treef0637c13c8aec0d0793f7d2498f5e2237e693c4b /open_issues/performance
parentacab07dfc9df44d6d54e03c701a90b5d6f537fcd (diff)
parent6c7d45e4631784d0e077e806521a736da6b0266e (diff)
Merge remote-tracking branch 'fp/master'
Conflicts: hurd.mdwn hurd/debugging/rpctrace.mdwn open_issues/clock_gettime.mdwn open_issues/time.mdwn
Diffstat (limited to 'open_issues/performance')
-rw-r--r--open_issues/performance/io_system/read-ahead.mdwn42
1 files changed, 42 insertions, 0 deletions
diff --git a/open_issues/performance/io_system/read-ahead.mdwn b/open_issues/performance/io_system/read-ahead.mdwn
index 8a8ba823..768dca93 100644
--- a/open_issues/performance/io_system/read-ahead.mdwn
+++ b/open_issues/performance/io_system/read-ahead.mdwn
@@ -2989,3 +2989,45 @@ License|/fdl]]."]]"""]]
determine what m_o_ function will be used
<mcsim> now default_read calls m_o_ on its own
<braunr> ok
+
+
+## IRC, freenode, #hurd, 2013-03-06
+
+ <mcsim> braunr: hi, regarding memory policies. Should I create separate
+ policy that will do pageout or VM_ADVICE_SEQUENTIAL is good enough?
+ <mcsim> braunr: at the moment it is exactly like NORMAL
+ <braunr> mcsim: i thought you only did pageins
+ <mcsim> braunr: yes, but I'm doing pageouts now
+ <braunr> oh
+ <braunr> i'd prefer you didn't :/
+ <braunr> if you want to improve paging, i have a suggestion i believe is a
+ lot better
+ <braunr> and we have 3 patches concerning libpager that we need to review,
+ polish, and merge in
+ <mcsim> braunr: That's not hard, and I think I know what to do
+ <braunr> yes i understand that
+ <braunr> but it may change the interface and conflict with the pending
+ changes
+ <mcsim> braunr: What changes?
+ <braunr> the large store patch, neal's libpager rework patch on top of
+ which you made your changes, and your changes
+ <braunr> the idea i have in mind was writeback throttling
+
+[[hurd/translator/ext2fs]], [[hurd/libpager]].
+
+ <braunr> i was planning on doing it myself but if you want to work on it,
+ feel free to
+ <braunr> it would be a much better improvement at this time than clustered
+ pageouts
+ <braunr> (which can then immediately follow
+ <braunr> )
+ <mcsim> braunr: ok
+ <mcsim> braunr: but this looks much more bigger task for me
+ <braunr> we'll talk about the strategy i had in mind tomorrow
+ <braunr> i hope you find it simple enough
+ <braunr> on the other hand, clustered pageouts are very similar to pageins
+ <braunr> and we have enough paging related changes to review that adding
+ another wouldn't be such a problem actually
+ <mcsim> so, add?
+ <braunr> if that's what you want to do, ok
+ <braunr> i'll think about your initial question tomorrow