lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5c49b0ed0608071614k3a62a982jbe27fa0c6d5fdb0@mail.gmail.com>
Date:	Mon, 7 Aug 2006 16:14:59 -0700
From:	"Nate Diller" <nate.diller@...il.com>
To:	"Jens Axboe" <axboe@...e.de>
Cc:	"Andrew Morton" <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm] [1/3] add elv_extended_request call to iosched API

On 8/4/06, Jens Axboe <axboe@...e.de> wrote:
> On Thu, Aug 03 2006, Andrew Morton wrote:
> > On Fri, 4 Aug 2006 07:20:32 +0200
> > Jens Axboe <axboe@...e.de> wrote:
> >
> > > On Thu, Aug 03 2006, Nate Diller wrote:
> > > > the Elevator iosched would prefer to be unconditionally notified of a
> > > > merge, but the current API calls only one 'merge' notifier
> > > > (elv_merge_requests or elv_merged_requests), even if both front and
> > > > back merges happened.
> > > >
> > > > elv_extended_request satisfies this requirement in conjunction with
> > > > elv_merge_requests.
> > >
> > > Ok, I suppose. But please rebase patches against the 'block' git branch,
> > > there are extensive changes in this area.
> > >
> >
> > argh, the great (but partial ;)) renaming bites again.
> >
> > A suitable patch to merge against is
> > http://www.zip.com.au/~akpm/linux/patches/stuff/git-block.patch
>
> not so much the renaming (that's easy enough), but the elevator core
> parts changed in some areas.

would it be appropriate to submit against 2.6.18-rc3-mm2?  I hope to
have a much-cleaned-up version tomorrow

thanks

NATE
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ