[lkml]   [2005]   [Oct]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] Use of getblk differs between locations
    On Wed, 12 Oct 2005, Mikulas Patocka wrote:
    > > > Is memory management ready for this? Can't deadlock like this happen?
    > > > - displaying dialog window needs memory, so it waits until memory will
    > > > be available
    > > > - system decides to write some write-back cached data in order to free
    > > > memory
    > > > - the write of these data waits until the dialog window is displayed,
    > > > user inserts the device and clicks 'OK'
    > >
    > > No, it's not, and deadlock is definitely possible. However, if we're at
    > > the point where memory is tight enough that it's an issue, the timer can
    > > expire and all the pending i/o is dropped just as it would be without
    > > the multipath code enabled.
    > >
    > > I'm not saying it's a solution ready for production, just a good
    > > starting point.
    > But discarding data sometimes on USB unplug is even worse than discarding data
    > always --- users will by experimenting learn that linux doesn't discard
    > write-cached data and reminds them to replug the device --- and one day,
    > randomly, they lose their data because of some memory management condition...

    And how exactly is that worse than discarding the data every time?!?!?!?

    Best regards,

    Anton Altaparmakov <aia21 at> (replace at with @)
    Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
    Linux NTFS maintainer / IRC: #ntfs on
    WWW: &
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-10-12 22:17    [W:0.022 / U:38.784 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site