diff for duplicates of <1492616599.2543.2.camel@sandisk.com> diff --git a/a/1.txt b/N1/1.txt index f40994b..080e7aa 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,14 +1,10 @@ On Wed, 2017-04-19 at 09:02 +0200, Paolo Valente wrote: -> > Il giorno 19 apr 2017, alle ore 07:01, Bart Van Assche <bart.vanassche@= -sandisk.com> ha scritto: -> > What API was used by the Android application to tell the I/O scheduler= -=20 -> > to optimize for latency? Do you think that it would be sufficient if th= -e=20 -> > application uses the ioprio_set() system call to set the I/O priority t= -o=20 +> > Il giorno 19 apr 2017, alle ore 07:01, Bart Van Assche <bart.vanassche@sandisk.com> ha scritto: +> > What API was used by the Android application to tell the I/O scheduler +> > to optimize for latency? Do you think that it would be sufficient if the +> > application uses the ioprio_set() system call to set the I/O priority to > > IOPRIO_CLASS_RT? ->=20 +> > That's exactly the hack we are using in our prototype. However, it > can only be a temporary hack, because it mixes two slightly different > concepts: 1) the activation of weight raising and other mechanisms for @@ -38,4 +34,4 @@ additional I/O priorities in the Linux kernel next to the existing I/O priorities RT, BE and NONE and that this may require to map multiple of these priorities onto the same drive priority. -Bart.= +Bart. diff --git a/a/content_digest b/N1/content_digest index 7db8399..4ad4f31 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -15,16 +15,12 @@ "\00:1\0" "b\0" "On Wed, 2017-04-19 at 09:02 +0200, Paolo Valente wrote:\n" - "> > Il giorno 19 apr 2017, alle ore 07:01, Bart Van Assche <bart.vanassche@=\n" - "sandisk.com> ha scritto:\n" - "> > What API was used by the Android application to tell the I/O scheduler=\n" - "=20\n" - "> > to optimize for latency? Do you think that it would be sufficient if th=\n" - "e=20\n" - "> > application uses the ioprio_set() system call to set the I/O priority t=\n" - "o=20\n" + "> > Il giorno 19 apr 2017, alle ore 07:01, Bart Van Assche <bart.vanassche@sandisk.com> ha scritto:\n" + "> > What API was used by the Android application to tell the I/O scheduler \n" + "> > to optimize for latency? Do you think that it would be sufficient if the \n" + "> > application uses the ioprio_set() system call to set the I/O priority to \n" "> > IOPRIO_CLASS_RT?\n" - ">=20\n" + "> \n" "> That's exactly the hack we are using in our prototype. However, it\n" "> can only be a temporary hack, because it mixes two slightly different\n" "> concepts: 1) the activation of weight raising and other mechanisms for\n" @@ -54,6 +50,6 @@ "priorities RT, BE and NONE and that this may require to map multiple of\n" "these priorities onto the same drive priority.\n" "\n" - Bart.= + Bart. -0b0b290da53b1dd9529e6d51078a3354c214e61fb6826fbbc0a8d16715c5cbe0 +9a243aadcba43553344df6cb610e8db48773aa1b5536ae92f484735639e71b32
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.