Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20181230163143.21030-1-ap420073@gmail.com> <20190105.141021.1299321405902891635.davem@davemloft.net>
 <CAMArcTUGujArU1L8L=n32yKbT+MwuUEm6S8C=am_EGQ5GG3jQA@mail.gmail.com> <20190106.085535.1209544587823450673.davem@davemloft.net>
In-Reply-To: <20190106.085535.1209544587823450673.davem@davemloft.net>
From:   Taehee Yoo <ap420073@gmail.com>
Date:   Mon, 7 Jan 2019 12:44:44 +0900
Message-ID: <CAMArcTXvCMPHarHJy19QAr9AKb4w2RNQ-E6JJoBhuD3eGhHkSg@mail.gmail.com>
Subject: Re: [PATCH net 1/4] umh: add exit routine for UMH process
To:     David Miller <davem@davemloft.net>
Cc:     Netdev <netdev@vger.kernel.org>, linux-kernel@vger.kernel.org,
        Daniel Borkmann <daniel@iogearbox.net>, ast@kernel.org,
        mcgrof@kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, 7 Jan 2019 at 01:55, David Miller <davem@davemloft.net> wrote:
>
> From: Taehee Yoo <ap420073@gmail.com>
> Date: Sun, 6 Jan 2019 14:34:52 +0900
>
> > How about adding a new PF_UMH flag for task_struct->flags to identify
> > UMH process?
> > By using this flag, the exit_umh() can avoid unnecessary lookups.
>
> Yes, that might be more efficient and eliminate the high cost for
> non-UMH tasks.

I will send a v3 patch.
Thank you!