Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1598137

Re: [PATCH 2/5] x86/intel_rdt: Improvements to parsing schemata

From "Luck, Tony" <tony.luck@intel.com>
Newsgroups linux.kernel
Subject Re: [PATCH 2/5] x86/intel_rdt: Improvements to parsing schemata
Date 2017-03-10 23:10 +0100
Message-ID <tjATw-1Jy-7@gated-at.bofh.it> (permalink)
References (2 earlier) <tgd73-47I-5@gated-at.bofh.it> <tjgi6-45M-13@gated-at.bofh.it> <tjqr8-2Qu-25@gated-at.bofh.it> <tjxsC-7NS-25@gated-at.bofh.it> <tjxVD-80K-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Fri, Mar 10, 2017 at 07:58:51PM +0100, Thomas Gleixner wrote:
> Well, we have several options to tackle this:
> 
> 1) Have schemata files for each resource
> 
>    schemata_l2, _l3 _mb
> 
> 2) Request a full overwrite every time (all entries required)
> 
>    That still does not require ordering
> 
> 3) Allow full overwrite and 'append' mode
> 
>    echo "...." > schemata
> 
>    Overwrites the whole file. It does not require all entries to be
>    supplied.  Non supplied entries are reset to default
> 
>    echo "...." >> schemata
> 		 
>    "Appends" the supplied entries by overwriting the existing ones.
> 
> My favourite would be #1, but I have no strong opinions other than not
> caring about resource write ordering for #2 and #3.

If you are going to head in the direction of partial update, then
why not go for:

4) Drop the code that check that the user wrote all
   the fields as well as the check for all the lines. Just update
   the bits they list, and leave the rest unchanged.

I.e. the user could say:

# echo "L3:1=0x3f" > schemata

if they just wanted to update resource L3, instance 1.

I don't think there is much benefit to the overwrite vs. append
semantics for the user.

-Tony

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH 2/5] x86/intel_rdt: Improvements to parsing schemata Thomas Gleixner <tglx@linutronix.de> - 2017-03-01 15:10 +0100
  Re: [PATCH 2/5] x86/intel_rdt: Improvements to parsing schemata Shivappa Vikas <vikas.shivappa@linux.intel.com> - 2017-03-10 01:10 +0100
    Re: [PATCH 2/5] x86/intel_rdt: Improvements to parsing schemata Thomas Gleixner <tglx@linutronix.de> - 2017-03-10 12:00 +0100
      Re: [PATCH 2/5] x86/intel_rdt: Improvements to parsing schemata Shivappa Vikas <vikas.shivappa@intel.com> - 2017-03-10 19:30 +0100
        Re: [PATCH 2/5] x86/intel_rdt: Improvements to parsing schemata Thomas Gleixner <tglx@linutronix.de> - 2017-03-10 20:00 +0100
          Re: [PATCH 2/5] x86/intel_rdt: Improvements to parsing schemata "Luck, Tony" <tony.luck@intel.com> - 2017-03-10 23:10 +0100
            Re: [PATCH 2/5] x86/intel_rdt: Improvements to parsing schemata Thomas Gleixner <tglx@linutronix.de> - 2017-03-11 08:50 +0100

csiph-web