linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: Luca Barbieri <ldb@ldb.ods.org>
Cc: trond.myklebust@fys.uio.no,
	Linux FSdevel <linux-fsdevel@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Initial support for struct vfs_cred   [0/1]
Date: Sat, 31 Aug 2002 12:36:04 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0208311235110.1255-100000@home.transmeta.com> (raw)
In-Reply-To: <1030820234.4408.119.camel@ldb>


On 31 Aug 2002, Luca Barbieri wrote:
>
> But aren't credential changes supposed to be infrequent?
> 
> If so, isn't it faster to put the fields directly in task_struct, keep a
> separate shared structure and copy them on kernel entry?

But that makes us copy them every time, even though they practically never 
change.. Much better to only copy them in the extremely rare cases when 
they do change.

		Linus


       reply	other threads:[~2002-08-31 19:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1030820234.4408.119.camel@ldb>
2002-08-31 19:36 ` Linus Torvalds [this message]
2002-08-31 19:38   ` [PATCH] Initial support for struct vfs_cred [0/1] Luca Barbieri
2002-08-31 22:30     ` Trond Myklebust
2002-08-31 23:13       ` Luca Barbieri
2002-09-01 13:03         ` Trond Myklebust
2002-09-01 14:10           ` Trond Myklebust
2002-09-01 14:20             ` Luca Barbieri
     [not found]             ` <1030890022.2145.52.camel@ldb>
2002-09-01 16:40               ` Trond Myklebust
     [not found]               ` <15730.17171.162970.367575@charged.uio.no>
2002-09-01 18:54                 ` Luca Barbieri
2002-09-01 19:40                   ` Trond Myklebust
     [not found]                   ` <15730.27952.29723.552617@charged.uio.no>
2002-09-01 21:34                     ` Luca Barbieri
     [not found]                     ` <1030916061.2145.344.camel@ldb>
2002-09-01 21:56                       ` Trond Myklebust
     [not found]                       ` <15730.36080.987645.452664@charged.uio.no>
2002-09-01 22:50                         ` Luca Barbieri
2002-09-01 14:33           ` Luca Barbieri
2002-09-01 16:38             ` Trond Myklebust
2002-09-01 18:42               ` Luca Barbieri
2002-09-01 19:25                 ` Trond Myklebust
2002-09-01 21:36                   ` Luca Barbieri
2002-09-01 15:15         ` Daniel Phillips
2002-09-01 15:35           ` Luca Barbieri
     [not found] <15728.61345.184030.293634@charged.uio.no>
2002-08-31 18:57 ` Luca Barbieri
2002-08-31 19:51 ` Luca Barbieri
2002-08-31 16:32 Trond Myklebust

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0208311235110.1255-100000@home.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=ldb@ldb.ods.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).